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

2018-01-25 Thread Guillem Jover
Hi! On Sun, 2018-01-21 at 17:13:38 +0200, Niko Tyni wrote: > On Sun, Jan 21, 2018 at 05:32:01AM +0100, Guillem Jover wrote: > > On Sun, 2018-01-21 at 02:59:53 +0100, Andreas Beckmann wrote: > > > Even if python is going to get fixed, this probably won't help > > > libglib2.0-dev (which drops the

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

2018-01-21 Thread Niko Tyni
On Sun, Jan 21, 2018 at 05:32:01AM +0100, Guillem Jover wrote: > On Sun, 2018-01-21 at 02:59:53 +0100, Andreas Beckmann wrote: > > Control: clone -1 -2 > > Control: retitle -2 libglib2.0-dev: needs dummy empty prerm > > Control: reassign -2 libglib2.0-dev 2.54.2-1 > > > > >> On Sat, Jan 20, 2018

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

2018-01-20 Thread Guillem Jover
On Sun, 2018-01-21 at 02:59:53 +0100, Andreas Beckmann wrote: > Control: clone -1 -2 > Control: retitle -2 libglib2.0-dev: needs dummy empty prerm > Control: reassign -2 libglib2.0-dev 2.54.2-1 > > >> On Sat, Jan 20, 2018 at 05:07:30PM +0100, Andreas Beckmann wrote:>>> For > >> now, I'd suggest

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

2018-01-20 Thread Andreas Beckmann
Control: clone -1 -2 Control: retitle -2 libglib2.0-dev: needs dummy empty prerm Control: reassign -2 libglib2.0-dev 2.54.2-1 >> On Sat, Jan 20, 2018 at 05:07:30PM +0100, Andreas Beckmann wrote:>>> For >> now, I'd suggest the dummy empty libglib2.0-dev.prerm, but if this Even if python is going

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

2018-01-20 Thread Guillem Jover
Control: reassign -1 python2.7-minimal,python3.6-minimal,debhelper Control: retitle -1 python: Wants to be used like Essential:yes but does not follow its requirements Control: affects -1 - libc6 libexpat1 Control: affects -1 + libglib2.0-dev Hi! On Sat, 2018-01-20 at 23:19:30 +0200, Niko Tyni

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. > > > >

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

2018-01-20 Thread Niko Tyni
On Sat, Jan 20, 2018 at 05:07:30PM +0100, Andreas Beckmann wrote: > For now, I'd suggest the dummy empty libglib2.0-dev.prerm, but if this > error starts to show up elsewhere (e.g. in a package where both old and > new prerm use python3), probably adding the Pre-Depends to libexpat1 > would be

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

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

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

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 > > >

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: > > >

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:

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