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 python dependency in buster), therefore > > > it will need to add the dummy empty prerm to mitigate this issue. > > > > I don't see why this would be needed. If python gets fixed to use > > Pre-Depends, then it does not matter whether libglib2.0-dev stops > > depending on it, as python should then be always usable even when > > just unpacked. > > stretch# apt --no-install-recommends install glib2.0-dev > [...] > stretch# dpkg --unpack libexpat1_2.2.5-3_amd64.deb # from sid > [...] > stretch# dpkg --unpack libglib2.0-dev_2.54.3-1_amd64.deb # from sid > /usr/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not > found (required by /lib/x86_64-linux-gnu/libexpat.so.1) > dpkg: warning: subprocess old pre-removal script returned error exit status 1 > dpkg: trying script from the new package instead ... > dpkg: error processing archive libglib2.0-dev_2.54.3-1_amd64.deb (--unpack): > there is no script in the new version of the package - giving up > /usr/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not > found (required by /lib/x86_64-linux-gnu/libexpat.so.1) > dpkg: error while cleaning up: > subprocess installed post-installation script returned error exit status 1 > > No python3 change in sid/buster is going to prevent this afaics?
Ah sorry, you are exactly right. Good think this is even worked around now in unstable anyway. :) Thanks, Guillem
