On Mon, 2015-05-25 at 20:47 +0200, Julien Cristau wrote: > On Mon, May 25, 2015 at 19:42:48 +0100, Simon McVittie wrote: > > > On 25/05/15 18:24, Lisandro Damián Nicanor Pérez Meyer wrote: > > > On Sunday 24 May 2015 21:27:47 Adam D. Barratt wrote: > > > [snip] > > >> Due to the way that the archive manages uploads to proposed-updates, if > > >> you upload a .changes file which only includes source and > > >> architecture:all packages, please ensure that you rename it to something > > >> other than "_$arch.changes". > > > > Does this only apply to source packages that produce at least one binary > > package on $arch, or does it also apply to source packages that solely > > produce architecture-independent binaries? > > > No, the issue is when the maintainer-uploaded .changes file name clashes > with the one from a binary (buildd) upload, so if there aren't any > architecture-dependent binaries, then this doesn't matter.
Perhaps the infrastructure could use something which doesn't clash with real person usages, e.g. "_$arch-buildd.changes" perhaps? (Eventually I mean). Ian. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1432647722.14664.118.ca...@debian.org
