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
control: reassign -1 gcl
control: affects -1 libc6
control: retitle -1 gcl: fails to start with glibc 2.33
control: forwarded -1 https://savannah.gnu.org/bugs/index.php?60161
control: patch -1 + upstream
control: patch -1 + patch
Hi,
On 2021-09-29 10:51, Andreas Kloeckner wrote:
> Package: libc6
Processing control commands:
> reassign -1 gcl
Bug #995323 [libc6] libc6: 2.33-0experimental2 breaks maxima
Bug reassigned from package 'libc6' to 'gcl'.
No longer marked as found in versions glibc/2.33-0experimental2.
Ignoring request to alter fixed versions of bug #995323 to the same values
Package: libc6
Version: 2.33-0experimental2
Severity: normal
Dear Maintainer,
Upgrading libc6 to 2.33-0experimental2 causes maxima to fail at startup
with the message:
The assertion realpath(s,o) on line 475 of main.c in function mbin failed:
Invalid argument[1]468085 abort (core dumped)
4 matches
Mail list logo
