On Sat, 2015-05-30 at 10:49 +0000, Gianfranco Costamagna wrote:
[...]
> >And I've just had to ask ftp-master to do more manual work to get the
> >amd64 buildd upload accepted in to the archive (currently pending on
> >someone having chance to do so).
>
> >We've discussed this on IRC and it was mentioned in my recent dda post -
> >if you're not uploading amd64 binaries, _please_ stop calling
> >the .changes file that you upload to stable "_amd64.changes".
>
>
> Your work is so much appreciated.
>
> I read your dda post, but this seems to clash with what ftp members
> told us a while ago [1] (or does just pu uploads
> behave differently from unstable ones?).
We cleared this up briefly on IRC earlier today, but for the record the
potential for name clashes affects any suite which uses a policy queue
as part of processing uploads - so at least the {,old}stable, backports
and security suites.
As you mentioned, the case where this used to be a problem for other
suites was resolved a while ago, but where a policy queue is involved,
dak keeps the .changes files around - you can see this by looking at
e.g. dists/proposed-updates on an ftp.d.o mirror - so there's still the
potential for clashes in those cases.
It sounds like ftp-master are looking at potential ways of making this
not be a problem for much longer, but that's the situation right now.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1432987712.1901.5.ca...@adam-barratt.org.uk
