Bug#708831: upgrade-reports: [sid->sid] left system barely unusable (manually fixed with dpkg --install)
reassign 708831 apt
retitle 708831 apt: packages unpacked in the wrong order
thanks
On Sat, May 18, 2013 at 11:29:22PM +0200, Richard Hartmann wrote:
> Package: upgrade-reports
> Severity: grave
> Justification: renders package unusable
>
>
> Broken Python upgrade left me without working debconf.
>
>
> Full log at http://paste.debian.net/5060/
>
>
> Fixed by manually installing libc6 packages and locales*.deb
>
>
> Fetched 520 MB in 21min 17s (407 kB/s)
> Reading changelogs... Done
> apt-listchanges: Mailing root: apt-listchanges: news for rockhopper
> Extracting templates from packages: 100%
> Preconfiguring packages ...
> (Reading database ... 212752 files and directories currently installed.)
> Preparing to replace libpython2.7 2.7.3-8 (using
> ..../libpython2.7_2.7.5-2_i386.deb) ...
> Unpacking replacement libpython2.7 ...
> Preparing to replace python2.7 2.7.3-8 (using
> ..../python2.7_2.7.5-2_i386.deb) ...
> Unpacking replacement python2.7 ...
> Preparing to replace python2.7-minimal 2.7.3-8 (using
> ..../python2.7-minimal_2.7.5-2_i386.deb) ...
> Unpacking replacement python2.7-minimal ...
> dpkg: warning: unable to delete old directory '/etc/python2.7':
> Directory not empty
> Selecting previously unselected package libpython2.7-minimal.
> Unpacking libpython2.7-minimal (from
> ..../libpython2.7-minimal_2.7.5-2_i386.deb) ...
> Preparing to replace mime-support 3.52-2 (using
> ..../mime-support_3.54_all.deb) ...
> Unpacking replacement mime-support ...
> Preparing to replace debconf 1.5.49 (using .../debconf_1.5.50_all.deb)
> ....
> /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version
> `GLIBC_2.15' not found (required by /usr/bin/python)
> /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version
> `GLIBC_2.16' not found (required by /usr/bin/python)
> dpkg: warning: subprocess old pre-removal script returned error exit
> status 1
> dpkg: trying script from the new package instead ...
> /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version
> `GLIBC_2.15' not found (required by /usr/bin/python)
> /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version
> `GLIBC_2.16' not found (required by /usr/bin/python)
> dpkg: error processing /var/cache/apt/archives/debconf_1.5.50_all.deb
> (--unpack):
> subprocess new pre-removal script returned error exit status 1
> /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version
> `GLIBC_2.15' not found (required by /usr/bin/python)
> /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version
> `GLIBC_2.16' not found (required by /usr/bin/python)
> dpkg: error while cleaning up:
> subprocess installed post-installation script returned error exit
> status 1
> Processing triggers for man-db ...
> Processing triggers for desktop-file-utils ...
> Errors were encountered while processing:
> /var/cache/apt/archives/debconf_1.5.50_all.deb
>
The problem is that python2.7-minimal depends on libc6 (>= 2.16), while
it is unpacked before libc6 is unpacked. According to one of the dpkg
maintainer, the order is chosen by apt, hence reassigning the bug there.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: