Mapping bullseye to stable.
Mapping stable to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 30 Sep 2021 22:47:49 +0200
Source: glibc
Architecture: source
Version: 2.31-13+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: GNU Libc
glibc_2.31-13+deb11u1_source.changes uploaded successfully to localhost
along with the files:
glibc_2.31-13+deb11u1.dsc
glibc_2.31-13+deb11u1.debian.tar.xz
glibc_2.31-13+deb11u1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Aurelien Jarno pushed new tag debian/2.31-13+deb11u1 at GNU Libc Maintainers /
glibc
--
View it on GitLab:
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.31-13+deb11u1
You're receiving this email because of your account on salsa.debian.org.
Aurelien Jarno pushed to branch bullseye at GNU Libc Maintainers / glibc
Commits:
2d44506b by Aurelien Jarno at 2021-09-30T22:48:07+02:00
releasing package glibc version 2.31-13+deb11u1
- - - - -
1 changed file:
- debian/changelog
View it on GitLab:
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:
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
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
>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,
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
10 matches
Mail list logo