[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#887060: testing migration happened despite FTBFS on arch:all buildd



On 2020-12-20, Paul Gevers wrote:
> On Thu, 15 Nov 2018 20:49:43 +0100 Paul Gevers <elbrus@debian.org> wrote:
>> I think I have found the cause for this issue. Apparently some arch:all
>> binary packages are not listed in both the binary-<arch>/Packages.* and
>> binary-all/Packages.* file groups, but ONLY in the binary-all/Packages.*
>> files (at least on unstable). The britney log tells me that the
>> binary-all files are not read in yet.
>> 
>> Currently the source package bzr is in this position (and I noticed
>> because autopkgtest fails on non-installability of the arch:all
>> packages), which enabled me to figure this out.
>
> Today (noted on IRC), pcb-rnd was in the same position. Luckily the
> migration didn't happen because the second phase blocked the migration
> (pcb-rnd (the binary) depends on pcb-rnd-doc).
>
> pcb-rnd-doc is in binary-all/Packages.* but not in binary-<any>/Packages.*.
>
> The situation will be gone soon, pcb-rnd build on arch:all several
> minutes ago.

FWIW, This also recently happened with src:u-boot, u-boot migrated
u-boot *:any even though u-boot-qemu:all FTBFS.


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature


Reply to: