Package: release.debian.org Severity: normal X-Debbugs-Cc: nu...@packages.debian.org Control: affects -1 + src:numpy User: release.debian....@packages.debian.org Usertags: transition
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear Release Team, I'd like to transition NumPy 2 and rebuild all binary Python extensions against the new version. The current NumPy 2 release is backwards compatible with NumPy 1, i.e., extensions built against NumPy 2 will continue to work with NumPy 1.24.x (but not the other way around). Therefore old binary packages will have "Depends: python3-numpy-abi9", and rebuilt binary packages will have "Depends: python3-numpy2-abi0 | python3-numpy-abi9". Below is a suggested Ben file which looked okay when I tested it locally. I may have missed some subtle problems though as this is my first hand-written rule set. title = "NumPy 2"; is_affected = .depends ~ /\bpython3-numpy2?-abi[0-9]+\b/ is_good = .depends ~ /\bpython3-numpy2-abi0\b/; is_bad = .depends ~ /\bpython3-numpy-abi[0-9]+\b/ & ! .depends ~ /\bpython3-numpy2-abi0\b/; Cheers Timo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmbsJg8ACgkQzIxr3RQD 9MpDHRAAviPy2KmXTB2IwT+6Jp0ePbt7IXSmbjnDvE1fZNRJJZT2jZOiEHfnH7x9 MOu9ZhdnIN0l/KR+KB3u5xGqXGDZM//SM47aonCo5PrNcF7X7TEpltKtGM9OqMja d65BCjXzOIOjyUwHjYk2rpM/MOgX0So0PvpCbMGW8AvA4wmBHmGdbgMwloPzY839 gHS6poT0iib6+08NSZv2lJuboOHVotj+VCHT7JvDuLGdvOxFIaBuyS1cdlel0C+B wJvujbJjYRqjMEIy7IKaBqBwST7N3zJbH/UXsvC0kPilnzZF0EedKYESCPUYtQ6z 6xRwATuUPc8N7u/cSzs0WqezhQuWeYqODlR1ZjlKufNptGy2MMvg1aEFzr7jYhvP 1MKcz7RIpJMk0zKjEg29S3TopwHnlc7Sz2GNfl1gTiAOmfbpMJIy0iK/lLkWK0MJ n+k9JXZJZobPO8LQlqnmyxViOKKmrnztn2g6cKO+v5Kic90gBiOEMPZWv5gn5sXo hp1ZtxLHVxYq7AtxKlneDLPx+vefFTPXGGucUJ4oH4SFA2nbWfkqSjkI1rh5hwAn WsCbPoEKgtCzHovvy+SxYLAg9fLpyqaEsEvdROaFAonohCG8fivkfzdw7cHnflXZ BkHhXd1gBXi1j75XHLupnXlrYpRdn4hSiNBcBAo5AHsEuMC0V+E= =G3Ys -----END PGP SIGNATURE-----
