[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [MoM] Packaging of python-csb



On Tue, Oct 30, 2012 at 06:48:33PM +0100, Tomás Di Domenico wrote:
> Greetings. Here's my first progress report for the packaging of the CSB
> Toolbox [1].

:-)

> 1) I've created a git repository for the package, which I named
> "python-csb" according to the Debian Python Policy. I hope this is correct.

Well, I need to admit I'm personally have the habit to run into trouble
when touching other peoples repositories - so it might be me that I get:

$ debcheckout --user tille git://git.debian.org/debian-med/python-csb.git --git-track '*'
declared git repository at git+ssh://tille@git.debian.org/git/debian-med/python-csb.git
git clone git+ssh://tille@git.debian.org/git/debian-med/python-csb.git python-csb ...
Cloning into 'python-csb'...
warning: You appear to have cloned an empty repository.
Use of uninitialized value $srcpkg in substitution (s///) at /usr/bin/debcheckout line 822.

and I also tried

 $ git clone git+ssh://git.debian.org/git/debian-med/python-csb.git
Cloning into 'python-csb'...
warning: You appear to have cloned an empty repository.


So either you might have forgotten a `git push` or something else is
wrong here.  I suspect a missing `git push` because I have not seen any
mail on our commit list which should be the case because as far as I can
see at git.debian.org you have properly set the postcommit hook to send
an e-mail.



> 2) I used pbuilder to setup a chroot in my computer. Even after reading
> the pbuilder User's Manual [2], I'm not 100% sure I understand how to
> use the chroot. I suppose that will become clear once I start trying to
> build the package, though.

You can simply use it by saying git-buildpackage if you add the following
to your file ${HOME}/.gbp.conf:

[DEFAULT]
builder = ${HOME}/bin/git-pbuilder

my ~/bin/git-pbuilder looks like this:

$ cat ~/bin/git-pbuilder
#!/bin/sh
set -e

/usr/bin/pdebuild --pbuilder cowbuilder --buildresult `dirname \$PWD` --debbuildopts "-i\.git -I.git $*"  --debsign-k "Andreas Tille <tille@debian.org>"
rm ../*_source.changes
lintian -i ../*.deb ../*.dsc


Please note:  Cowbuilder is some kind of "faster pbuilder" - leave out
the "--pbuilder cowbuilder" for the moment or setup cowbuilder if you
want this.


For a very simple test you can also just use plain command `pdebuild` in
your packaging directory to use pbuilder.

 
> 3) I've followed the first part of the Debian New Maintainer's Guide,
> played around with a toy example, took a look at the generated files, etc.

Fine.
 
> 4) Following the developer's docs on the CSB project site [3], I checked
> out the latest version of the project and built it. The build process
> includes the running of several unit tests. It eventually generates a
> tar.gz file with a format like "csb-1.1.0.tar.gz", which seems preety
> close with the desired format for sources according to the guide.

I might have a look at this once I can clone the git reporitory you
created in 1).
 
> _Question here_ (maybe ahead of myself): the building process also
> builds HTML documentation using python-epidoc. Does this fit into the
> framework of a Debian package?

Yes, for sure.  Any user relevant documentation should be provided in a
binary doc package (for instance named like python-csb-doc).  We have
several examples in Vcs how to do this.  I could also give you a kick
start right in the Git repository.

> In any case, I'd appreciate input on how to go on. The Python package
> building process is probably pretty different from the ones that involve
> standard GNU building tools and the like, so a bit on guidance on how to
> proceed would be great.

I'd suggest the first we should do is to get the git repository properly
to enable me cloning.  Once this is done we should probably write a
debian/watch file to enable simple download of the source and inject
the pristine-tar into the repository.  Once this is done I might have
a look how to reasonably proceed with the build process.  As far as I
can say dh does an amazingly clever job by just using

	dh $@ --with python2

in your debian/rules file and I would be really astonished if this
package should be an exception.

Kind regards

      Andreas.

-- 
http://fam-tille.de


Reply to: