[Bug 915167] Re: pycompile will use /usr/local/bin/python2.X if available and python2.X is installed.

[Stefano Rivera]

** Summary changed:

- pycompile will use /usr/local/bin/python2.6 if available and python2.6 isn't installed.
+ pycompile will use /usr/local/bin/python2.X if available and python2.X is installed.

** Description changed:

  [Impact]
- <fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release>
+ Anyone who has a locally built python in /usr/local as well as the Ubuntu package with the same version. This is something that Debian/Ubuntu's python approach intends to support.
  
  [Development Fix]
- <fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. >
+ This bug was fixed upstream very soon after the version of python-defaults we ended up with in natty.
  
  [Stable Fix]
- <fill me in by pointing out a minimal patch applicable to the stable version of the package.>
+ The patch is trivial, call python with an absolute path, instead of relying on $PATH.
  
  [Text Case]
- <fill me in with detailed *instructions* on how to reproduce the bug.  This will be used by people later on to verify the updated package fixes the problem.>
- 1.
- 2.
- 3.
- Broken Behavior: 
- Fixed Behavior: 
+ 
+ 1. Install python-all
+ 2. Build and install cpython from source
+    OR
+    echo -e '#!/bin/sh\nexit 1' > /usr/local/bin/python2.7
+    chmod +x /usr/local/bin/python2.7
+ 3. Install a python package such as python-beautifulsoup
+ Success: It works
+ Failure: An error while setting up python-beautifulsoup
  
  [Regression Potential]
- <fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. 
+ Patch is simple enough that I can't see any. The risk of any rebuild at all is higher than the impact of this patch.
  
  [Original Report]
  Problem installing -
  sudo apt-get install linaro-image-tools
  
  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: python-beautifulsoup 3.2.0-1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu Jan 12 13:54:21 2012
  ErrorMessage: subprocess installed post-installation script returned error exit status 1
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  SourcePackage: beautifulsoup
  Title: package python-beautifulsoup 3.2.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
- 
- == SRU Impact ==
- Anyone who has a locally built python in /usr/local as well as the Ubuntu package with the same version.
- 
- == SRU Verification ==
- 1. Install python-all
- 2. Build and install cpython from source
-    OR
-    echo -e '#!/bin/sh\nexit 1' > /usr/local/bin/python2.7
-    chmod +x /usr/local/bin/python2.7
- 3. Install a python package such as python-beautifulsoup
- Failure: An error while setting up python-beautifulsoup

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/915167

Title:
  pycompile will use /usr/local/bin/python2.X if available and python2.X
  is installed.

Status in “python-defaults” package in Ubuntu:
  Fix Released
Status in “python-defaults” source package in Natty:
  New

Bug description:
  [Impact]
  Anyone who has a locally built python in /usr/local as well as the Ubuntu package with the same version. This is something that Debian/Ubuntu's python approach intends to support.

  [Development Fix]
  This bug was fixed upstream very soon after the version of python-defaults we ended up with in natty.

  [Stable Fix]
  The patch is trivial, call python with an absolute path, instead of relying on $PATH.

  [Text Case]

  1. Install python-all
  2. Build and install cpython from source
     OR
     echo -e '#!/bin/sh\nexit 1' > /usr/local/bin/python2.7
     chmod +x /usr/local/bin/python2.7
  3. Install a python package such as python-beautifulsoup
  Success: It works
  Failure: An error while setting up python-beautifulsoup

  [Regression Potential]
  Patch is simple enough that I can't see any. The risk of any rebuild at all is higher than the impact of this patch.

  [Original Report]
  Problem installing -
  sudo apt-get install linaro-image-tools

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: python-beautifulsoup 3.2.0-1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu Jan 12 13:54:21 2012
  ErrorMessage: subprocess installed post-installation script returned error exit status 1
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  SourcePackage: beautifulsoup
  Title: package python-beautifulsoup 3.2.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/915167/+subscriptions