cdbs creates empty bogus directories if Python files are not installed in /usr/lib/python*

Bug #401953 reported by Luca Falavigna
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cdbs (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: cdbs

Some Python applications install files in a private directory (e.g passing --install-lib to setup.py call) and do not touch at all /usr/lib/python*/dist-packages. When this happens, python-distutils.mk tries to create correspondant /usr/lib/python*/site-packages directories, but if /usr/lib/python*/dist-packages are not present, make can't parse jolly characters and creates stale, empty directories such as /usr/lib/python?.?/site-packages (with "?.?" as part of the directory name).

cdbs should check if /usr/lib/python*/dist-packages exists before attempting to create correspondant site-packages directory, attached debdiff fixes this.

Revision history for this message
Luca Falavigna (dktrkranz) wrote :
Changed in cdbs (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cdbs - 0.4.56ubuntu6

---------------
cdbs (0.4.56ubuntu6) karmic; urgency=low

  * 1/class/python-distutils.mk:
    - Check existence of /usr/lib/python*/dist-packages before trying to
      create correspondant /usr/lib/python*/site-packages (LP: #401953).

 -- Luca Falavigna <email address hidden> Thu, 23 Jul 2009 16:06:46 +0200

Changed in cdbs (Ubuntu):
status: Confirmed → Fix Released
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.