On Saturday 04 June 2011 04:45:36 Kouhei Maeda wrote: > Are you saying that, > > python-sphinxcontrib-blockdiag -> python-sphinx-blockdiag > > What a mean?
No, for the Python Policy binary package should be: python-sphinxcontrib.blockdiag, but for source package you can just use upstream project name. I'm packaging sphinxcontrib-spelling (I did't finish because I'm waiting upstream to fix an issue) but you can find my packaging stuff here: http://anonscm.debian.org/viewvc/python-modules/packages/sphinxcontrib spelling/trunk/ The problem related to the namespace is different: to use dh_python2 all packages which share the same namespace must be converted at the same time, but because of python-sphinx-issuetracker (which is already in the archive) we have to use pysupport. Or obviously convince python-sphinx-issuetracker's maintainer to switch too :) HTH, -- Daniele Tricoli 'Eriol' http://mornie.org -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201106052149.40963.er...@mornie.org
