Bug#1023248: systemd fails to install: Failed to resolve group 'systemd-journal'.

[Jochen Sprickerhof]

Hi Helmut,

* Helmut Grohne <helmut at subdivi.de> [2022-11-01 06:08]:
>Package: systemd
>Version: 252-1
>Severity: serious
>
>systemd fails to install in unstable:
>
>mmdebstrap --verbose --variant apt --include systemd unstable /dev/null
>
>| Setting up systemd (252-1) ...
>| Created symlink /etc/systemd/system/getty.target.wants/getty at tty1.service → /lib/systemd/system/getty at .service.
>| Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target → /lib/systemd/system/remote-fs.target.
>| Created symlink /etc/systemd/system/sysinit.target.wants/systemd-pstore.service → /lib/systemd/system/systemd-pstore.service.
>| Initializing machine ID from random generator.
>| /usr/lib/tmpfiles.d/systemd.conf:28: Failed to resolve group 'systemd-journal'.
>| /usr/lib/tmpfiles.d/systemd.conf:29: Failed to resolve group 'systemd-journal'.
>| /usr/lib/tmpfiles.d/systemd.conf:30: Failed to resolve group 'systemd-journal'.
>| dpkg: error processing package systemd (--configure):
>|  installed systemd package post-installation script subprocess returned error exit status 65
>| Processing triggers for libc-bin (2.35-4) ...
>| Errors were encountered while processing:
>|  systemd
>| E: Sub-process env returned an error code (1)
>
>Hope you can figure this out quickly. It happens to break rebootstrap
>CI. If you happen to know a workaround that'd be appreciated as well.

I've opened a MR to fix this:

https://salsa.debian.org/systemd-team/systemd/-/merge_requests/182

Cheers Jochen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20221101/e8c163e2/attachment.sig>