cj 2.0.1 in maverick is missing computerjanitord/__init__.py

Bug #586088 reported by Barry Warsaw
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
computer-janitor (Ubuntu)
Fix Released
Critical
Barry Warsaw

Bug Description

Binary package hint: computer-janitor

mvo pushed cj 2.0.1 up to maverick for me, but that package is broken. The problem is that the orig.tar.gz did not have the computerjanitord package in it, and because computerjanitord/__init__.py is an empty file, it does not appear in the diff.gz. Thus when the binary package got installed, everything in computerjanitord got installed *except* the __init__.py. So Python does not recognize /usr/share/computerjanitor/computerjanitord as a package and the import from computerjanitord fails, crashing c-j-gtk.

I'm not entirely sure what the right answer is. #debian-python suggests touching the __init__.py in debian/rules, or that the problem is caused by the debian/ directory in the source tree in the first place. None of these seem entirely satisfactory though.

Tags: udd
Revision history for this message
Barry Warsaw (barry) wrote :

Note that cj 2.0.1 in my PPA does not suffer the same problem as the package in maverick. I think that's because there was no orig.tar.gz to diff against, and the orig.tar.gz got built and pushed into my PPA, whereas for maverick it used the orig.tar.gz from Lucid.

tags: added: udd
Changed in computer-janitor (Ubuntu):
assignee: nobody → Barry Warsaw (barry)
milestone: none → maverick-alpha-1
importance: Undecided → Critical
status: New → Confirmed
Barry Warsaw (barry)
Changed in computer-janitor (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.