Package: python3-numpy
Version: 1:1.21.5-2

Dear Sandro, dear Matthias, dear all:

Why does python3-numpy under bookworm, since a few days, depend on python3.10
*and* on python3.11?

This breaks our software projects that combine C++ with Python.
The CMake command

  find_package(Python3 3.${version_minor_min} REQUIRED
               COMPONENTS Interpreter Development NumPy)

fails with error message

CMake Error at 
/usr/local/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:230 
(message):
  Could NOT find Python3 (missing: Development NumPy Development.Module
  Development.Embed) (found suitable version "3.11.0", minimum required is
  "3.7")
Call Stack (most recent call first):
  /usr/local/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:594 
(_FPHSA_FAILURE_MESSAGE)
  /usr/local/share/cmake-3.23/Modules/FindPython/Support.cmake:3192 
(find_package_handle_standard_args)
  /usr/local/share/cmake-3.23/Modules/FindPython3.cmake:490 (include)
  CMakeLists.txt:154 (find_package)

The new dependences of python3-numpy lead to installation of python3.11-minimal,
which somehow lets CMake believe we have a Python3.11 system.

However, lots of other packages (e.g. xfce and xelatex) depend on 
python3.10-minimal.
So I cannot uninstall that one.

I already experienced (and reported) similar problems with previous increments
of the Python minor version. What could be a global solution?

Kind regards, and thanks for your maintenance work - Joachim


------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Volker Rieke
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr. Astrid Lambrecht,
Prof. Dr. Frauke Melchior
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Reply via email to