Bug#910987: Bug#917025: tracker.debian.org: 0 new commits since last upload
Control: reassign -1 tracker.debian.org Re: Mattia Rizzolo 2018-12-21 <20181221211515.gn19...@mapreri.org> > > Not sure if this is a duplicate of #910987, but I see the problem. > > Not quite. However, it's not a problem coming from tracker, rather by > the data source it uses. It's somewhat related because in both bugs, the wording used by the tracker is the problem. In #910987, the information is technically correct, but the wording is a little bit too aggressive in suggesting that A Upload Is Needed Now. > > -->8-- > > action needed > > 0 new commits since last upload, time to upload? normal > > vcswatch reports that this package seems to have a new changelog entry > > (version 1:5.25.2-2, distribution unstable) and new commits in its VCS. > > You should consider whether it's time to make an upload. > > > > Here are the relevant commit messages: > > > > None > > > > Created: 2018-12-21 Last update: 2018-12-21 15:05 > > -->8--- > > > > Latest commit is 727f110b (tagged then, after several minutes, > > everything was pushed to the public repo _before_ upload to > > the debian archive was done). The problem here is that the tracker is interpreting the information from vcswatch wrongly. The "commits since last tag" information should only be used when the status is "COMMITS". And even when done correctly, it should rather be saying "eventually this package should be uploaded", and not "time to upload?" which seems to suggest that this should happen "now". Christoph
Bug#917025: tracker.debian.org: 0 new commits since last upload
Control: reassign -1 qa.debian.org On Fri, Dec 21, 2018 at 07:11:18PM +0300, Sergey B Kirpichev wrote: > Not sure if this is a duplicate of #910987, but I see the problem. Not quite. However, it's not a problem coming from tracker, rather by the data source it uses. > Right now interface on https://tracker.debian.org/pkg/monit shows: FWIW, I see the issue is now gone from that package, however I saw it elsewhere today (but was too lazy to report). I'm reassigning to the right pseudo-package, CCing the maintainer of the vcswatch service. :) > -->8-- > action needed > 0 new commits since last upload, time to upload? normal > vcswatch reports that this package seems to have a new changelog entry > (version 1:5.25.2-2, distribution unstable) and new commits in its VCS. > You should consider whether it's time to make an upload. > > Here are the relevant commit messages: > > None > > Created: 2018-12-21 Last update: 2018-12-21 15:05 > -->8--- > > Latest commit is 727f110b (tagged then, after several minutes, > everything was pushed to the public repo _before_ upload to > the debian archive was done). > -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#917025: tracker.debian.org: 0 new commits since last upload
Package: tracker.debian.org Severity: normal Not sure if this is a duplicate of #910987, but I see the problem. Right now interface on https://tracker.debian.org/pkg/monit shows: -->8-- action needed 0 new commits since last upload, time to upload? normal vcswatch reports that this package seems to have a new changelog entry (version 1:5.25.2-2, distribution unstable) and new commits in its VCS. You should consider whether it's time to make an upload. Here are the relevant commit messages: None Created: 2018-12-21 Last update: 2018-12-21 15:05 -->8--- Latest commit is 727f110b (tagged then, after several minutes, everything was pushed to the public repo _before_ upload to the debian archive was done).
