Your message dated Mon, 03 Feb 2020 23:35:07 +0000 with message-id <e1iylfd-000dd8...@fasolo.debian.org> and subject line Bug#950533: fixed in systemd 244.1-3 has caused the Debian Bug report #950533, regarding upgrade fails in a chroot without mounted /proc to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 950533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: systemd Version: 244.1-2 Severity: serious Hi folks, I'm guessing this is fallout from enabling persistent journal by default, maybe. I have a development box running multiple chroots, and ths sid chroots are now failing to upgradw with the following errors: Upgrading from 240-5 to 244.1-2: ... Need to get 0 B/5987 kB of archives. After this operation, 444 kB of additional disk space will be used. E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device) Setting up systemd (244.1-2) ... [/usr/lib/tmpfiles.d/systemd-tmp.conf:11] Failed to replace specifiers: /tmp/systemd-private-%b-* [/usr/lib/tmpfiles.d/systemd-tmp.conf:12] Failed to replace specifiers: /tmp/systemd-private-%b-*/tmp [/usr/lib/tmpfiles.d/systemd-tmp.conf:13] Failed to replace specifiers: /var/tmp/systemd-private-%b-* [/usr/lib/tmpfiles.d/systemd-tmp.conf:14] Failed to replace specifiers: /var/tmp/systemd-private-%b-*/tmp [/usr/lib/tmpfiles.d/systemd-tmp.conf:22] Failed to replace specifiers: /var/lib/systemd/coredump/.#core*.%b* ACL operation on "/var/log/journal" failed: No such file or directory ACL operation on "/var/log/journal" failed: No such file or directory Failed to re-open '/var/log/journal': No such file or directory fchmod() of /var/log/journal failed: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 73 Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I don't have a /var/log/journal in those chroots. -- Package-specific info: -- System Information: Debian Release: 10.2 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.53-4 ii libapparmor1 2.13.2-10 ii libaudit1 1:2.8.4-3 ii libblkid1 2.33.1-0.1 ii libc6 2.28-10 ii libcap2 1:2.25-2 ii libcryptsetup12 2:2.1.0-5+deb10u2 ii libgcrypt20 1.8.4-5 ii libgnutls30 3.6.7-4 ii libgpg-error0 1.35-1 ii libidn11 1.33-2.2 ii libip4tc0 1.8.2-4 ii libkmod2 26-1 ii liblz4-1 1.8.3-1 ii liblzma5 5.2.4-1 ii libmount1 2.33.1-0.1 ii libpam0g 1.3.1-5 ii libseccomp2 2.3.3-4 ii libselinux1 2.8-1+b1 ii libsystemd0 241-7~deb10u2 ii mount 2.33.1-0.1 ii util-linux 2.33.1-0.1 Versions of packages systemd recommends: ii dbus 1.12.16-1 ii libpam-systemd 241-7~deb10u2 Versions of packages systemd suggests: ii policykit-1 0.105-25 ii systemd-container 241-7~deb10u2 Versions of packages systemd is related to: pn dracut <none> ii initramfs-tools 0.133+deb10u1 ii udev 241-7~deb10u2 -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- no debconf information
--- End Message ---
--- Begin Message ---Source: systemd Source-Version: 244.1-3 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl <bi...@debian.org> (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 04 Feb 2020 00:11:55 +0100 Source: systemd Architecture: source Version: 244.1-3 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintain...@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org> Closes: 946196 950409 950489 950533 Changes: systemd (244.1-3) unstable; urgency=medium . * Update documentation regarding network interface naming. Document that 73-usb-net-by-mac.link needs to be masked together with 99-default.link if one wants to disable the systemd naming scheme and keep the kernel-provided names. (Closes: #946196) * Update debian/rules clean target to remove all Python bytecode * Update systemd package description. Recommend init=/lib/systemd/systemd instead of init=/bin/systemd. The latter is just a compat symlink which might go away eventually. * shared/dropin: fix assert for invalid drop-in. Fixes an assertion when running systemctl cat on inexistent unit templates. (Closes: #950489) * core: call dynamic_user_acquire() only when 'group' is non-null. Fixes an assertion in systemd which could happen if a unit is reloaded and the unit is in bad-setting state. (Closes: #950409) * Don't fail upgrade if /proc is not mounted. Applying ACLs on /var/log/journal via systemd-tmpfiles requires a mounted /proc. Skip this step if /proc is not available, e.g. in a chroot. (Closes: #950533) Checksums-Sha1: 8e592a9204ca176cca8c03f45b5fed60b960dfd5 5021 systemd_244.1-3.dsc c254fc5d6d7317add73bd14e461c65070cc74ed2 148272 systemd_244.1-3.debian.tar.xz 1e65b6355e2e2506acad10fd8c00dee3ce977125 9739 systemd_244.1-3_source.buildinfo Checksums-Sha256: 9661c9af6278cddfc620c3f9c93ce7673795860d06294470ff3248436f61187e 5021 systemd_244.1-3.dsc 9e3284cd4c77721cff8bde5979c78cb0b8ed486a3d9d7419285279fff93fbdaa 148272 systemd_244.1-3.debian.tar.xz f853df49a574cd0b578c84496ef1514031f458aea8871d54ad4200abb9f29f3e 9739 systemd_244.1-3_source.buildinfo Files: 27a975921ef2225843e3714b1f129c45 5021 admin optional systemd_244.1-3.dsc d77371db84cc3024b3838f839c3c6ac0 148272 admin optional systemd_244.1-3.debian.tar.xz c5cd8a7337fa24bf5820703c33dff15c 9739 admin optional systemd_244.1-3_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAl44qRwACgkQauHfDWCP ItxWIQ/+ItCqAMC5bahxOFxYmyvTdrbGyCunnHP/6MYrE6LYeBDqF/ynSNmAvu+z 9pll54bDLJYGprKJrkT5a5Dy7Rep+AS4hjES8xOUYDkyMXMhG8JiBcjoCujZDah6 JyYt7iADx7Nimipkv79el5ClpVNL0OurvSpzX8s2xLwW3UpBmYDIrhn4m8+SVJPZ v4hnopCpRl1RdNokged74QkMEBfqdfq8YR9/1RpHndbNNZdZjbRa7IV/QzOavaiR shQzPoYob3poYLujsPjFqNGE1x2BX11iDNDYRleYZ7skBu5TcU5DsJmrzQOEbwCQ twhUOnPAEVnCoehf48hsU6rWDnFdy5AmjIcGPjT/wO8zqm5Sef+4iIhcDr/YzyOd AbJGMn5RZc5UK7EWImxHPFLTfMPBs6uREO0N/OF7ofyCT32aNWZHsSKqnio/alIC dgu7urEYTf3id0FP9EKpEBjun0Onq4Y1mb6hiViO00MlZIwtgFhiRwdkm+qrm7HP NCx9eFAkgQJwtx4URnbBUxHOdZcRsz/upgv+Eacq1vdS35A96WBh5qllD+LoC4oJ H5iK2JBB/gWAIjkAWSBMgp0eioNJryMjmYaE3M3i4X2yivvu70EsJcCZpb2lIXTx ON2nPKgaixZpr1o0UBmhFetYJsj7y7ZCYyw2TgUq/9xAZc7py10= =xnRv -----END PGP SIGNATURE-----
--- End Message ---
