Upgrade to hardy beta fails

[zapodot]

Binary package hint: update-manager

While upgrading my system from Ubuntu Gutsy (server) to Ubuntu Hardy (server) using the command "update-manager -d" fails with the error message "Internal Error, Could not perform immediate configuration (2) on libpam0g "

The log files from /var/log/dist-upgrade are attached.

[Richard Birnie (rbirnie-deactivatedaccount)]

From a quick look through the apt.log it looks like some dependency issues around libsasl2 and libvolumeid are the problem

Investigating libvolume-id0
Package libvolume-id0 has broken dep on libvolumeid0
  Considering libvolumeid0 4 as a solution to libvolume-id0 10
  Added libvolumeid0 to the remove list
  Fixing libvolume-id0 via remove of libvolumeid0
Investigating libsasl2
Package libsasl2 has broken dep on libsasl2-modules
  Considering libsasl2-modules 15 as a solution to libsasl2 4
Package libsasl2 has broken dep on libsasl2-modules-sql
Package libsasl2 has broken dep on libsasl2-modules-gssapi-heimdal
Package libsasl2 has broken dep on libsasl2-modules-kerberos-heimdal
  Or group remove for libsasl2

[Russell Smith (mr-russ)]

A manual installation of libpam0g appears to fix the problem. I experienced the same problem updating a gutsy -> hardy server this evening. Updates were applied at 18:30+10 Saturday 12th April. Upgrade to hardy was then done at 19:00+10. This failed and investigation followed. The upgrade appears to be running correctly after completing the workaround below.

To work around this issue;

After the initial failure
$ sudo apt-get install libpam0g
$ sudo do-release-upgrade -d

Upgrade should continue as expected, it did for me.

[Richard Birnie (rbirnie-deactivatedaccount)]

Russell,

Thanks for providing a work around. Do you have the log files from /var/log/dist-upgrade from your upgrade? It would be useful to compare against zapodots logs to find the root of the problem

[Russell Smith (mr-russ)]

I have all the files and they are attached. It includes what I had at
the end of the upgrade. I did not specifically save them after the
initial failure. So what is attached is all the upgrade information I
can probably provide. Unless there is other system information that is
useful. I've also attached a package list 'dpkg -l' for the system now,
after the upgrade. I'm not well versed in what I should include in this
type of bug report, so if there are further commands I can run to give
useful information please ask.

The failure happens at the beginning stage of installing the new
packages. sources.list has been altered to hardy, but none of the hardy
packages have been installed.

Regards

Russell

[Richard Birnie (rbirnie-deactivatedaccount)]

Thanks for following up Russell. You've provided all the right information. Those log files I asked for are the critical thing for update manager bugs. I'm getting a bit out of my depth now but it looks like your problems are related to a package called bash-completion. apt-term.log ends with

Errors were encountered while processing:
 bash-completion
Log ended: 2008-04-12 20:39:22

Looking earlier in the same log I found a lot of nonsense characters but once I filtered out the noise I was left with the following
################################
Setting up bash-completion (20060301-3ubuntu2) ...
Package configuration
Modified configuration file
A new version of configuration file /etc/bash_completion is available,
but the version installed currently has been locally modified. What would you like to do about bash_completion?
install the package maintainer's version
keep the local version currently installed
show the differences between the versions
show a side-by-side difference between the versions
start a new shell to examine the situation <Ok>
keep the local version currently installed
show the differences between the versions
show a side-by-side difference between the versions
q
dpkg: error processing bash-completion (--configure):
 subprocess post-installation script killed by signal (Interrupt)
##################################
It looks like the system was asking for some input. Do you remember seeing this and can you remember what response you gave?

I think there might be two separate issues here. If I look at Russells main.log I find
###########################
ERROR got an error from dpkg for pkg: 'bash-completion': 'subprocess post-installation script killed by signal (Interrupt)'
2008-04-12 20:35:12,087 DEBUG running apport_pkgfailure() bash-completion: subprocess post-installation script killed by signal (Interrupt)
###########################

In comparison zapodots main.log has the following
###########################
ERROR SystemError from cache.commit(): E:Internal Error, Could not perform immediate configuration (2) on libpam0g
2008-04-11 08:59:23,370 WARNING cache.commit() raised a SystemError but pkg_failures count is 0
2008-04-11 08:59:23,370 DEBUG running apport_pkgfailure() update-manager: SystemError in cache.commit(): E:Internal Error, Could not perform immediate configuration (2) on libpam0g
###########################

Sorry for the huge report. In summary, Russell, thanks for following through on this. If you can remember what you answered to the questions about bash-completion that would be great. Then it's over to the developers to figure out what this all means.

Rich

[Russell Smith (mr-russ)]

Richard,

The comprehensive reply is helpful and in this case important. During
the upgrade I selected "compare side by side" for the bash completion,
which gave me a blank screen. I press control-C and the installation
continued as expected. It then again at the end of the upgrade asked to
configure bash completion. This time I did a regular diff. I replaced
the local copy with the version from the package. Everything finished
correctly and I had a perfectly running system.

I suspect what you see below in my log is that experience, not the
libpam0g problem I was experiencing. The original log before the manual
installation of libpam0g looks exactly like zapodots unless I'm
mistaken. I don't think I am. The log files I send are from the
sucessful upgrade. As I mentioned in the earlier mail, I don't have the
logs from the failed upgrade, I probably should have kept those. Too
late now :(

So even though it looks like the problems are different, I suspect they
are exactly the same.

Other thinking is that linux-libc-dev was required to be installed to
enable libpam0g to be installed when I didn apt-get install libpam0g.
But it's not listed in the upgrade package list.

Regards

Russell

[Richard Birnie (rbirnie-deactivatedaccount)]

Thanks again for following up. I think we've done as much as we can now it's over to the developers.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, this bug is a duplicate of bug 217435, which was fixed on 2008-04-15, and is being marked as such. Feel free to submit any future bugs you may find.

Here is the changelog entry:

This bug was fixed in the package liblocale-gettext-perl - 1.05-2ubuntu1

---------------
liblocale-gettext-perl (1.05-2ubuntu1) hardy; urgency=low

  * debian/rules:
    - relax the dependencies to workaround ordering
      problem in apt on gutsy->hardy upgrade (LP: #217435)

 -- Michael Vogt <email address hidden> Tue, 15 Apr 2008 16:33:19 +0200