Your message dated Thu, 29 Sep 2022 04:19:44 +0000 with message-id <[email protected]> and subject line Bug#1020312: fixed in usrmerge 32 has caused the Debian Bug report #1020312, regarding usrmerge: files in a nested symlinked directory in /lib/foo/ are not moved to /usr/lib/foo/ 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 [email protected] immediately.) -- 1020312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020312 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: usrmerge Version: 30+nmu2 Severity: serious Justification: break other packages upgrades When I upgraded my system to current unstable, usrmerge has been pulled-in due to the init-system-helpers dependency. But one package fails to upgrade (fetchmail) due to /lib/systemd/system/sysinit.target missing. Reinstalling the systemd package fixes the problem. Feel free to reassign to systemd if you think the problem comes from it but usrmerge is my first guess (without any specific evidence) Note that systemd does *not* upgrade today (see at the end of the commands) vdanjean@eyak:~$ sudo apt upgrade [...] Paramétrage de fetchmail (6.4.33-2) ... insserv: warning: current stop runlevel(s) (empty) of script `fetchmail' overrides LSB defaults (0 1 6). Failed to restart fetchmail.service: Unit sysinit.target not found. invoke-rc.d: initscript fetchmail, action "restart" failed. ○ fetchmail.service - LSB: init-Script for system wide fetchmail daemon Loaded: loaded (/etc/init.d/fetchmail; generated) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) sept. 19 20:27:35 eyak systemd[1]: Starting LSB: init-Script for system wide fetchmail daemon... sept. 19 20:27:35 eyak fetchmail[2556]: Not starting fetchmail daemon, disabled via /etc/default/fetchmail. sept. 19 20:27:35 eyak systemd[1]: Started LSB: init-Script for system wide fetchmail daemon. sept. 19 21:35:02 eyak systemd[1]: Stopping LSB: init-Script for system wide fetchmail daemon... sept. 19 21:35:02 eyak fetchmail[22013]: Not starting fetchmail daemon, disabled via /etc/default/fetchmail. sept. 19 21:35:02 eyak systemd[1]: fetchmail.service: Deactivated successfully. sept. 19 21:35:02 eyak systemd[1]: Stopped LSB: init-Script for system wide fetchmail daemon. dpkg: erreur de traitement du paquet fetchmail (--configure) : installed fetchmail package post-installation script subprocess returned error exit status 1 Des erreurs ont été rencontrées pendant l'exécution : fetchmail vdanjean@eyak:~$ sudo systemctl cat fetchmail # /run/systemd/generator.late/fetchmail.service # Automatically generated by systemd-sysv-generator [Unit] Documentation=man:systemd-sysv-generator(8) SourcePath=/etc/init.d/fetchmail Description=LSB: init-Script for system wide fetchmail daemon Before=multi-user.target Before=multi-user.target Before=multi-user.target Before=graphical.target After=network-online.target After=remote-fs.target After=mail-transport-agent.target After=postfix.service After=exim4.service After=nss-lookup.target Wants=network-online.target [Service] Type=forking Restart=no TimeoutSec=5min IgnoreSIGPIPE=no KillMode=process GuessMainPID=no RemainAfterExit=yes SuccessExitStatus=5 6 ExecStart=/etc/init.d/fetchmail start ExecStop=/etc/init.d/fetchmail stop vdanjean@eyak:~$ sudo systemctl restart fetchmail Failed to restart fetchmail.service: Unit sysinit.target not found. vdanjean@eyak:~$ sudo systemctl status sysinit.target ● sysinit.target Loaded: not-found (Reason: Unit sysinit.target not found.) Active: active since Mon 2022-09-19 20:27:32 CEST; 1h 16min ago Until: Mon 2022-09-19 20:27:32 CEST; 1h 16min ago sept. 19 20:27:32 eyak systemd[1]: Reached target System Initialization. vdanjean@eyak:~$ sudo systemctl daemon-reexec vdanjean@eyak:~$ sudo systemctl status sysinit.target ● sysinit.target Loaded: not-found (Reason: Unit sysinit.target not found.) Active: active since Mon 2022-09-19 20:27:32 CEST; 1h 17min ago Until: Mon 2022-09-19 20:27:32 CEST; 1h 17min ago sept. 19 20:27:32 eyak systemd[1]: Reached target System Initialization. vdanjean@eyak:~$ dpkg -S sysinit.target udev: /lib/systemd/system/sysinit.target.wants/systemd-udevd.service systemd: /lib/systemd/system/sysinit.target.wants/systemd-sysctl.service systemd: /lib/systemd/system/sysinit.target.wants/dev-hugepages.mount systemd: /lib/systemd/system/sysinit.target.wants/systemd-random-seed.service systemd: /lib/systemd/system/sysinit.target.wants/systemd-sysusers.service systemd: /lib/systemd/system/sysinit.target.wants/veritysetup.target systemd: /lib/systemd/system/sysinit.target.wants/systemd-machine-id-commit.service udev, systemd: /lib/systemd/system/sysinit.target.wants udev: /lib/systemd/system/sysinit.target.wants/systemd-udev-trigger.service systemd: /lib/systemd/system/sysinit.target.wants/systemd-journald.service systemd: /lib/systemd/system/sysinit.target.wants/systemd-update-utmp.service systemd: /lib/systemd/system/sysinit.target.wants/sys-kernel-debug.mount systemd: /lib/systemd/system/sysinit.target.wants/sys-kernel-config.mount systemd: /lib/systemd/system/sysinit.target systemd: /lib/systemd/system/sysinit.target.wants/dev-mqueue.mount systemd: /lib/systemd/system/sysinit.target.wants/sys-fs-fuse-connections.mount systemd: /lib/systemd/system/sysinit.target.wants/systemd-ask-password-console.path systemd: /lib/systemd/system/sysinit.target.wants/systemd-binfmt.service systemd: /lib/systemd/system/sysinit.target.wants/systemd-tmpfiles-setup.service systemd: /lib/systemd/system/sysinit.target.wants/sys-kernel-tracing.mount systemd: /lib/systemd/system/sysinit.target.wants/proc-sys-fs-binfmt_misc.automount systemd: /lib/systemd/system/sysinit.target.wants/systemd-journal-flush.service systemd: /lib/systemd/system/sysinit.target.wants/cryptsetup.target systemd: /lib/systemd/system/sysinit.target.wants/integritysetup.target systemd: /lib/systemd/system/sysinit.target.wants/systemd-modules-load.service systemd: /lib/systemd/system/sysinit.target.wants/systemd-repart.service systemd: /lib/systemd/system/sysinit.target.wants/systemd-tmpfiles-setup-dev.service systemd: /lib/systemd/system/sysinit.target.wants/kmod-static-nodes.service vdanjean@eyak:~$ less /lib/systemd/system/sysinit.target /lib/systemd/system/sysinit.target: Aucun fichier ou dossier de ce type vdanjean@eyak:~$ sudo apt install --reinstall systemd [...] Préparation du dépaquetage de .../systemd_251.4-3_amd64.deb ... Dépaquetage de systemd (251.4-3) sur (251.4-3) ... Paramétrage de fetchmail (6.4.33-2) ... insserv: warning: current stop runlevel(s) (empty) of script `fetchmail' overrides LSB defaults (0 1 6). Paramétrage de systemd (251.4-3) ... Traitement des actions différées (« triggers ») pour dbus (1.14.0-2) ... Traitement des actions différées (« triggers ») pour man-db (2.10.2-3) ... [...] vdanjean@eyak:~$ ls -l /lib/systemd/system/sysinit.target -rw-r--r-- 1 root root 566 8 août 11:10 /lib/systemd/system/sysinit.target vdanjean@eyak:~$ cat /var/log/dpkg.log | grep 2022-09-19 | grep systemd 2022-09-19 21:36:59 status triggers-pending systemd:amd64 251.4-3 2022-09-19 21:40:47 trigproc systemd:amd64 251.4-3 <none> 2022-09-19 21:40:47 status half-configured systemd:amd64 251.4-3 2022-09-19 21:40:47 status installed systemd:amd64 251.4-3 2022-09-19 21:56:16 upgrade systemd:amd64 251.4-3 251.4-3 2022-09-19 21:56:16 status half-configured systemd:amd64 251.4-3 2022-09-19 21:56:16 status unpacked systemd:amd64 251.4-3 2022-09-19 21:56:16 status half-installed systemd:amd64 251.4-3 2022-09-19 21:56:16 status unpacked systemd:amd64 251.4-3 2022-09-19 21:56:17 configure systemd:amd64 251.4-3 <none> 2022-09-19 21:56:17 status unpacked systemd:amd64 251.4-3 2022-09-19 21:56:17 status half-configured systemd:amd64 251.4-3 2022-09-19 21:56:17 status installed systemd:amd64 251.4-3 vdanjean@eyak:~$ => no systemd upgrade (only the reinstall to fix the problem). Where does this bug come from? Is there other packages I need to reinstall? Regards, Vincent -- Package-specific info: -- System Information: Debian Release: bookworm/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel, mipsel Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages usrmerge depends on: ii libfile-find-rule-perl 0.34-2 ii perl 5.34.0-5 usrmerge recommends no packages. usrmerge suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: usrmerge Source-Version: 32 Done: Marco d'Itri <[email protected]> We believe that the bug you reported is fixed in the latest version of usrmerge, 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 [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco d'Itri <[email protected]> (supplier of updated usrmerge 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 [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 29 Sep 2022 05:51:16 +0200 Source: usrmerge Architecture: source Version: 32 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri <[email protected]> Changed-By: Marco d'Itri <[email protected]> Closes: 1020312 1020549 Changes: usrmerge (32) unstable; urgency=medium . * convert-usrmerge: fix handling the link X directory case. The case in which the source and destination are a symlink and a directory (or a directory and a symlink) actually was never handled. (Closes: #1020312) * Updated the versioned conflict with libpng12-0. (Closes: #1020549) * Relabel for SELinux the newly created directories and /etc/shells, courtesy of Christian Göttsche. Checksums-Sha1: 0703e6538c9d00bc1c9d75b8235c27c48b544fa0 981 usrmerge_32.dsc 63db9306d99e36a7e69cf62bcfc812a64a496eae 13640 usrmerge_32.tar.xz 4f5adae21040f2ca6864d466191abf593baf4b16 5421 usrmerge_32_amd64.buildinfo Checksums-Sha256: 1f500570b649129ee82f113f52f0e9ccac67258a599a34f93d3a253cdd487f99 981 usrmerge_32.dsc fd3971bd0a97697ff13d1b75a9b551bb2cad8e8d4d92334444a87eb5463ec04d 13640 usrmerge_32.tar.xz 4d2a87f313cc784125cc96ca2a64e54ce77e052b04a903d48a9db61ebfda002b 5421 usrmerge_32_amd64.buildinfo Files: 59362392fb2049d65e6f06d84bf9570d 981 admin optional usrmerge_32.dsc 6862a5ce2d8fef65eefae6cd401d0f3e 13640 admin optional usrmerge_32.tar.xz 712431ff703a04f7c4f0ab5c8e0f56b7 5421 admin optional usrmerge_32_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCYzUWqAAKCRDLPsM64d7X gdu4AQDKqV3+FfPj4h4qob+5osT4VRmiZaW9+SkThCdW+Dxp8wD9HEVHS8N35QGs ShV6N5Qj98ziGeBsR2UlpkEDhZ+1CwA= =uQ/p -----END PGP SIGNATURE-----
--- End Message ---
