Dear Release Managers:
Given that packages in trixie must build in trixie, I tried
building all packages in trixie/sid from a machine running trixie
(i.e. the machine itself, including the kernel, not just the chroot).
I only found one build failure which may be explained by the
kernel of trixie, which I reported here, but the maintainer disagrees
about the severity on the basis that the buildds have not been
upgraded to trixie yet:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105067#68
(Note: You can skip all messages before #68 as they are mostly noise. Apparently maintainer missed that I was running trixie and I had to forward
the bug upstream myself before he decided to reproduce the bug in trixie
as I reported it).
I personally believe this is worse than packages containing time-bombs,
which we already agreed to make RC when we can anticipate that the
package would fail to build at some point during the three years
following the release date.
Even if we would take whatever happens in the autobuilders as the sole
criteria for RC-ness (which I think it's not a good idea), I believe
the package would fail to build quite soon after the release of trixie,
so following the time-bomb rationale, I think this one would be RC now as well.
Thanks.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)