package mythtv-database 0.22.0+fixes23003-0ubuntu0+mythbuntu3 failed to install/upgrade: could not backup or apply new schema to mythconverg

Bug #501732 reported by gregbuntu
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Expired
Undecided
Unassigned

Bug Description

Upon upgrade from mythbuntu 0.22 to 0.22.0+fixes23003, installer crashed. The installer indicated it would upgrade the mythconverg schema but it was unable to create a backup. I proceeded (knowing I have a manual backup). The installation then failed: unable to update schema for mythconverg, which also caused the myth-backend and master backend upgrade to fail. Manually running mythtv-setup also fails with the same errors. This system was originally upgraded from Mythbuntu 8.10 (mythtv 0.21) to Mythbuntu 9.10 (mythtv 0.22). I have been trying to import the recordings tables from the original Mythbuntu 8.10 partition but with little success (recordings after April 10, 2009 have a reference in MythTV and the .nuv files appear in the recordings directory but they are not available for viewing within MythTV). Possibly this database issue is related to the failed setup.

ProblemType: Package
Architecture: amd64
CrashDB: mythbuntu
Date: Wed Dec 30 14:13:34 2009
DistroRelease: Ubuntu 9.10
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Mythbuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: mythtv-database 0.22.0+fixes23003-0ubuntu0+mythbuntu3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: mythtv
Title: package mythtv-database 0.22.0+fixes23003-0ubuntu0+mythbuntu3 failed to install/upgrade:
Uname: Linux 2.6.31-16-generic x86_64

Revision history for this message
gregbuntu (wyatt-greg) wrote :
Revision history for this message
Mario Limonciello (superm1) wrote :

Is your database corrupted per chance? have you tried to run the standard repair on all the tables?

If that's the root cause here, there's not much we can do. If that doesn't help out, can you please add "set -x" to the second line of /var/lib/dpkg/info/mythtv-database.postinst and run dpkg-reconfigure mythtv-database? The output of that should help us debug what's going on.

Changed in mythbuntu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mythbuntu because there has been no activity for 60 days.]

Changed in mythbuntu:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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