On Mon, 2015-02-09 at 17:53:36 +0100, Joost van Baal-Ilić wrote: > On Mon, Feb 09, 2015 at 04:38:35PM +0100, Holger Levsen wrote: > > On Montag, 9. Februar 2015, David Prévot wrote: > > > They are purposely built then uploaded and installed separately in the > > > archive: > > [...] > > > Maybe this bug should rather be reassigned to the reproducible effort. > > > > I dont think this bug is in any way related to the reproducible effort, > > that's > > just how I noticed it. As a mere user I'd be equally surprised if some > > build > > leaves stuff in the pbuilder results dir. > > > > Maybe its just a very seldom used feature of pbuider. > > > > > From the end of debian/rules: > > > # list them in the .changes file, so that they'll get uploaded properly: > > > dpkg-distaddfile debian-faq.en.html.tar.gz byhand - > > > dpkg-distaddfile debian-faq.en.txt.gz byhand - > > > dpkg-distaddfile debian-faq.en.ps.gz byhand - > > > dpkg-distaddfile debian-faq.en.pdf.gz byhand - > > > > I see. I'm not sure this should be part of the standard binary targets > > then...
The whole point of BYHAND processing is that it allows to include non-standard files in the archive, if those are not included in the *.changes file for every upload then the archive docs would always be out-of-date compared to the package. If there's a problem, then it's in pbuilder's (or whoever is in charge of) cleaning up, it should be removing any artifacts referenced from the *.changes file. > AFAIK, this is some ancient way to make sure these documents end up in > ftp://ftp.debian.org/debian/doc/FAQ/ . Could be this practice is obsolete now > and/or should be dealt with differently. I don't think there's any automatic way to pull stuff that is not source or binary packages into the archive, no. Regards, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
