Ubuntu
mythtv package

Upgrade to Edgy aborted on mythtv-database

Bug #68672 reported by Colin Fox
6
Affects Status Importance Assigned to Milestone
mythtv (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

The upgrade from Dapper to Edgy aborted when it got to installing mythtv-database, and asked me to include /var/log/dist-upgrade/ files.

Revision history for this message
Colin Fox (cfox) wrote :

One of the three logfiles.

Revision history for this message
Colin Fox (cfox) wrote :
Revision history for this message
Colin Fox (cfox) wrote :
Revision history for this message
Mario Limonciello (superm1) wrote :

Michael,

Several bugs like this have been cropping up with mythtv-database & the upgrade to edgy. During the upgrade process, mysql is momentarily stopped for the upgrade.

Unfortunately, both mythtv-database mythtv-backend won't be able to be properly installed without it running.

Is there any sort of way that you could force mysql to be configured (and thus started) prior to mythtv-backend and mythtv-database?

Revision history for this message
Michael Vogt (mvo) wrote :

Hello Mario!

Thanks for looking into this issue. Unfortunately the update-manager can't control the odering of unpack/configure in dpkg during the install directly. This is all be done according to the dependencies of the packages. The dependencies of the mytv-database are in such a way that mysql server is unpacked (and therefore stopped) and it is restarted only when it is configured again by dpkg (which happens after mytv-database is configured).

So what happns is:

unpack mysql-server (stops the server)
unpack mythtv-database
configure mytv-database (tries to connect)
configure mysql-server (starts the server)

To fix the issue we either need to ensure that mytv-database is only configured after mysql-server was configured. In theory a pre-depends could be used for this, but because mytv-database does not depend on mysql-server directly but only on the client this is not practical (server might be on a different machine etc).

The other option is that the mytv-database postinst does not fail if it can't connect to the database but echo a warning to run "dpkg-reconfigure mythtv-database" (or even use a post-install notification or a debconf note) and keeps going. Looking over the postinst script it seems to be setting up a database (should be not needed on upgrades) and converting from some older db format to a newer one. I don't know if that is a issue during the upgrade. But if not I would only print out a warning instead of letting the postinst fail when no database connection is available.

Please let me know what you think!

Cheers,
 Michael

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.