Bug#1110737: trixie-pu: package systemd/257.8-1~deb13u1

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

On Mon, 2025-08-25 at 14:23 +0100, Luca Boccassi wrote:
> On Mon, 25 Aug 2025 at 14:07, Adam D. Barratt
> <adam@adam-barratt.org.uk> wrote:
> > 
> > [CCed to kibi and -boot for visibility]
> 
> Moving to BCC, please note that since Trixie the src:systemd package
> is _not_ used anymore for D-I, as udebs are built elsewhere. Hence
> there is no need to trouble kibi and the D-I team for these uploads
> anymore going forward.
> 

Thanks for the note, I'll try and remember that for future updates.

> > On Sun, 2025-08-10 at 17:02 +0100, Luca Boccassi wrote:
> > > New release, new stable series.
> > > 
> > > We would like to upload the latest stable point release of
> > > systemd
> > > 257 to trixie-p-u.
> > 
> > Getting this into 13.1 is currently blocked by #1110980, as stable
> > and testing currently have the same systemd version, so we'd end up
> > with unstable > stable > testing.
> 
> It's actually blocked by
> https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/588
> as that bugfix is needed for one autopkgtest to succeed. Once that is
> merged and updated in debci, it will migrate.

I must admit that I'm a little confused here, as the current britney
excuses imply that both are blockers. The version metadata on #1110980
also supports that.

systemd (257.7-1 to 258~rc3-1)
    Maintainer: Debian systemd Maintainers
    Migration status for systemd (257.7-1 to 258~rc3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
    Issues preventing migration:
    ∙ ∙ Updating systemd would introduce bugs in testing: #1110980

> The kernel is also newer in stable (via -security), so is there any
> reason it couldn't get the same treatment?

You are correct that the kernel has version skew in -security
currently, and that's something we're trying to resolve. If you check
through the logs of #d-release over the weekend, you'll see that we
asked the kernel team about the situation, and are not keen to try and
carry the issue through into stable itself.

For clarity, the relevant version of the kernel is *not* in p-u right
now.

Regards,

Adam