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

2022-01-18 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 915948 Bug #887060 [release.debian.org] testing migration happened despite FTBFS on arch:all buildd 887060 was not blocked by any bugs. 887060 was not blocking any bugs. Added blocking bug(s) of 887060: 915948 -- 887060: https://bugs.debian.org/cgi-bin

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

2022-01-18 Thread Paul Gevers
Control: block -1 by 915948 Hi, On 18-01-2022 21:59, Vagrant Cascadian wrote: On 2020-12-20, Paul Gevers wrote: On Thu, 15 Nov 2018 20:49:43 +0100 Paul Gevers wrote: I think I have found the cause for this issue. Apparently some arch:all binary packages are not listed in both the binary-/Pac

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

2022-01-18 Thread Vagrant Cascadian
On 2020-12-20, Paul Gevers wrote: > On Thu, 15 Nov 2018 20:49:43 +0100 Paul Gevers wrote: >> I think I have found the cause for this issue. Apparently some arch:all >> binary packages are not listed in both the binary-/Packages.* and >> binary-all/Packages.* file groups, but ONLY in the binary-all

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

2020-12-19 Thread Paul Gevers
Hi all, On Thu, 15 Nov 2018 20:49:43 +0100 Paul Gevers wrote: > I think I have found the cause for this issue. Apparently some arch:all > binary packages are not listed in both the binary-/Packages.* and > binary-all/Packages.* file groups, but ONLY in the binary-all/Packages.* > files (at least

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

2018-11-15 Thread Paul Gevers
Dear all, I think I have found the cause for this issue. Apparently some arch:all binary packages are not listed in both the binary-/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 fi

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

2018-06-07 Thread Paul Gevers
(from IRC) I just saw (unfortunately the data will be gone now): old binaries left on all: python-doc (from 2.7.15~rc1-1) (but ignoring cruft, so nevermind) Maybe a hint, this happened in the package python-defaults. I don't think it shouldn't say "cruft". Paul signature.asc Description: Ope

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

2018-01-13 Thread Sébastien Villemot
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: britney Hi, Package src:octave-interval creates two binaries: - octave-interval (arch:any) - octave-interval-doc (arch:all) Version 3.1.0-3 was uploaded on 2018-01-07 as source-only: https://tra