Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

2018-05-08 Thread Stuart Prescott
Paul Wise wrote: > If someone revives this service, this approach missed packages that do > not use a VCS. This could be worked around by the addition of fetching > from source packages when there is no VCS. The VCS should be preferred > since source packages don't need to be updated immediately wh

Re: recutils is marked for autoremoval from testing

2018-05-08 Thread Mattia Rizzolo
On Tue, May 08, 2018 at 12:17:48AM +0200, Sven Wick wrote: > would you sponsor it another time? Of course :) Though it's probably better if next time (starting with the next email, I'm still keeping it here to publicly ack the mail) we don't bother debian-qa@ for this, as it has nothing to do wit

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

2018-05-08 Thread Paul Wise
On Tue, May 8, 2018 at 4:02 PM, Stuart Prescott wrote: > or looking at Contents-source.gz and linking to sources.debian.net. (or > asking ftp-master to export these files like they do with changelogs, > copyright files etc.) Good idea. vcswatch could take over the VCS scanning too. > Are there a

Re: What to do with the "Upstream info" links in the PTS and the packages-metadata branch in collab-qa ?

2018-05-08 Thread gregor herrmann
On Tue, 08 May 2018 17:22:40 +0800, Paul Wise wrote: > On Tue, May 8, 2018 at 4:02 PM, Stuart Prescott wrote: > > Are there any other consumers of these files? > No services, but potentially tracker.d.o and packages.d.o. > People interacting with the source package might use them. Right, in the