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

Helmut Grohne helmut at subdivi.de
Tue Nov 1 05:08:45 GMT 2022


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.

Helmut



More information about the Pkg-systemd-maintainers mailing list