dh_python2: revert pyshared removal in 2.7.3-0ubuntu3

Bug #1001912 reported by Julian Taylor
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-defaults (Ubuntu)
High
Unassigned

Bug Description

2.7.3-0ubuntu3 removes the move to pyshared of dh_python2
this should be reverted, plenty of packages make explicit use of pyshared in their build and are now partially or completely broken.
E.g. python-traits fails to build due to this change
before such a step is taken first all packages should be fixed to not reference pyshared anymore

Julian Taylor (jtaylor)
Changed in python-defaults (Ubuntu):
importance: Undecided → High
Revision history for this message
Scott Kitterman (kitterman) wrote :

Python policy says:

A common location to share, across Python versions, arch-independent files which would otherwise go to the directory of system public modules is /usr/share/pyshared. For python3, a special location is not required, use /usr/lib/python3/dist-packages.

At this point this is a gratuitous change from Debian. There's no need for it and it should be coordinated. Removing the infrastructure to support multiple Python versions is something that should be discussed and agreed in Debian (with Python policy changes) before it's done in Ubuntu. There's nothing driving Ubuntu to rush on this.

Changed in python-defaults (Ubuntu):
status: New → Confirmed
Revision history for this message
Matthias Klose (doko) wrote :

please keep the change for now. it's important to catch all this kind build failures early in the cycle. There should be invalid uses of pyshared during build time, and then maybe build failures during the install stage when install files reference pyshared.

There is nothing in policy which explicitly allows the use of pyshared for anything besides installation.

Please let's collect these issues and tag them with `pyshared'.

tags: added: pyshared
Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 1001912] Re: dh_python2: revert pyshared removal in 2.7.3-0ubuntu3

It's the place Python policy says version independent files go. There are
reasonable reasons for dealing with files there.

What's the point in breaking a bunch of packages to avoid some symlinks?

Revision history for this message
Julian Taylor (jtaylor) wrote :

attached a list of 38 packages from the modules and apps team svn referencing pyshared in their debian folder
a lot of fixing for pretty much no gain.

Revision history for this message
Scott Kitterman (kitterman) wrote :

It's not just no gain. It makes the packages less backportable to releases
that still have python2.6. There's active harm.

Revision history for this message
Julian Taylor (jtaylor) wrote :

not necessarily, one can change them so that they still work when pyshared is present
e.g. edit files only through the default version symlinks

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

On 22.05.2012 01:18, Julian Taylor wrote:
> attached a list of 38 packages from the modules and apps team svn referencing pyshared in their debian folder
> a lot of fixing for pretty much no gain.

can you split these in those, where pyshared is only mentioned in *.install and
*.links files and the rest?

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package python-defaults - 2.7.3-0ubuntu4

---------------
python-defaults (2.7.3-0ubuntu4) quantal; urgency=low

  * Revert 2.7.3-0ubuntu3 as this breaks a large number of packages and the
    benefits of it are unclear (LP: #1001912)
 -- Scott Kitterman <email address hidden> Tue, 22 May 2012 11:23:40 -0400

Changed in python-defaults (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments