Re: CMake 4 upload to unstable
On Thu, Sep 25, 2025 at 10:33:31AM +0200, Lucas Nussbaum wrote:
> On 25/09/25 at 10:00 +0200, Paul Gevers wrote:
> > I'm wondering if we
> > should hold off migrating cmake 4 while we're waiting a bit for autoremoval
> > to do its job (including sending notifications). Or should we be more
> > aggressive with manual removal? What do you think?
>
> I wonder if we should decrease the auto-removal timeouts to make it
> easier to get broken packages out of testing (and new packages in
> testing) and increase it again later in the release cycle.
>
> There's some value to faster transitions even if that means temporarily
> removing non-key packages from testing. There's plenty of time to get
> them back in testing.
Your suggestion might not result in faster transitions.
As long as the autopkgtest of at least one key package gets broken
(as is the case for CMake) it's either a manual hint to ignore
autopkgtest failures or no migration.
Of the ~ 800 CMake 4 bugs only ~ 30 might have relevance for
migration.[1]
> Lucas
cu
Adrian
BTW: The first key package with an autopkgtest broken by CMake 4
I looked at does not even have a bug (libzstd).
[1] https://release.debian.org/britney/pseudo-excuses-experimental.html#cmake
Reply to: