Control: tags 1135774 patch
Hi doko
On 6/4/26 05:11, Matthias Klose wrote:
> sure, but it's not release critical. At least that's an undocumented
> requirement.
This makes at least gcc-for-build non-installable, see #1135774 [1],
which already has a patch. Being installable in testing is a
requirement for migration.
> you also seem to have more insight into that issue than you are willing
> to communicate in the bug report. Please don't do this, but describe
> the issue as complete as possible.
gcc-defaults 1.230 was binNMU'd on 2026-04-26 [2] for the reason
'Rebuild on buildd for loong64'. gcc-defaults 1.230+b1 binaries have
been unable to migrate to testing [3] since then.
trying: gcc-defaults/amd64
skipped: gcc-defaults/amd64 (6, 0, 24)
got: 55+1419: a-27:a-7:a-3:i-18:l-1419:p-0:r-0:s-0
* amd64: cpp-for-build, g++-for-build, ga68-for-build,
gcc-for-build, gccgo-for-build, gcobol-for-build, gdc-for-build,
gfortran-for-build, gm2-for-build, gobjc++-for-build, gobjc-for-build
Regards
Graham
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1135774
[2] https://buildd.debian.org/status/package.php?p=gcc-defaults
[3] https://release.debian.org/britney/update_output.txt
