I see multiple odd things in the log:
dpkg: status database area is locked by another process
that seem to indicate that synaptic or some other software is running
concurrently
dpkg: error processing libdb4.7 (--configure):
package libdb4.7 is already installed and configured
Errors were encountered while processing:
libdb4.7
this seems to indicate that dpkg --configure libdb4.7 was run when it was
already configured, and I think we should ignore such failures (perhaps we
already do?)
The same thing happens near bzip2:
dpkg: dependency problems prevent configuration of libpython2.6:
libpython2.6 depends on python2.6 (= 2.6.4-0ubuntu1); however:
Package python2.6 is not configured yet.
dpkg: error processing libpython2.6 (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: error
processing bzip2 (--configure):
package bzip2 is already installed and configured
but I suspect the apport output might confuse parsing of the error.
The only real error I see in this log is:
Preparing to replace python2.6 2.6.2-0ubuntu1 (using
.../python2.6_2.6.4-0ubuntu1_amd64.deb) ...
Unpacking replacement python2.6 ...
Preparing to replace python2.6-minimal 2.6.2-0ubuntu1 (using
.../python2.6-minimal_2.6.4-0ubuntu1_amd64.deb) ...
Unpacking replacement python2.6-minimal ...
dpkg: status database area is locked by another process
which seems to have broken python2.6 libpython2.6 python python-support
etc., apparently due to another tool being launched during the upgrade.
However I dont know which tool causes packages like bzip2 to get
--configured when these already are.
--
package bzip2 1.0.5-1ubuntu1 failed to install/upgrade:
https://bugs.launchpad.net/bugs/475340
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
