Bug#1110414: systemd-sysv: Missing versioned dependency on libsystemd-shared
Luca Boccassi
bluca at debian.org
Mon Aug 18 10:41:10 BST 2025
Control: tags -1 -moreinfo unreproducible
Control: close -1
On Mon, 18 Aug 2025 at 10:33, Michael Biebl <biebl at debian.org> wrote:
>
> On Sun, 10 Aug 2025 13:16:13 +0100 Luca Boccassi <bluca at debian.org> wrote:
> > Control: tags -1 moreinfo
> >
> > The dependencies all look correct to me, so I'm not quite sure I follow
> > what the issue is.
> >
> > Package: systemd-sysv
> > Version: 257.7-1
> > Depends: systemd (= 257.7-1)
> > Pre-Depends: systemd
> >
> > Package: systemd
> > Version: 257.7-1
> > Pre-Depends: libc6 (>= 2.38), libsystemd-shared (= 257.7-1)
> >
> The problem afaics is, that systemd has a Pre-Depends on both the new
> libc6 and new libsystemd-shared.
>
> Both are unpacked, then libc6.postinst triggered a daemon-reexec. At
> this point old systemd and new libsystemd-shared were installed → crash.
>
> There has been corresponding commit in glibc at the meantime:
>
> https://salsa.debian.org/glibc-team/glibc/-/commit/cab7833001ed8031e1cb834976518463b1d5f2fd
>
> which should avoid this situation.
Still looks like an apt issue to me, the old systemd has a strict
dependency on libsystemd-shared, so surely it should unpack the new
one too before executing anything. Unpacking just libraries but not
what has strict dependencies on them, and then executing things, means
the system is in an inconsistent state.
And also glibc shouldn't really restart systemd or anything at all,
there's need-restart for that nowadays.
More information about the Pkg-systemd-maintainers
mailing list