Re: libcrypt1: symlink points to libpthread

2021-09-30 Thread shichimohedron
On Thursday, September 30th, 2021 at 12:08 PM, Aurelien Jarno wrote: > It could be that this libpthread.so.1 file is actually a copy of an old > > libcrypt.so.1. It's something you can check with: > > readelf --dynamic /lib/x86_64-linux-gnu/libpthread.so.1 | grep SONAME And it actually is:

Re: libcrypt1: symlink points to libpthread

2021-09-30 Thread Marco d'Itri
Thank you Aurelien for your help, so this is user error. On Sep 30, shichimohedron wrote: > > On Thursday, September 30th, 2021 at 12:08 PM, Aurelien Jarno > wrote: > > > It could be that this libpthread.so.1 file is actually a copy of an old > > > > libcrypt.so.1. It's something you can

Re: libcrypt1: symlink points to libpthread

2021-09-30 Thread Aurelien Jarno
On 2021-09-30 15:46, shichimohedron wrote: > >Can you please try to call /usr/sbin/ldconfig.old to check if the wrong > link is recreated? That's needed to confirm if ldconfig is the culprit > here. > >Can you confirm it's libpthread.so.1 and not libpthread.so.0? If so can > you please tell how

Re: libcrypt1: symlink points to libpthread

2021-09-30 Thread shichimohedron
>Can you please try to call /usr/sbin/ldconfig.old to check if the wrong link is recreated? That's needed to confirm if ldconfig is the culprit here. >Can you confirm it's libpthread.so.1 and not libpthread.so.0? If so can you please tell how did you install that file? Here is a shell log,

Re: libcrypt1: symlink points to libpthread

2021-09-30 Thread Aurelien Jarno
On 2021-09-29 10:33, Flying Sea Buckthorn wrote: > Package: libcrypt1 > Version: 1:4.4.18-4 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: shichimohed...@protonmail.com > > Dear Maintainer, > > Recently I have upgraded from Buster to Bullseye and, among other things,

Re: Bug#995308: libcrypt1: symlink points to libpthread

2021-09-30 Thread Aurelien Jarno
On 2021-09-30 02:45, Marco d'Itri wrote: > Maybe then the glibc people know what could make ldconfig create a link > to the wrong library. I don't see how that could happen. ldconfig uses the SONAME entry to create the links. First we have to get confirmed that ldconfig is the culprit. > On Sep

Re: Bug#995308: libcrypt1: symlink points to libpthread

2021-09-29 Thread Marco d'Itri
Maybe then the glibc people know what could make ldconfig create a link to the wrong library. On Sep 30, shichimohedron wrote: > >Does it still happen after something like this? > > > mv /usr/sbin/ldconfig /usr/sbin/ldconfig.old > > cp -a /bin/true /usr/sbin/ldconfig > > dpkg -i