package resolvconf 1.63ubuntu14 failed to install/upgrade: ErrorMessage: pre-dependency problem - not installing resolvconf

[Andres Gimenez]

[TEST CASE]
(from bug 937196)
1. Install Mythbuntu 10.04, and reboot
2. Press ESC to quit Mythbuntu
3. Do not install updates even if the system request you to do it
4. In a terminal run the following command:
 $ do-release-upgrade -d
5. Proceed with the upgrade to Precise

[ACTUAL RESULT]
Upgrade to Precise fails with the following trace in /var/log/dist-upgrade/apt-term.log:
Setting up libplymouth2 (0.8.2-2ubuntu30) ...
dpkg: dependency problems prevent configuration of ifupdown:
 ifupdown depends on upstart-job; however:
  Package upstart-job is not installed.
  Package upstart which provides upstart-job is not configured yet.
 ifupdown depends on initscripts (>= 2.88dsf-13.3); however:
  Package initscripts is not configured yet.
dpkg: error processing ifupdown (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 ifupdown

[EXPECTED RESULT]
Upgrade to Precise succeeds

It automatically detected the bug....

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: resolvconf 1.63ubuntu14
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Sat Jun 23 14:03:11 2012
ErrorMessage: ErrorMessage: pre-dependency problem - not installing resolvconf
PackageArchitecture: all
SourcePackage: resolvconf
Title: package resolvconf 1.63ubuntu14 failed to install/upgrade: ErrorMessage: pre-dependency problem - not installing resolvconf
UpgradeStatus: Upgraded to precise on 2012-06-23 (0 days ago)

[Steve Langasek (vorlon)]

The upgrade logs shows cascading failures due to apt not configuring packages in order:

Setting up gcc-4.6-base (4.6.3-1ubuntu5) ...
dpkg: dependency problems prevent configuration of libgcc1:i386:
 libgcc1:i386 depends on libc6 (>= 2.2.4); however:
  Package libc6:i386 is not configured yet.
dpkg: error processing libgcc1:i386 (--configure):
 dependency problems - leaving unconfigured

Reassigning to apt.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Steve Langasek (vorlon)]

There are now two reports of this issue within 24 hours of each other. It's possible that there's been a regression of some kind in precise-updates which is triggering wrong upgrade behavior. Marking as critical.

The first error from the duplicate bug is:

dpkg: dependency problems prevent configuration of ifupdown:
 ifupdown depends on initscripts (>= 2.88dsf-13.3); however:
  Package initscripts is not configured yet.
