Package: libc6-dev-s390
Version: 2.13-37
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
I tried to compile 31-bit program on 64-bit s390x system
* What exactly
Package: libc6-dev-x32
Version: 2.24-11+deb9u1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I was trying to compile a program for the x32 ABI.
* What exactly did you do (or not do)
Package: libc6
Severity: important
Tags: upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
The stack clash patch modifies the kernel so that there is 1MB gap below the
stack. If a single function
Package: libc6-dev
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Programs can't be statically linked against OpenSSL in Debian Stretch.
* What exactly did you do (or not do) that was
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 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 lib
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 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
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
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 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 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
&g
12 matches
Mail list logo
