On Tue, Nov 01, 2016 at 10:47:05AM +0100, Paolo Greppi wrote: > On 30/10/2016 11:40, Mattia Rizzolo wrote: > > ok, but I find weird that you bumped std-ver 3.9.5 → 3.9.6 then… > > You could have gone all the way to 3.9.8, since no changes are needed > > for this package anyway. > > https://www.debian.org/doc/debian-policy/upgrading-checklist > > The reason is that 3.9.6 is the current one on jessie. But will 0.1.3-2 > ever get to jessie ?
It wont, development targets unstable. And even if you're doing a backport to jessie-backports that's not a reason to declare compliance to an old version of policy. > > > Other things:: > > * you changed d/watch to point to somebody else's repo in github, > > writing "Fix d/watch". You're not saying what that fixes; it > > should really work both ways, since there is a redirect. > > Also please use more descriptive messagges in changelog > > OK > > The old watch faile is currently failing on > https://packages.qa.debian.org/n/node-findup-sync.html > whereas the redirect works on: > https://tracker.debian.org/pkg/node-findup-sync > > Probably we're all on the bleeding edge (tracker.d.o) but people who > click on the Developer Information (PTS) link on packages.d.o still land > on packages.qa.d.o pacakges.qa.debian.org doesn't updated d/watch info anymore; it used a backend that's now removed (it use a thing we called "mole"), wheras tracker.d.o gets the uscan data from UDD. Have you found a package on package.qa.debian.org that doesn't show an error for uscan? And how would that change make it work "on" packages.qa.debian.org anyway? -- 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 `-
Description: PGP signature