On Tue, 03 Oct 2006, Joey Hess wrote:
Raphael Hertzog wrote:
Yes you should IMO because the current dh_python assumes pycompat==2 if
there's no pycompat file and if there's a Python-Version control field.
That's because pycompat has only been introduced after the start of the
migration
Context for debian-python: we're deprecating dh_python on Joey's request
and thus move the logic of substvars generation into
dh_pycentral/dh_pysupport. debhelper/python-central/python-support will
be jointly uploaded in 2 days (the packages are in DELAYED/2-days right now)
to make that happen.
On Mon, 02 Oct 2006, Pierre Habouzit wrote:
Another problem with smart-notifier is that it calls dh_python but
lacks a pycompat file, so the new dh_python will do old-style stuff
with it, including adding a postinst call to compileall.py.
that's RC then. and a packaging problem, not our
Raphael Hertzog wrote:
Yes you should IMO because the current dh_python assumes pycompat==2 if
there's no pycompat file and if there's a Python-Version control field.
That's because pycompat has only been introduced after the start of the
migration when Josselin decided to change his mind...
Hi,
Attached is the patch for python-central.
I've tested on 5 packages yet, and it seems to work correctly on
packages with public modules. Though it seems that it completely fails
with packages with private modules, (like smart-notifier)
Also note that smart-notifier packaging is
Pierre HABOUZIT wrote:
I've tested on 5 packages yet, and it seems to work correctly on
packages with public modules. Though it seems that it completely fails
with packages with private modules, (like smart-notifier)
Also note that smart-notifier packaging is buggy as it should not ask
Le lun 2 octobre 2006 18:17, Joey Hess a écrit :
Pierre HABOUZIT wrote:
I've tested on 5 packages yet, and it seems to work correctly on
packages with public modules. Though it seems that it completely
fails with packages with private modules, (like smart-notifier)
Also note that
7 matches
Mail list logo
