Bug#1110737: trixie-pu: package systemd/257.8-1~deb13u1
On Mon, 25 Aug 2025 at 14:33, Adam D. Barratt <adam@adam-barratt.org.uk> wrote:
> > > 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
That will be otherwise solved once the other blocker is removed. If
you check on the excuses, the syslog-ng tests are not working (chain
tmpfailing, so always shows as 'running' at any given time) due to
that autopkgtest issue, so that's the last remaining blocker.
So either that MR, or another similar fix needs to be merged in
autopkgtest, then a new version uploaded and deployed to debci, and
then that syslog-ng test will work again. Or alternatively, the
autopkgtest results need to be ignored/waved.
Reply to: