Please merge capisuite 0.4.5-9 (universe) from Debian unstable (main)

Bug #378069 reported by Nick Ellery
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
capisuite (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: capisuite

Please merge capisuite 0.4.5-9 (universe) from Debian unstable (main).

 capisuite (0.4.5-9) unstable; urgency=low

   * QA upload.
   * Move to quilt patch system.
     + Convert existing patches to quilt.
   * 030_sox_call.diff. Remove -w option from call to sox. (Closes: #519062).
     + Thanks to Michael Kaaden.
   * 040_python26.diff. Build with Python 2.6. (Closes: #520656).
     + Thanks to Savvas Radevic for the patch.
   * Change exim depends to exim4. (Closes: #420275).
   * Replace obsolete gs depends with ghostscript.
   * Bump debhelper build-dep and compat to 5.
   * Bump Standards Version to 3.8.1. (No changes needed).

 -- Barry deFreese <email address hidden> Fri, 01 May 2009 10:42:21 -0400

Revision history for this message
Nick Ellery (nick.ellery) wrote :

The python2.6 transition change was fixed in Debian too, so the only change left is the dependency on postfix over exim. I've submitted a bug to Debian requested an alternative depend be added on postfix so the package can be synced in the future.

capisuite (0.4.5-9ubuntu1) karmic; urgency=low

  * Merge from debian unstable, remaining changes (LP: #378069):
    - Prefer postfix as MTA

 -- Nick Ellery <email address hidden> Mon, 18 May 2009 12:10:32 -0700

Revision history for this message
Nick Ellery (nick.ellery) wrote :
Revision history for this message
Andreas Moog (ampelbein) wrote :

Nick, I tried building your package but it FTBFS:

dh_gencontrol
dh_md5sums
dh_builddeb
Found files in /usr/lib/python2.6/site-packages (must be in dist-packages for python2.6).
debian/capisuite/usr/lib/python2.6/site-packages
debian/capisuite/usr/lib/python2.6/site-packages/cs_helpers.py
dh_builddeb: dpkg-deb returned exit code 1
make: *** [binary-arch] Error 1
dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit status 2
E: Failed autobuilding of package

It is python2.6 policy that distribution-packages should go to dist-packages, not site-packages.

Thanks.

Changed in capisuite (Ubuntu):
assignee: nobody → Nick Ellery (nick.ellery)
importance: Undecided → Wishlist
status: New → Incomplete
Revision history for this message
Nick Ellery (nick.ellery) wrote :

Hmm... this is an old bug report which apparently I never subscribed sponsors for prior to becoming MOTU. Something must have caused it to FTBFS between then. I'll have a look at it.

Revision history for this message
Andreas Moog (ampelbein) wrote :

Nick, I've seen you uploaded this to karmic, but it FTBFS there also. FYI: When building your package with pbuilder, use 'sudo pbuilder --build --extrapackages pkgbinarymangler *.dsc' . That way, your pbuilder-environment will resemble more closely the buildd and you can test better if your package builds.

Revision history for this message
Nick Ellery (nick.ellery) wrote :

I don't exactly know why it FTBFS, as it built fine in my PPA (https://edge.launchpad.net/~nick.ellery/+archive/ppa). Are you aware of how to fix this FTBFS?

Revision history for this message
Nick Ellery (nick.ellery) wrote :

Ah, here we go. I fixed this by editting debian/patches/040_python26.diff as such:

-python_moduledir=$pythondir
-python_moduleexecdir=$pyexecdir
+python_moduledir="${python_libdir}/dist-packages"
+python_moduleexecdir="{python_libdir}/dist-packages"

Just to be sure I'm doing this right, would you mind test building this too before I upload it? I've attached a debdiff (this also includes another requested change).

Revision history for this message
Andreas Moog (ampelbein) wrote :

That looks good and builds fine, thanks for your work. You want to upload it yourself?

Revision history for this message
Nick Ellery (nick.ellery) wrote :

I've uploaded it myself. Thanks a lot for testing it out for me.

Changed in capisuite (Ubuntu):
assignee: Nick Ellery (nick.ellery) → nobody
status: Incomplete → 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.