* Jakub Wilk <jw...@debian.org>, 2011-08-07, 22:29:
2) Do not skip the "Before you begin"[0] step. This is very important:
if two packages share a namespace, either both or none of them must use
python-support. Also, it's not enough just to convert them all to
dh_python2: you must make sure (using Breaks or Depends relationships)
that you cannot co-install an older python-support-based versions
together with dh_python2-based ones.
An alternative might be using this trick:
http://docs.python.org/library/pkgutil.html#pkgutil.extend_path
(Though a convenient place to insert the code might not exist in some
cases.)
This is what I did in my two packages:
http://anonscm.debian.org/viewvc/python-modules/packages/gamera/trunk/debian/patches/namespace-package.diff?revision=21262&view=markup
http://anonscm.debian.org/viewvc/python-modules/packages/sphinx/trunk/debian/patches/sphinxcontrib_namespace.diff?revision=20343&view=markup
I set up a page to track this kinds of issues in unstable[2] and
testing[3]. Please note that I analyse only package contents, not
relationships. The tracker is updated daily. (Any volunteers to file
bugs?)
The pages moved to:
[2] http://people.debian.org/~jwilk/python/namespace/conflicts-unstable.txt
[3] http://people.debian.org/~jwilk/python/namespace/conflicts-testing.txt
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120503194108.ga5...@jwilk.net
