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:
~
>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, literal
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 did
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,
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
On 2021-09-29 22:07, shichimohedron wrote:
> >Is this about libcrypto.so.1 or libcrypt.so.1?
> This is about libcrypt.so.1. Sorry for mistyping the filename.
>
> >Does it still happen after something like this?
>
> > mv /usr/sbin/ldconfig /usr/sbin/ldconfig.old
> > cp -a /bin/true /usr/sbin/ldcon
>Is this about libcrypto.so.1 or libcrypt.so.1?
This is about libcrypt.so.1. Sorry for mistyping the filename.
>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 .../libcrypt1_*.deb
I tried this out, and
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 .../libcrypt1_
On Sep 29, Flying Sea Buckthorn wrote:
> Curiuosly enough, I found out that the symlink that should have been
> pointing to crypto library (/lib/x86_64-linux-gnu/libcrypto.so.1 ->
> libcrypto.so.1.1.0) pointed to libpthread.so.1 instead since upgrade.
Is this about libcrypto.so.1 or libcrypt.so
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, have
installed libcrypt1 package.
Curiuosly enough, I found out th
10 matches
Mail list logo
