Spoke too soon, usrmerge broke my system worse than I could have imagined, /usr/bin/init went to systemd but in the old place /lib/systemd (the lib folder was either empty or not there, likely because of the usrmerge), fixing that didn't really do much as I suspect a whole bunch of other stuff was moved without the system really knowing where it all was. (I could have sat there moving stuff around or symlinking to hopefully solve the problem but in the end it seemed like alot of work)
So I figured it was easier to reinstall than try and figure out what went wrong at that point. My suspicion is that trying to resolve that GLOB issue caused me to inadvertently get it so usrmerge ran (which honestly was what I wanted so I could get apt to work again) when it probably shouldn't have, a whole bunch of libraries stopped working because they couldn't be found and then I couldn't login to the machine anymore because bash couldn't run. ________________________________ From: Marco d'Itri Sent: Monday, June 12, 2023 12:08 To: Lawrence Bayly Cc: 1037...@bugs.debian.org Subject: Re: Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close On Jun 12, Lawrence Bayly <lawrenceba...@hotmail.com> wrote: > root@cg-sg:/tmp/coreutils/bin# ldd /bin/cp > not a dynamic executable > root@cg-sg:/tmp/coreutils/bin# file /bin/cp > /bin/cp: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically > linked, interpreter /lib64/ld-linux-x86-64.so.2, > BuildID[sha1]=e8f03b272b3dbd03cc8748cf2b52744a58d0cf5c, for GNU/Linux 3.2.0, > stripped This is the correct file. Is your ldd weird then? It should look like this: -rwxr-xr-x 1 root root 5398 Apr 10 10:35 /usr/bin/ldd Please also report the output of: - dpkg -l libc-bin - which ldd - ldd --version -- ciao, Marco
