Your message dated Fri, 22 Jan 2016 06:20:14 +0000 with message-id <[email protected]> and subject line Bug#810860: fixed in usrmerge 8 has caused the Debian Bug report #810860, regarding usrmerge: System cannot be rebooted after partial usrmerge installation 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.) -- 810860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810860 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: usrmerge Version: 6 Severity: critical Justification: breaks the whole system Dear Maintainer, I installed usrmerge on a system to try it out, and ended up with system that could not be rebooted. I'll try to outline the status as best I recall in the hopes that you can recreate the issue. * What led up to the situation? I installed usrmerge, and got the following during configuration: -------------------- Setting up usrmerge (6) ... WARNING: renaming /bin/ (for the purpose of replacing it with a symlink to /usr/bin/) has failed with the EBUSY error. This is probably caused by a systemd service started with the ProtectSystem option. Before running again this program you will need to stop the relevant daemon(s) or reboot the system. Do not install or update other Debian packages until the program has been run successfully. WARNING: renaming /sbin/ (for the purpose of replacing it with a symlink to /usr/sbin/) has failed with the EBUSY error. This is probably caused by a systemd service started with the ProtectSystem option. Before running again this program you will need to stop the relevant daemon(s) or reboot the system. Do not install or update other Debian packages until the program has been run successfully. WARNING: renaming /lib/ (for the purpose of replacing it with a symlink to /usr/lib/) has failed with the EBUSY error. This is probably caused by a systemd service started with the ProtectSystem option. Before running again this program you will need to stop the relevant daemon(s) or reboot the system. Do not install or update other Debian packages until the program has been run successfully. WARNING: renaming /lib64/ (for the purpose of replacing it with a symlink to /usr/lib64/) has failed with the EBUSY error. This is probably caused by a systemd service started with the ProtectSystem option. Before running again this program you will need to stop the relevant daemon(s) or reboot the system. Do not install or update other Debian packages until the program has been run successfully. dpkg: error processing package usrmerge (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: usrmerge -------------------- I could not figure out which processes/daemons in particular were causing the errors. At this point, I examined the disk layout, and noticed that basically everything* in /{bin,sbin,lib} had been moved to /usr/{bin,sbin,lib}, and replaced with symlinks in /{bin,sbin,lib}, but /{bin,sbin,lib} still existed as real directories (not symlinks). (* - I noticed two exceptions in /lib, both of which were directories, but unfortunately I can't remember exactly what they were, and the history is beyond the top of my terminal buffer. My best guess is that they were systemd and x86_64-linux-gnu, but again, I'm not certain of that.) Since I couldn't figure out which daemon was causing the problem, I rebooted the system as suggested in the usrmerge configure error messages. It didn't come back up: it failed to start with an error that /sbin/init was not found on the disk. Oddly, however, I could run ls /sbin/init which *did* show an existing symlink and target. I tried rebooting with init=/usr/sbin/init, but that also did not work. Eventually I got the system to boot using init=/usr/lib/systemd/systemd after which a dpkg --configure usrmerge completed the merge (turning /{bin,sbin/lib} into symlinks). After this, rebooting without specifying init= was successful. Please let me know if there's any other information I can provide to keep this from happening to others. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) 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-1 usrmerge recommends no packages. usrmerge suggests no packages. -- no debconf information -- debsums errors found: debsums: can't check usrmerge file /usr/share/doc/usrmerge/changelog.gz (Wide character in subroutine entry)
--- End Message ---
--- Begin Message ---Source: usrmerge Source-Version: 8 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: SHA1 Format: 1.8 Date: Fri, 22 Jan 2016 07:07:50 +0100 Source: usrmerge Binary: usrmerge Architecture: source all Version: 8 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri <[email protected]> Changed-By: Marco d'Itri <[email protected]> Description: usrmerge - Convert the system to everything-in-usr Closes: 810860 811317 Changes: usrmerge (8) unstable; urgency=medium . * Added Breaks with older cruft-ng and initramfs-tools. (Closes: #810860, #811317) * dpkg.cfg: removed coreutils. * Added a conflict with older open-vm-tools. Checksums-Sha1: b2021f9cdcf3b0a52bff58ce8c287e9b04d8652c 1309 usrmerge_8.dsc 87d0fae1596e146a6bdf811ce3373ae08c65f533 10052 usrmerge_8.tar.xz 94cd2fe1e470e973c733a57741c328dedc59b6b6 9328 usrmerge_8_all.deb Checksums-Sha256: 9fd9bd9d6d014d6e7d4ce51cec62e7e728e51d7eabc11b79f7f6511a1b964cac 1309 usrmerge_8.dsc f70d88179b310003278fccec1be78954b052afd2da53bc8af8a0926a87d7b5a5 10052 usrmerge_8.tar.xz 687b0e13fd60d5f8b0be61fb18c03672858077c9ed187d16f6a37f65436e4e8c 9328 usrmerge_8_all.deb Files: 0b6ec78b0bc453ff43d962f24d2f2e5a 1309 admin extra usrmerge_8.dsc a6ec8ec7b0922ac4d207570137c192a4 10052 admin extra usrmerge_8.tar.xz 1a05078cf071428dd451b806897b418f 9328 admin extra usrmerge_8_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQGcBAEBAgAGBQJWocgmAAoJECv1pcEixPekwWUL/R4rN1+LTqZUEZrp2l9712FK VLyjy1mUEQ2bs0apFHVrWWwp1Y3s8hj3COQWNNFqRZ9+BbluebZxVxrhkK9+fvK1 9FcLlCYhFcwZLXsP163buungmEaSp5aq3Musek8FBuHrw4C56E4ZnW2J0Q/ZrWab 2bQqWtxU1MkqKmp1J0j6PQmrf7m0fgD4WENCoDqnqUn5BlRJ1NIK3tPqNxMV3VLD lA9Ly8TLCRx/p/Qq+O2DoWi/oOlSHlA9ujrUrlQrCp3AloI+kOrySuCLCHy8p+aB nYKd4qJ0lLtkmbJwzhqzlMbdthkZcRMm3U9/ZxzSJWOPJtdgIyzdHC2gJCnuh9tE 5zddwCV6zVsiOiY/X9ob2J21GtlAKpFwv9WPPUusTuUzGmRa9UOS2zTL2mmILSui ce2Ot6Fk4kGsE+0pM6DKt/JgzuFE4IeAz+szvDhHbhmLuzcvajizDYdTRK8s2JxF JSs6X07O2DijWtWq/i2uO9O3LZCxNdm9oe0nxiFnfQ== =E1bF -----END PGP SIGNATURE-----
--- End Message ---
