Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-13 Thread Marco d'Itri
retitle -1 1037362 usrmerge: fails to run ldd On Jun 13, Lawrence Bayly wrote: > 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

Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-13 Thread Lawrence Bayly
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

Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-12 Thread Marco d'Itri
On Jun 12, Lawrence Bayly 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, >

Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-12 Thread Lawrence Bayly
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

Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-12 Thread Marco d'Itri
On Jun 12, Lawrence Bayly 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.

Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-12 Thread Lawrence Bayly
Hi Marco, 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 root@cg-sg:~# ls -l /bin/cp -rwxr-xr-x 1

Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-12 Thread Marco d'Itri
On Jun 12, Lawrence Bayly wrote: > The output is as follows:- > > root@cg-sg:~# ldd /bin/cp >not a dynamic executable Weird. Is /bin/cp a script then? Where does it come from? -- ciao, Marco

Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-12 Thread Marco d'Itri
On Jun 12, Lawrence Bayly wrote: > FATAL ERROR: > Can't close(GLOB(0x564e905c3aa0)) filehandle: '' at > /usr/lib/usrmerge/convert-usrmerge line 222 This is not an open file but the call to ldd, the default error message is stupid. Please report the output and exit status of "ldd /bin/cp". --

Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-12 Thread Lawrence Bayly
Package: usrmerge Version: 35 Severity: important Dear Maintainer, * What led up to the situation? I tried to upgrade debian to Debian 12 from Debian 11 on a Linode VPS. * What exactly did you do (or not do) that was effective (or ineffective)? Cannot upgrade because of usrmerge