dpkg aborts

[Michal Suchanek]

Oneiric dpkg aborts.

Since Precise dpkg does not I guess the simplest fix is to just import the new version

Setting up libx11-doc (2:1.4.99.1-0ubuntu1) ...
dpkg: ../../src/packages.c:229: process_queue: Assertion `dependtry <= 4' failed.
E: Sub-process /usr/bin/dpkg exited unexpectedly
A package failed to install. Trying to recover:
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
dpkg: ../../src/packages.c:229: process_queue: Assertion `dependtry <= 4' failed.
Aborted
Press return to continue.
^C
root@iscsi:~# dpkg --pending --configure
dpkg: ../../src/packages.c:229: process_queue: Assertion `dependtry <= 4' failed.
Aborted
root@iscsi:~# aptitude install -t precise dpkg
The following packages will be upgraded:
  dpkg
The following partially installed packages will be configured:
  wine1.3 wine1.4 wine1.4-amd64 wine1.4-i386
1 packages upgraded, 0 newly installed, 0 to remove and 1354 not upgraded.
Need to get 1,829 kB of archives. After unpacking 534 kB will be freed.
Do you want to continue? [Y/n/?]
Get: 1 http://cz.archive.ubuntu.com/ubuntu/ precise/main dpkg amd64 1.16.1.2ubuntu5 [1,829 kB]
Fetched 1,829 kB in 3s (494 kB/s)
(Reading database ... 248413 files and directories currently installed.)
Preparing to replace dpkg 1.16.0.3ubuntu5 (using .../dpkg_1.16.1.2ubuntu5_amd64.deb) ...
Unpacking replacement dpkg ...
Processing triggers for man-db ...
Setting up dpkg (1.16.1.2ubuntu5) ...
Setting up wine1.4 (1.4~rc2-0ubuntu2) ...
procps stop/waiting
Setting up wine1.4-amd64 (1.4~rc2-0ubuntu2) ...
Setting up wine1.3 (1.4~rc2-0ubuntu2) ...
Setting up wine1.4-i386:i386 (1.4~rc2-0ubuntu2) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: dpkg 1.16.1.2ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-15.26-server 3.0.13
Uname: Linux 3.0.0-15-server x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Fri Feb 17 12:07:04 2012
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: dpkg
UpgradeStatus: No upgrade log present (probably fresh install)

[Raphaël Hertzog (hertzog)]

You fixed the problem a bit too quickly... now tell me how can I reproduce it?

You should have made a backup of all the important files in /var/lib/dpkg/ (at least status, possibly the content of the updates directory too, if not empty) when you were encountering the problem.

[Michal Suchanek (hramrach)]

2012/2/17 Raphaël Hertzog <email address hidden>:
> You fixed the problem a bit too quickly... now tell me how can I
> reproduce it?

Setting up dpkg (1.16.0.3ubuntu5) ...

# aptitude reinstall wine1.4{,-i386,-amd64} wine1.3
The following packages will be REINSTALLED:
  wine1.3 wine1.4 wine1.4-amd64
0 packages upgraded, 0 newly installed, 3 reinstalled, 0 to remove and
0 not upgraded.
Need to get 0 B/22.1 MB of archives. After unpacking 0 B will be used.
Preconfiguring packages ...
(Reading database ... 248413 files and directories currently installed.)
Preparing to replace wine1.4 1.4~rc2-0ubuntu2 (using
.../wine1.4_1.4~rc2-0ubuntu2_amd64.deb) ...
Unpacking replacement wine1.4 ...
Preparing to replace wine1.4-amd64 1.4~rc2-0ubuntu2 (using
.../wine1.4-amd64_1.4~rc2-0ubuntu2_amd64.deb) ...
Unpacking replacement wine1.4-amd64 ...
Preparing to replace wine1.3 1.4~rc2-0ubuntu2 (using
.../wine1.3_1.4~rc2-0ubuntu2_amd64.deb) ...
Unpacking replacement wine1.3 ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for gnome-menus ...
Processing triggers for desktop-file-utils ...
Processing triggers for man-db ...
dpkg: ../../src/packages.c:229: process_queue: Assertion `dependtry <=
4' failed.
E: Sub-process /usr/bin/dpkg exited unexpectedly
A package failed to install. Trying to recover:
dpkg: ../../src/packages.c:229: process_queue: Assertion `dependtry <=
4' failed.
Aborted

>
> You should have made a backup of all the important files in
> /var/lib/dpkg/ (at least status, possibly the content of the updates
> directory too, if not empty) when you were encountering the problem.
>

Now this is somewhat redudndant chasing a bug fixed in newer dpkg already.

[Raphaël Hertzog (hertzog)]

On Fri, 17 Feb 2012, Michal Suchanek wrote:
> > You should have made a backup of all the important files in
> > /var/lib/dpkg/ (at least status, possibly the content of the updates
> > directory too, if not empty) when you were encountering the problem.
>
> Now this is somewhat redudndant chasing a bug fixed in newer dpkg
> already.

Right... why did you decide to report it then? Do you really believe that
it's worth being fixed in oneiric? It's not a widely encountered bug since
you're the firt one to report it. :-)

Please, despite this, can you attach the /var/lib/dpkg/status that
triggers this bug ? I don't have any oneiric chroot to reproduce it
quickly...

Cheers,
--
Raphaël Hertzog ◈ Debian Developer

Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/liberation/

[Michal Suchanek (hramrach)]

I suspect that once packges get backported to oneiric whatever trigggers the issue might get backported as well or some other packages might trigger it. As it is fixed in newer version I also suspect it was already diagnosed and fixed, hence re-diagnosing it is redudndant.

[dino99 (9d9)]

That version is no more supported