Hi! On 20/01/20 12:58, Christoph Berg wrote: > Package: dh-python > Version: 4.20191017 > Severity: normal > > libarcus and libsavitar from the 3dprinting team have the problem > that the cmake jobs called from dh_auto_install use the wrong python > version, note that 3.8 is used in the 3.7 install pass: > > https://salsa.debian.org/3dprinting-team/libsavitar/-/jobs/515849#L935 > > olasd tracked the problem down to find_package(Python3) not working: > > I: pybuild base:217: dh_auto_configure --buildsystem=cmake > --builddirectory="/builds/3dprinting-team/libsavitar/debian/output/libsavitar-4.4.1/.pybuild/cpython3_3.7/build" > -- -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python3.7 > -DPYTHON_LIBRARY:FILEPATH=/usr/lib/python3.7/config-3.7m-x86_64-linux-gnu/libpython3.7m.so > -DPYTHON_INCLUDE_DIR:PATH=/usr/include/python3.7m > ... > -- Found Python3: /usr/bin/python3.8 (found suitable version "3.8.1", minimum > required is "3.4") found components: Interpreter Development > > It looks like dh-python should include Python_EXECUTABLE: > > https://gitlab.kitware.com/cmake/cmake/commit/06d9e67fbd2b2dfc9cba12327866b2f73eab8a18
I might be wrong, but: if by the above you mean that dh-python should get the value returned into Python_EXECUTABLE and pass it over: yes, it's possible. I'm writing this because at first I understood that dh-python should *set* this variable, but that's FindPython's job. Except I am missing something. Cheers, Lisandro.
