Re: Building Python debug extensions with dh

2010-08-10 Thread Jakub Wilk
* Yaroslav Halchenko , 2010-08-10, 11:48: * It appears that more packages have gotten the issue in #576014 wrong that right. as I've heard at debconf10 but haven't looked into/tried myself, dh_python2 (instead of support) might be doing the right thing out of the box... True. It works out-of-t

Bug#592533: lintian: check for missing dependency on python-central

2010-08-10 Thread Jakub Wilk
Package: lintian Version: 2.4.3 Severity: wishlist If a binary package ships /usr/share/pyshared-data/PACKAGENAME file, it should have dependency on at least python-central (>= 0.6). Normally missing/insufficient dependency on python-central indicates that ${python:Depends} was omitted from D

Re: Building Python debug extensions with dh

2010-08-10 Thread Yaroslav Halchenko
Thank you Christian and Jakub for the nice wiki! > * It appears that more packages have gotten the issue in #576014 wrong > that right. as I've heard at debconf10 but haven't looked into/tried myself, dh_python2 (instead of support) might be doing the right thing out of the box... --

Building Python debug extensions with dh

2010-08-10 Thread Christian Kastner
A mentor recently proposed that I ship -dbg versions of a Python extension. Researching on how to properly do so, it appeared that there was no standard approach to this. On the contrary, I found numerous differing implementations, with quite a few exhibiting some flaws. I chose to follow the appr

Bug#592491: lintian: check for missing dependency on python-support

2010-08-10 Thread Jakub Wilk
Package: lintian Version: 2.4.3 Severity: wishlist If a binary package ships files in /usr/share/python-support/, it should have at least unversioned dependency on python-support. If a binary package ships a /usr/share/python-support/PACAKGENAME.public or /usr/share/python-support/PACKAGENAME