Python Modules Packaging Team
Howdy, This sounds like a good initiative. I'd like to add the python-modules-team as uploader of pyvtk, a package I maintain. Do I understand correctly that this implies I should put pyvtk into the alioth subversion repository? If so: sign up user 'smr' for this. Cheers, -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC/RFS: python-enchant -- spellchecking library for Python
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Piotr Ozarowski wrote: > I'm looking for a sponsor for python-enchant (ITP #299783). > Package is lintian/linda clean and builds in pbuilder. > > * Package name: python-enchant > Version : 1.1.5 > Upstream Author : Ryan Kelly <[EMAIL PROTECTED]> > * URL : http://pyenchant.sourceforge.net/ > * License : LGPL with a special exception to link to non-free > spell checker backend (e.g. Microsoft Office > spell checker) > Description : spellchecking library for Python > > PyEnchant consists of Python binding to Enchant spellchecking > library and some wrapper classes. It includes all the functionality > of Enchant in Pythonic object-oriented interface, and also provides > some higher-level functionality than is available in the C API. > > > I have also updated my gaupol package, so now it recommends > python2.4-enchant > > Both packages can be downloaded from: http://debian.pox.one.pl/ > > BTW: I have permission to take over from Seo Sanghyeon Hi Piotr, I just had a look at your packaging as present in the Python module svn. I noticed several things: - - the repo contains only the debian/ dir, but the mergeWithUpstream property is missing. You can set it with $ svn propset mergeWithUpstream 1 debian - - you should use debhelper (>= 5) and set debian/compat to 5 - - have you considered switching to cdbs? For a python module, the debian/rules file boils down to: == begin #!/usr/bin/make -f include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/python-distutils.mk clean:: # hack (CDBS bug -- see #300149) -rm -rf build == end and I'm not sure if the clean:: hack is still needed. - - it's a matter of taste, but I think that compressing the example is not needed. With dh_make, you can just add the flag -X.py to dh_compress to excluded python files from compression. - - there are some grammar mistakes in the package descriptions: PyEnchant consists of Python binding*s* to *the* Enchant spellchecking library and some wrapper classes. It includes all the functionality of Enchant in *a* Pythonic, object-oriented interface and also provides some higher-level functionality *which is not* available in the C API. Apart from that, it looks good to me. Maybe you could also add a short statement about the license of the Debian packaging, along the lines of [1]. best, Torsten [1] http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html - -- Torsten Marek <[EMAIL PROTECTED]> ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858 Keyserver: subkeys.pgp.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEQOkWfMVFHqJEyFgRAiahAJ9ZUUqz624oqzjghfUiEnZzIOYQWwCgpof4 Z0cn97DwsJRSfV6/zaKs5sg= =BGut -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC/RFS: python-enchant -- spellchecking library for Python
> "Torsten" == Torsten Marek <[EMAIL PROTECTED]> writes: Torsten> clean:: # hack (CDBS bug -- see #300149) -rm -rf build == Torsten> end and I'm not sure if the clean:: hack is still needed. Hello, I have tried to build pcapy without doing 'rm -rf build' but even with -tc, i have at the end of the build the build directory. So this bug doesn't seem to be fix... Regards, Arnaud Fontaine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC/RFS: python-enchant -- spellchecking library for Python
Torsten Marek ([EMAIL PROTECTED]): > - the repo contains only the debian/ dir, but the mergeWithUpstream property > is > missing. You can set it with > $ svn propset mergeWithUpstream 1 debian > - you should use debhelper (>= 5) and set debian/compat to 5 done > - have you considered switching to cdbs? For a python module, the debian/rules cdbs generates bad packages, f.e. it builds .egg files, clean rule is not working, it compresses exemple .py files (my rule is not doing it anymore :) > - it's a matter of taste, but I think that compressing the example is not > needed. With dh_make, you can just add the flag -X.py to dh_compress to > excluded > python files from compression. done > - there are some grammar mistakes in the package descriptions: fixed > Maybe you could also add a short statement about the license of the Debian > packaging, along the lines of [1]. done Thanks for your comments! -- -=[ Piotr Ozarowski ]=- -=[ http://www.ozarowski.pl ]=- pgpgSJHQgLTHB.pgp Description: PGP signature
Re: RFC/RFS: python-enchant -- spellchecking library for Python
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Piotr Ozarowski wrote: > Torsten Marek ([EMAIL PROTECTED]): >> - the repo contains only the debian/ dir, but the mergeWithUpstream property >> is >> missing. You can set it with >> $ svn propset mergeWithUpstream 1 debian >> - you should use debhelper (>= 5) and set debian/compat to 5 > > done > >> - have you considered switching to cdbs? For a python module, the >> debian/rules > > cdbs generates bad packages, f.e. it builds .egg files, clean rule is > not working, it compresses exemple .py files (my rule is not doing it > anymore :) Hi, To suppress compression of .py files, use DEB_COMPRESS_EXCLUDE := .py Do you use an option to suppress creation of .egg files? Add it to DEB_PYTHON_BUILD_ARGS The cdbs documentation is at https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml best, Torsten - -- Torsten Marek <[EMAIL PROTECTED]> ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858 Keyserver: subkeys.pgp.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEQQ0YfMVFHqJEyFgRAlzaAJ4tgRWifCKoYAqyAIr6mhQ7IMK9awCfTgWZ RxNwnL3v6RdIOOEvzy1tJZQ= =WOxq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Python Modules Packaging Team
Hi, On Sat, 15 Apr 2006, Steve M. Robbins wrote: > This sounds like a good initiative. I'd like to add the > python-modules-team as uploader of pyvtk, a package I maintain. Good! > Do I understand correctly that this implies I should put pyvtk into > the alioth subversion repository? If so: sign up user 'smr' for this. Yes, you should maintain your package in the SVN repository. You have been added to the project. You will have commit rights tomorrow. Welcome to the group! Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#362532: ITA: python-medusa
> I have prepared a new package using cdbs. However, i saw that there is > already a debian/ directory into the upstream source, so i have removed > it. I don't know if it was a good idea to do that ? I think there is no fixed rule, and usually the best thing to do is coordinate with upstream. However, I (the previous maintainer) never successfully communicated with upstream. Maybe you will have better luck, or you will just have to make your own judgement call. Jeff
