Some mythplugins packages fail to configure if /var/lib/mythtv NFS mounted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mythexport (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Hardy |
Won't Fix
|
Undecided
|
Unassigned | ||
mythplugins (Ubuntu) |
Fix Released
|
Undecided
|
Mario Limonciello | ||
Hardy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mythgallery, mythmusic, mythvideo
When /var/lib/mythtv is mounted over NFS, the following MythTV plug-in packages will fail to configure: mythgallery, mythmusic, mythvideo. These packages attempt to change ownership/
Setting up mythgallery (0.21.0-
chown: changing ownership of `/var/lib/
dpkg: error processing mythgallery (--configure):
subprocess post-installation script returned error exit status 1
Setting up mythvideo (0.21.0-
chown: changing ownership of `/var/lib/
dpkg: error processing mythvideo (--configure):
subprocess post-installation script returned error exit status 1
Setting up mythmusic (0.21.0-
chown: changing ownership of `/var/lib/
dpkg: error processing mythmusic (--configure):
subprocess post-installation script returned error exit status 1
This issue is likely to occur for those who use NFS when upgrading from version 0.20 to 0.21 in gutsy-backports or hardy. A possible workaround is to temporarily unmount the NFS, then completely reinstall all three packages. Note that simply retrying the configure after unmounting does not necessarily work, since those directories would not have been created during package install (empty mount point directory eclipsed by NFS mount).
description: | updated |
Changed in mythexport (Ubuntu): | |
status: | New → In Progress |
Here's a debdiff.
This differs from the original approach for this SRU (as discussed with superm1 and slangasek). It was planned to change the code to ignore chmod/chown failures on package updates, but not on fresh installs. However, that doesn't make a lot of sense considering that people might already have the network mounts in place before they install the packages for the first time.
Maybe it'd be a good idea to check permissions and only fix them if necessary, but that'd be too intrusive for an SRU, IMHO.