dpkg: error processing ifupdown (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                          dpkg: dependency problems prevent configuration of upstart:
 upstart depends on initscripts; however:
  Package initscripts is not configured yet.
 upstart depends on mountall; however:
  Package mountall is not configured yet.
 upstart depends on ifupdown (>= 0.6.10ubuntu5); however:
  Package ifupdown is not configured yet.

[Steve Langasek (vorlon)]

probably the same bug as bug #937196.

[Stéphane Graber (stgraber)]

Copying link from one of the dups:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/937196/+attachment/3205719/+files/VarLogDistupgradeAptclonesystemstate.tar.gz

[Michael Vogt (mvo)]

I tried to reproduce this from the aptclone file but couldn't trigger the bug unfortunately :/

[Michael Vogt (mvo)]

Still no luck in a chroot for me, I added a apt-clone show-diff command to see the differences, the packages are exactly the same in my chroot, but there are some version differences:

$ ./apt-clone show-diff --destination ./lp1017001 ./apt-clone.tar.gz
Clone info differences:
 'kernel': System='3.5.0-6-generic' clone='None'
 'hostname': System='top' clone='centurion.vanschouwen.nl'
 'uname_arch': System='x86_64' clone='None'

Version differences:
Pkgname <clone-file-version> <system-version>
 linux-headers-2.6.32-41-server <2.6.32-41.88> <2.6.32-41.91>
 libisccfg60 <1:9.7.0.dfsg.P1-1ubuntu0.4> <1:9.7.0.dfsg.P1-1ubuntu0.5>
 wpasupplicant <0.6.9-3ubuntu3> <0.6.9-3ubuntu3.1>
 php5-cgi <5.3.2-1ubuntu4.14> <5.3.2-1ubuntu4.17>
 landscape-common <11.07.1.1-0ubuntu0.10.04.0> <12.04.3-0ubuntu0.10.04>
 apt-transport-https <0.7.25.3ubuntu9.11> <0.7.25.3ubuntu9.13>
 dnsutils <1:9.7.0.dfsg.P1-1ubuntu0.4> <1:9.7.0.dfsg.P1-1ubuntu0.5>
 bind9-host <1:9.7.0.dfsg.P1-1ubuntu0.4> <1:9.7.0.dfsg.P1-1ubuntu0.5>
 php5-common <5.3.2-1ubuntu4.14> <5.3.2-1ubuntu4.17>
 libisc60 <1:9.7.0.dfsg.P1-1ubuntu0.4> <1:9.7.0.dfsg.P1-1ubuntu0.5>
 libtasn1-3 <2.4-1> <2.4-1ubuntu0.1>
 liblwres60 <1:9.7.0.dfsg.P1-1ubuntu0.4> <1:9.7.0.dfsg.P1-1ubuntu0.5>
 apparmor <2.5.1-0ubuntu0.10.04.3> <2.5.1-0ubuntu0.10.04.4>
 apparmor-utils <2.5.1-0ubuntu0.10.04.3> <2.5.1-0ubuntu0.10.04.4>
 apt <0.7.25.3ubuntu9.11> <0.7.25.3ubuntu9.13>
 libapparmor1 <2.5.1-0ubuntu0.10.04.3> <2.5.1-0ubuntu0.10.04.4>
 libgcrypt11 <1.4.4-5ubuntu2> <1.4.4-5ubuntu2.1>
 linux-headers-2.6.32-41 <2.6.32-41.88> <2.6.32-41.91>
 openssl <0.9.8k-7ubuntu8.11> <0.9.8k-7ubuntu8.13>
 libapparmor-perl <2.5.1-0ubuntu0.10.04.3> <2.5.1-0ubuntu0.10.04.4>
 linux-firmware <1.34.7> <1.34.14>
 libdns64 <1:9.7.0.dfsg.P1-1ubuntu0.4> <1:9.7.0.dfsg.P1-1ubuntu0.5>
 libisccc60 <1:9.7.0.dfsg.P1-1ubuntu0.4> <1:9.7.0.dfsg.P1-1ubuntu0.5>
 libxml2 <2.7.6.dfsg-1ubuntu1.4> <2.7.6.dfsg-1ubuntu1.5>
 linux-image-2.6.32-41-server <2.6.32-41.88> <2.6.32-41.91>
 libbind9-60 <1:9.7.0.dfsg.P1-1ubuntu0.4> <1:9.7.0.dfsg.P1-1ubuntu0.5>
 libssl0.9.8 <0.9.8k-7ubuntu8.11> <0.9.8k-7ubuntu8.13>
 firefox-locale-en <12.0+build1-0ubuntu0.10.04.1> <13.0.1+build1-0ubuntu0.10.04.1>
 sudo <1.7.2p1-1ubuntu5.3> <1.7.2p1-1ubuntu5.4>
 apt-utils <0.7.25.3ubuntu9.11> <0.7.25.3ubuntu9.13>

I try to find debs for these versions and try again.

[Steve Langasek (vorlon)]

fwiw the versions shown here seem to correspond quite closely to what was current at the time 10.04.4 was released - I find most of them on the 10.04.4 server CD. Perhaps that helps?

[Brian Murray (brian-murray)]

Here is another apt-clone file from bug 989436.

[Stéphane Graber (stgraber)]

Ran with that other apt-clone but couldn't reproduce the bug.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1017001

[Hendrik Friedel (henfri)]

Hello,

 I am experiencing the same problem. Is there a solution/workaround for this already?

Greetings,
Hendrik

[Juan Acosta (jmacostap)]

After the error, I applied the upgrade from the command line and it
finnished fine.
I did not need to install mythbuntu.

On Sun, Nov 25, 2012 at 11:09 AM, Hendrik Friedel <email address hidden> wrote:

> Hello,
>
> I am experiencing the same problem. Is there a solution/workaround for
> this already?
>
> Greetings,
> Hendrik
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1043517).
> https://bugs.launchpad.net/bugs/1017001
>
> Title:
> package resolvconf 1.63ubuntu14 failed to install/upgrade:
> ErrorMessage: pre-dependency problem - not installing resolvconf
>
> Status in “apt” package in Ubuntu:
> Confirmed
> Status in “apt” source package in Precise:
> Confirmed
> Status in “apt” source package in Quantal:
> Confirmed
>
> Bug description:
> [TEST CASE]
> (from bug 937196)
> 1. Install Mythbuntu 10.04, and reboot
> 2. Press ESC to quit Mythbuntu
> 3. Do not install updates even if the system request you to do it
> 4. In a terminal run the following command:
> $ do-release-upgrade -d
> 5. Proceed with the upgrade to Precise
>
> [ACTUAL RESULT]
> Upgrade to Precise fails with the following trace in
> /var/log/dist-upgrade/apt-term.log:
> Setting up libplymouth2 (0.8.2-2ubuntu30) ...
> dpkg: dependency problems prevent configuration of ifupdown:
> ifupdown depends on upstart-job; however:
> Package upstart-job is not installed.
> Package upstart which provides upstart-job is not configured yet.
> ifupdown depends on initscripts (>= 2.88dsf-13.3); however:
> Package initscripts is not configured yet.
> dpkg: error processing ifupdown (--configure):
> dependency problems - leaving unconfigured
> Processing triggers for libc-bin ...
> ldconfig deferred processing now taking place
> Errors were encountered while processing:
> ifupdown
>
> [EXPECTED RESULT]
> Upgrade to Precise succeeds
>
>
> It automatically detected the bug....
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: resolvconf 1.63ubuntu14
> ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
> Uname: Linux 3.2.0-25-generic x86_64
> ApportVersion: 2.0.1-0ubuntu8
> Architecture: amd64
> Date: Sat Jun 23 14:03:11 2012
> ErrorMessage: ErrorMessage: pre-dependency problem - not installing
> resolvconf
> PackageArchitecture: all
> SourcePackage: resolvconf
> Title: package resolvconf 1.63ubuntu14 failed to install/upgrade:
> ErrorMessage: pre-dependency problem - not installing resolvconf
> UpgradeStatus: Upgraded to precise on 2012-06-23 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1017001/+subscriptions
>

[Rolf Leggewie (r0lf)]

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

[Julian Andres Klode (juliank)]

Likely fixed in 1.3 or newer, as we just hand large batches to dpkg and let it do its magic. If someone can reproduce in yakkety or newer, either re-open or file a new bug.