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