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 own. > > > I thought that making dh_python a NOOP if there was a pycompat file > > was good enough, but this package seems to say otherwise? It seems > > that dh_python also needs to be a NOOP if Python-Version is set. Can > > someone verify that for me?
Yes I confirm that. > well, you can do that too, but using dh_python to generate the substvars > for the new policy needed a pycompat if using dh_py* + dh_python. > That's a packaging problem. You should not care about it. 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... Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
