[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1082237: marked as done (transition: numpy 2)

Your message dated Mon, 24 Feb 2025 23:17:39 +0100
with message-id <0f5ba548-8733-422a-84e9-9675143a3855@debian.org>
and subject line Re: Bug#1082237: transition: numpy 2
has caused the Debian Bug report #1082237,
regarding transition: numpy 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1082237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082237
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: numpy@packages.debian.org
Control: affects -1 + src:numpy
User: release.debian.org@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-----

--- End Message ---
--- Begin Message --- 
On 17/02/2025 09:02, Andrey Rakhmatullin wrote:

On Tue, Feb 11, 2025 at 11:57:14PM +0500, Andrey Rakhmatullin wrote:

I removed the packages that were failing to build, but there's a few that
are good in the tracker but are failing their autopkgtests. Some of them
don't have bugs filed. Can you look at them [1] and file bugs as
appropriate?


All of them should have bugs filed at this stage, and I've just rechecked
that. The only ones that don't have them are python-soxr (needs a rebuild
but is blocked by a build-dep bug), scikit-learn and spectral-cube (both
fail because of joblib).


Failing key packages:

joblib
seaborn
sympy (for an unrelated reason)



These all are fixed now.

So, looking at https://release.debian.org/transitions/html/numpy2.html and
https://tracker.debian.org/pkg/numpy and skipping packages fixed in sid,
these seem to be the unfixed ones:

bmtk (autoremoval in 4 days)
mdanalysis
mdp
meep
pyrr
python-hug (RM bug exists)
python-meshplex
python-pbcore
python-qmix
python-soxr


After a few hints, numpy has now migrated.

Cheers,
Emilio

--- End Message ---
Reply to: