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 > for XS-P-V: 2.4 but >= 2.3 if not all.
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. 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? > though that does not changes a damn thing, and would break other > packages anyway. > > > I don't know what we can do right now… Well, the other thing we could do is put a private copy of dh_python into pycentral (not in path) and make dh_pycentral call it and be otherwise unchanged. Very ugly and it might mean that pycentral would inherit RC bugs like #381389 from dh_python. -- see shy jo
signature.asc
Description: Digital signature
