Hi Fred, On Mon, Oct 15, 2018 at 06:51:09PM +0000, PICCA Frederic-Emmanuel wrote: > Hello Andreas, > > > Patches are welcome (I have no idea what the construct is doing neither > > how to replace it with something valid). > > > Patch welcome as well - preferably as commit to Git. > > done but now, we need to understand why lintian complain about python module > at the wrong place before uploading. > I amnot sure thet the test run as installed...
I can reproduce the wrongly placed / duplicated modules. Its the same observation I made with lmfit-py[1]. While lintian recommends the usage of dh_python3 W: python3-uncertainties: python-module-in-wrong-location usr/lib/python3.7/dist-packages/uncertainties/ usr/lib/python3/dist-packages/uncertainties/ N: N: The package installs a Python module or debug information for a Python N: module in the wrong location for the given version of Python. N: N: dh_python3 can be used to fix this for Python 3 modules. N: N: Refer to Debian Python Policy section 2.5 (Module Path) and N: https://bugs.debian.org/576012 for details. N: N: Severity: normal, Certainty: possible N: N: Check: files, Type: binary, udeb I need to admit I have not found out how to use it properly and thus I simply removed the module in question manually[1]. I admit I'd prefer a better solution as well and since it seems to happen systematically I wonder whether dh-python might have some flaw? Kind regards Andreas. PS: I'd also love to see those useless "fork me on github" privacy breaches go away. It seems these are not part of the uncertainties source but injected by sphinx somehow. [1] https://salsa.debian.org/science-team/lmfit-py/commit/36f5f0456365f59a488a479233aebbf45dd48b05 -- http://fam-tille.de
