On Sat, 8 Dec 2018 11:19:27 +0200 Niko Tyni <[email protected]> wrote: > ISTR there at least used to be a check where arch:all binaries are not > exposed before the corresponding arch:any ones are built, but it looks > like the reverse is not true? In any case, even the old versions (5.28.1-2 > in this case) of the arch:all binaries disappearing seems incorrect to me?
There is an argument to be made that arch:all/arch:any packages should be copied into the Packages files even without the corresponding arch:any/arch:all packages being built (for example because of a FTBFS): once an arch:all/arch:any package is put into incoming.d.o it can be used to build other source packages. At that point it should end up in a Packages file because otherwise it will not be registered by snapshot.d.o and then a source package built on the buildds might not be reproducible anymore as one of its build dependencies never appeared on snapshot.d.o. Relevant MR: https://salsa.debian.org/ftp-team/dak/-/merge_requests/298 Thanks! cheers, josch
signature.asc
Description: signature
