Comment 44 for bug 990740

It's too soon to close this bug.

The original issue: "E: could not perform immediate configuration on python-minimal" happened to me yesterday (2 Sept 2012) in the context of manual recovery of a failed upgrade from lucid to precise. (My original post-point-release effort to upgrade was launched on 27 Aug with update manager.)

"python-minimal" for lucid depends on "python2.7-minimal", and " python2.7-minimal depends on
python-minimal (>=2.6.6-3+squeeze1); however: Version of python-minimal on system is 2.6.5-0ubuntu1."

I've checked a fully updated lucid where no attempt at upgrade had been made to verify that its python-minimal
is 2.6.5-0ubuntu1.

Anyway, what is this dependency on "squeeze" (a version of Debian?)?

It seems that something is wrong with the metadata for python2.7-minimal.

Given this dependency and that an updated lucid with python2.6 has python-minimal 2.6.5-0ubuntu1, how can the upgrade from lucid to precise be expected to work?