Dear Debian Pythonistas,
the NumPy 2 transition is now on its way, and while many packages
seem to rebuild quite nicely, there are a few gotchas I'd like to
point out, so everyone does not need to figure this out on their
own.
1. We did some work to improve cross build support in NumPy [1],
which means that dh-sequence-numpy3 can no longer pull the native
Python module. If you encounter weird ModuleNotFoundErrors, you
probably need to add python3-numpy as an explicit dependency.
2. The NumPy module hierarchy has changed in a way that breaks code
trying to compute the include path to the NumPy headers on its own.
If you encounter build errors where GCC fails to find headers such
as numpy/arrayobject.h, make sure you use the intended API to
configure the build [2].
3. Lintian has yet to catch up with the changed virtual package for
the NumPy ABI [3], so you might see a few spurious "missing-dependency-on-numpy-abi" diagnostics.
Cheers
Timo
[1]
https://bugs.debian.org/1076236
[2]
https://numpy.org/doc/stable/reference/generated/numpy.get_include.html
[3]
https://bugs.debian.org/1094364
--
⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │
⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmeY8noACgkQzIxr3RQD 9Mq1uQ//UQ3ZQ8U9YxDrkP+MYVyu+EoaaccSOtGj3y2VtPszXeAJPHz2UeCBrYyd FSsMWU12OwhnWPr+D8yHyRoqMIl4h1VGhNE+u8MsNMDiw9EtnOg250k31GLBDR63 oA5V68vqBOPC9j4P43J8NO8ZVSNEHDPryJtD53wiIV8MHnOhcM6cje32RU25YwZ4 UKGBdrp/neBUW1ci455roveNZNJO4ksvwWQcrT5n43ZAG218BQL/rUHymTi50OzB 2PKLCsxbaZajEfaXVEpIgY0ufF11M1Cf9RIbtXWOgnYRdywFW/artJqaOhT+KzEI 5IUG8Vfn4yuhiQLwMfkh3Khm82BCsMM94wMtXmpPrLI