Yep I came to that conclusion too, getting it to install has become the
challenge as apt is not happy and will just run that usrmerge which will fail,
so I set about going through that process of reinstalling it using dpkg. This
is what I result with:-
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
Trying again gives me the same error:-
FATAL ERROR:
Can't close(GLOB(0x5577769d56e8)) filehandle: '' at
/usr/lib/usrmerge/convert-usrmerge line 222
You can try correcting the errors reported and running again
/usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
Do not install or update other Debian packages until the program
has been run successfully.
There is only that one file (ld-linux-x86-64.so.2) in /lib64, I tried to move
it to see if it would use something else and that did not go well, couldn't run
any commands after that, have to boot into a rescue mode to move it back.
Thanks,
Lawrence
________________________________
From: Marco d'Itri
Sent: Monday, June 12, 2023 08:37
To: Lawrence Bayly; [email protected]
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 <[email protected]> wrote:
> root@cg-sg:~# 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, for GNU/Linux 2.6.32,
> BuildID[sha1]=3a0bad79264ea6b37c1b8d4dd2b206b8001097dc, stripped
Interesting. I am still trying to figure out why ldd does not work on
it.
> The upgrade did kinda go badly and I did lose libcrypt.so.1 at one
> point earlier in the upgrade for some odd reason which meant perl
> wouldn't run (and that script wouldn't run either as it depended on
> perl) until I copied it back, so it potentially could be that /bin/cp
> is also an outdated binary.
This happened because you upgraded while skipping a release, and this is
not supported.
> Should I copy /bin/cp from another debian system and try again?
Reinstalling the coreutils package should be enough, but I wonder at
this point what else is broken on your system.
--
ciao,
Marco
