(Warning: I don't actually maintain any Python modules, only programs.) On Sun, 2003-06-29 at 13:45, Kai Hendry wrote: > Today I have spent a few hours trying to package a python library called > lupy. > > http://www.divmod.org/Lupy/ > > Firstly, I think there is Debian Python Policy. But I can't find it. Any > clues? /usr/share/doc/python/python-policy.txt.gz > I thought the debian/ was a set of basic control files that assembles > the sources below it. Pretty much anything can go in debian/. I have't looked at this case specifically, but a full copy of the source tree does seem kind of odd, but not against policy. (If you built the package before checking, that's how the source tree got there.) > I ran dh_make and it seem to have created a whole host of unnecessary > files... > > I tried dh_python: > hendry@bilbo:~/lupy-package/python-lupy-0.1.5.2$ dh_python > Can't stat debian/python-lupy: No such file or directory > at /usr/bin/dh_python line 124 > > Is it looking for some sort of structure like pyblosxom that I mentioned? dh_python isn't like dh_make; it's called from your maintainer scripts to compile .py files to pyc/pyo files. > Other questions. How do I replace bilbo (my machine's name) <hendry@bilbo> > with a proper email extension? export EMAIL="your@email.org" > Do I edit the changelog with a special tool? Emacs has a Debian changelog mode, and there's a program called "dch", but I don't use either. You can just use a normal text editor. -- Joe Wreschnig <piman@debian.org>
Attachment:
signature.asc
Description: This is a digitally signed message part