Processing control commands:
> tag -1 - pending
Bug #882255 [libc6-amd64] libc6-amd64: Multilib causes catastrophic system
failure during upgrade to libc 2.25
Removed tag(s) pending.
--
882255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882255
Debian Bug Tracking System
Contact
control: tag -1 - pending
On 2017-12-02 03:34, Mikulas Patocka wrote:
>
>
> On Sun, 26 Nov 2017, Aurelien Jarno wrote:
>
> > > > You mean that even now running 'ldconfig' followed by 'ldd /bin/true'
> > > > will give you
> > > > libc.so.6 => /lib64/libc.so.6
> > > > instead of
> > > >
On Sun, 26 Nov 2017, Aurelien Jarno wrote:
> > > You mean that even now running 'ldconfig' followed by 'ldd /bin/true'
> > > will give you
> > > libc.so.6 => /lib64/libc.so.6
> > > instead of
> > > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
> > > ?
> >
> > Yes.
> > # ldd /bin/true
> >
On 2017-11-26 09:21, Bastian Blank wrote:
> On Sun, Nov 26, 2017 at 09:13:52AM +0100, Bastian Blank wrote:
> > It seems that ldconfig does not force the collation to a value that
> > would make it use the claimed sorting.
This is indeed correct, that said it's not true for the locale of the
On Sun, Nov 26, 2017 at 09:13:52AM +0100, Bastian Blank wrote:
> It seems that ldconfig does not force the collation to a value that
> would make it use the claimed sorting.
ldconfig:
-> setlocale (LC_ALL, "")
-> glob()
-> qsort(strcoll-equiv)
Other occurances of similar bugs:
On Sun, Nov 26, 2017 at 01:03:58AM +0100, Aurelien Jarno wrote:
> I am still unable to reproduce this problem. On my system
> lib/x86_64-linux-gnu/ is preferred over lib64. ldconfig uses glob to to
> interpret the "*.conf" in /etc/ld.so.conf, so the files are sorted
> alphabetically and thus the
On 2017-11-21 01:43, Mikulas Patocka wrote:
>
>
> On Tue, 21 Nov 2017, Aurelien Jarno wrote:
>
> > On 2017-11-21 01:01, Mikulas Patocka wrote:
> > >
> > >
> > > On Tue, 21 Nov 2017, Aurelien Jarno wrote:
> > >
> > > > On 2017-11-21 00:12, Mikulas Patocka wrote:
> > > > >
> > > > >
> > > >
On Tue, 21 Nov 2017, Aurelien Jarno wrote:
> On 2017-11-21 01:01, Mikulas Patocka wrote:
> >
> >
> > On Tue, 21 Nov 2017, Aurelien Jarno wrote:
> >
> > > On 2017-11-21 00:12, Mikulas Patocka wrote:
> > > >
> > > >
> > > > On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> > > >
> > > > > On
On 2017-11-21 01:01, Mikulas Patocka wrote:
>
>
> On Tue, 21 Nov 2017, Aurelien Jarno wrote:
>
> > On 2017-11-21 00:12, Mikulas Patocka wrote:
> > >
> > >
> > > On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> > >
> > > > On 2017-11-20 19:13, Mikulas Patocka wrote:
> > > > > Package: libc6-amd64
On Tue, 21 Nov 2017, Aurelien Jarno wrote:
> On 2017-11-21 00:15, Mikulas Patocka wrote:
> >
> >
> > On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> >
> > > On 2017-11-20 21:58, Mikulas Patocka wrote:
> > > >
> > > >
> > > > On Mon, 20 Nov 2017, Samuel Thibault wrote:
> > > >
> > > > >
On Tue, 21 Nov 2017, Aurelien Jarno wrote:
> On 2017-11-21 00:12, Mikulas Patocka wrote:
> >
> >
> > On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> >
> > > On 2017-11-20 19:13, Mikulas Patocka wrote:
> > > > Package: libc6-amd64
> > > > Version: 2.25-1
> > > > Severity: critical
> > > >
On 2017-11-21 00:12, Mikulas Patocka wrote:
>
>
> On Mon, 20 Nov 2017, Aurelien Jarno wrote:
>
> > On 2017-11-20 19:13, Mikulas Patocka wrote:
> > > Package: libc6-amd64
> > > Version: 2.25-1
> > > Severity: critical
> > > Justification: breaks the whole system
> > >
> > > Dear Maintainer,
> >
On 2017-11-21 00:15, Mikulas Patocka wrote:
>
>
> On Mon, 20 Nov 2017, Aurelien Jarno wrote:
>
> > On 2017-11-20 21:58, Mikulas Patocka wrote:
> > >
> > >
> > > On Mon, 20 Nov 2017, Samuel Thibault wrote:
> > >
> > > > Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > > > >
On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> On 2017-11-20 21:58, Mikulas Patocka wrote:
> >
> >
> > On Mon, 20 Nov 2017, Samuel Thibault wrote:
> >
> > > Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> On 2017-11-20 19:13, Mikulas Patocka wrote:
> > Package: libc6-amd64
> > Version: 2.25-1
> > Severity: critical
> > Justification: breaks the whole system
> >
> > Dear Maintainer,
> >
> > *** Reporter, please consider answering these questions,
On 2017-11-20 19:13, Mikulas Patocka wrote:
> Package: libc6-amd64
> Version: 2.25-1
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>
>
On 2017-11-20 21:58, Mikulas Patocka wrote:
>
>
> On Mon, 20 Nov 2017, Samuel Thibault wrote:
>
> > Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > > x86-64 libc in /lib64/). This package is not
On Mon, 20 Nov 2017, Samuel Thibault wrote:
> Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > x86-64 libc in /lib64/). This package is not technically needed (because
> > x86-64 libc is already installed
On 2017-11-20 20:47, Samuel Thibault wrote:
> Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > x86-64 libc in /lib64/). This package is not technically needed (because
> > x86-64 libc is already installed in
Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> x86-64 libc in /lib64/). This package is not technically needed (because
> x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> installed
Package: libc6-amd64
Version: 2.25-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I have a x86-64 system with i386 and x32 foreign architectures
21 matches
Mail list logo
