Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

2018-01-20 Thread Guillem Jover
Hi! On Thu, 2018-01-18 at 21:45:51 +0100, Aurelien Jarno wrote: > On 2018-01-18 20:38, Julian Andres Klode wrote: > > On Thu, Jan 18, 2018 at 06:41:52PM +0100, Aurelien Jarno wrote: > > > This failure is normal given libexpat1 requires the new libc which has > > > not been unpacked yet. > > > > Y

Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

2018-01-20 Thread Andreas Beckmann
On 2018-01-18 23:59, David Kalnischkies wrote: > Hi, > > On Thu, Jan 18, 2018 at 09:45:51PM +0100, Aurelien Jarno wrote: > [...] > Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ... > /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' > not found

Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

2018-01-19 Thread Andreas Beckmann
On 2018-01-18 21:45, Aurelien Jarno wrote: [...] Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ... /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/i386-linux-gnu/libexpat.so.1) dpkg: warning: subprocess o

Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

2018-01-18 Thread David Kalnischkies
Hi, On Thu, Jan 18, 2018 at 09:45:51PM +0100, Aurelien Jarno wrote: > > > > [...] > > > > Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ... > > > > /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' > > > > not found (required by /lib/i386-linux-gnu/libexpat.so

Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

2018-01-18 Thread Aurelien Jarno
On 2018-01-18 20:38, Julian Andres Klode wrote: > On Thu, Jan 18, 2018 at 06:41:52PM +0100, Aurelien Jarno wrote: > > control: reassign -1 apt,dpkg > > control: affects -1 libc6 > > control: affects -1 libexpat1 > > > > On 2018-01-18 15:53, Andreas Beckmann wrote: > > > Package: libc6 > > > Versio

Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

2018-01-18 Thread Julian Andres Klode
On Thu, Jan 18, 2018 at 08:38:02PM +0100, Julian Andres Klode wrote: > On Thu, Jan 18, 2018 at 06:41:52PM +0100, Aurelien Jarno wrote: > > control: reassign -1 apt,dpkg > > control: affects -1 libc6 > > control: affects -1 libexpat1 > > > > On 2018-01-18 15:53, Andreas Beckmann wrote: > > > Packag

Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

2018-01-18 Thread Julian Andres Klode
On Thu, Jan 18, 2018 at 06:41:52PM +0100, Aurelien Jarno wrote: > control: reassign -1 apt,dpkg > control: affects -1 libc6 > control: affects -1 libexpat1 > > On 2018-01-18 15:53, Andreas Beckmann wrote: > > Package: libc6 > > Version: 2.26-2 > > Severity: serious > > User: debian...@lists.debian

Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

2018-01-18 Thread Aurelien Jarno
control: reassign -1 apt,dpkg control: affects -1 libc6 control: affects -1 libexpat1 On 2018-01-18 15:53, Andreas Beckmann wrote: > Package: libc6 > Version: 2.26-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your