[Patches] [ python-Patches-1054967 ] bdist_deb - Debian packager

[SourceForge.net]

Patches item #1054967, was opened at 2004-10-27 02:48
Message generated for change (Comment added) made by alberanid
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1054967&group_id=5470

Category: Distutils and setup.py
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Submitted By: Geoffrey T. Dairiki (dairiki)
Assigned to: Sean Reifschneider (jafo)
Summary: bdist_deb - Debian packager

Initial Comment:
Here's a first crack at a bdist_deb.

This patch implements two new distutils commands:

bdist_deb:
  Build Debian packages
  
debianize:
  Create and populate a top-level debian subdirectory.
  (Essentially dh_make for distutils packages.)

There is a slightly detailed README.bdist_deb included
in the patches.

I'm open to suggestions for improvements and bug-fixes.



----------------------------------------------------------------------

Comment By: Davide Alberani (alberanid)
Date: 2004-10-30 10:57

Message:
Logged In: YES 
user_id=170840

I've tried the 29/10 patch with my home system (dpkg-dev 1.10,
debhelper 4.1.90 and dh-make 0.30) and another "pure woody"
system (dpkg-dev 1.9.21, debhelper 4.0.2 and dh-make 0.30).

I've used your test suite and some of my personal projects
(using both bdist_deb and dh_make); as far as I can tell, it
works very well. :-)

bdist_deb always worked as expected, producing good debian
packages.

I've used dh_make and then I've run "dpkg-buildpackage
-rfakeroot" and I got some errors (but I'm not sure they
depends on your code).  Also your test suite produced some
failures.

Here you can find the output of "dpkg-buildpackage -rfakeroot"
and of your tests suite (both were running on my home system):
  http://erlug.linux.it/~da/tmp/dpkg-buildpackage
  http://erlug.linux.it/~da/tmp/testsuite


Thank you for your great effort!

----------------------------------------------------------------------

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2004-10-29 21:38

Message:
Logged In: YES 
user_id=45814

Thanks for the comments.  Here's a second attempt.

Changes include:

It might work with woody.  (I'd appreciate it if you could
try again, Davide)

'debianize' command renamed to 'dh_make'.

Use debchange to create debian/changelog.  This eliminates
the need to duplicate debchange's logic to deduce the
packagers name and e-mail.

A more complete test script.


Patches are on today's CVS.

----------------------------------------------------------------------

Comment By: Davide Alberani (alberanid)
Date: 2004-10-27 16:47

Message:
Logged In: YES 
user_id=170840

I've a woody with some packages backported from sarge
(debhelper 4.1.90 and dpkg-dev 1.10).

Running python2.3 ./setup.py bdist_deb with some of
my projects, I got the error:

dpkg-buildpackage: unknown option or argument
--check-dirname-level=1
Debian dpkg-buildpackage .

Commenting out the "check-dirname-level" and
"check-dirname-regex" options in the bdist_deb.py file
the script can go on, but it exits with the error:

debian/rules:11: *** first argument to `word' function must
be greater than 0.  Stop.

Hope this helps.

----------------------------------------------------------------------

Comment By: Sean Reifschneider (jafo)
Date: 2004-10-27 05:44

Message:
Logged In: YES 
user_id=81797

I'm just doing a review of this code.  A couple of things:

   There's been some concern expressed about
get_default_maintainer.
   Namely, that if debchange changes it's algorithm, it won't be
   reflected in this code.  It seems like one possible way
around that
   would be to build a directory with a "debian" directory
under it, a
   fake "changelog", and then call debchange to write the
data out, and
   parse it.  Too bad there's not a direct hook into
debchange to get
   that information.

   Can _formatdate, if email doesn't exist, use
rfc822.formatdate()?

   Ditto for _parseaddr?

It looks pretty good.  However, when trying to build a .deb
of my
jotweb2 package, it's failing with:

   [...]
   dh_testdir
   dh_testroot
   dh_installchangelogs-
   dh_installdocs
   cp: cannot stat `doc': No such file or directory
   dh_installdocs: command returned error code 256
   [...]

I'm not sure exactly why.  I do have a "doc" directory in my
main
package directory, but I don't reference to it in my setup.py or
MANIFEST.  Adding it to the MANIFEST doesn't seem to help this.

Sean

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1054967&group_id=5470