On Tue, 20 Sep 2022 01:11:43 +0200 Vincent Danjean <vdanj...@debian.org> wrote: > Hi, > > Le 19/09/2022 à 23:49, Luca Boccassi a écrit : > > On Mon, 2022-09-19 at 22:29 +0100, Luca Boccassi wrote: > >> On Mon, 19 Sep 2022 22:08:48 +0200 Vincent Danjean > >> <vdanj...@debian.org> wrote: > >>> 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) > >> > >> What was the order of upgrades? Can you share the full apt log? > >> Are you sure the problem was not there beforehand? > > > > Also can you run 'debsums -c' and paste the output? > > Oh yes. I'm back online after having rebooted after the upgrade. > It took me several hours to get a bootable system again (hence, > I will upgrade the severity to serious juste after this mail). > > So, first, at reboot, I got the emergency shell of systemd. > It reports timeout when waiting for most (all?) devices. > Once in the shell, all /dev/... files reported by systemd were > there. And "mount -a" correctly mounts all filesystems that > systemd was enable to. > I "fixed" this by booting on a debian rescue disk and > running (from memory): > apt install --reinstall systemd-container systemd-sysv systemd-ui udev cryptsetup cryptsetup-bin cryptsetup-initramfs basefiles > > After this, I've been able to boot to a text-mode only system. > No gdm3 graphical prompt. > So, I've run deb5sums. Here is the result of > debsums |& cat > /tmp/debsum2.txt & > cat /tmp/debsum2.txt | grep -v ' OK$' > /tmp/debsum2-missing.txt > The 3 FAILED lines are "correct" (I manually modified these files long before) > But lots of /lib/* files was missing. > > I used sed/grep/... to reinstall all cited packages. > Then, with a reboot, I'm back again. > > I will re-run debsums (it seems that the "|&" polute the output > a litle bit, I want to be sure I reinstalled all required packages)
Thanks for the logs, it looks like it's only file under /lib/systemd/system/ that went missing - can you find them anywhere else on the system? Directories are merged recursively if they exist in both hierarchies, so I guess you had something that installs files in /usr/lib/systemd/system/ and something went horribly wrong somewhere. We don't delete files, so I'm thinking they might have been moved to the wrong place. We can add debsums -c before/after the conversion, so that if this happens again there's a clear message immediately. But this is very strange, I've never seen this reported in Debian or Ubuntu in ~5 years. -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
