package python3.1-minimal 3.1.1-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #446004 reported by christian
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
python3.1 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: python3.1

the configure uses /usr/local which was mounted over nfs and somehow no directories could be created.

whether this a bug or not I do not know. but I expected /usr/local to be untouched by the core system !?

unmounting the nfs share solved the problem

ProblemType: Package
AptOrdering:
 python3.1-minimal: Configure
 python3-minimal: Configure
 python3.1: Configure
Architecture: i386
Date: Thu Oct 8 09:48:37 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 1
Package: python3.1-minimal 3.1.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.31-12.40-generic
SourcePackage: python3.1
Title: package python3.1-minimal 3.1.1-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Uname: Linux 2.6.31-12-generic i686

Revision history for this message
christian (meier-christian) wrote :
Revision history for this message
Matthias Klose (doko) wrote :

no, this is correct. The postinst creates a directory /usr/local/lib/python2.6/dist-packages which is used for local installations of python modules.

See http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1

As mandated by the FHS, packages must not place any files in /usr/local, either by putting them in the file system archive to be unpacked by dpkg or by manipulating them in their maintainer scripts.

However, the package may create empty directories below /usr/local so that the system administrator knows where to place site-specific files. These are not directories in /usr/local, but are children of directories in /usr/local. These directories (/usr/local/*/dir/) should be removed on package removal if they are empty.

Changed in python3.1 (Ubuntu):
status: New → Invalid
Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :

And so how do i fix my system:

Setting up python3.1-minimal (3.1.1-0ubuntu5) ...
mkdir: cannot create directory `/usr/local/lib/python3.1': Permission denied
dpkg: error processing python3.1-minimal (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python3.1:
 python3.1 depends on python3.1-minimal (= 3.1.1-0ubuntu5); however:
  Package python3.1-minimal is not configured yet.
dpkg: error processing python3.1 (--configure):
 dependency problems - leaving unconfigured

The bottom line is that /usr/local is defined by FHS as being site-local and anyone/anything other than the sysadmin should not be expecting to be able to do anything in there as it is by definition for the local administrator and packages should not be meddling in.

Revision history for this message
jtniehof (jtniehof) wrote :

The policy Matthias linked also says "[T]hese directories must be created and removed by the postinst and prerm maintainer scripts.... These scripts must not fail if either of these operations fail. " Since the installation of python31-minimal fails when /usr/local/lib is not writeable, I believe this is a valid bug. Attached is a patch to fix the postinst script per the directions in the Debian policy manual (9.1.2).

Changed in python3.1 (Ubuntu):
status: Invalid → Confirmed
Matthias Klose (doko)
Changed in python3.1 (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Matthias Klose (doko) wrote :

fixed in 3.1.2-0ubuntu1

Changed in python3.1 (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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