Re: Upstream release monitoring issue
On Tue, Feb 02, 2016 at 04:11:46PM -0600, Richard Shaw wrote:
I was notified by a user that a newer version of trustedqsl was
available
so I looked into why I wasn't notified.
For some reason it still thinks 1.13 is the current version when it is
2.2:
https://release-monitoring.org/project/4998/
I've tried tweaking things but can't seem to find the magic formula to get
it to work.
Any suggestions?
I fixed it.
I had to set the name of the project to tqsl (which is the name of the tarball
anitya looks for) and the name of the sourceforge project to trustedqsl (so it
knows in which SF projects to look for this tarball).
You should have received a notification for 2.2.
Pierre