Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: nu...@packages.debian.org
Control: affects -1 + src:numpy
User: release.debian....@packages.debian.org
Usertags: pu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
[ Reason ]
python3-numpy has an undeclared file conflict on /usr/bin/f2py with
python-numpy. Even though python-numpy is gone, it is possible to have that
package linger on systems, which will affect the upgrade to bookworm
(#1053649).
Note that python3-numpy in bullseye did *not* yet with the conflicting file,
so it possible for python-numpy to coexist on a fully upgraded bullseye
installation, only triggering this issue with the upgrade to bookworm.
[ Impact ]
Users who upgrade to bookworm and still have python-numpy installed will
experience an unpack error during the upgrade.
[ Tests ]
I did not test the upgrade scenario because I consider the change trivial and
the regression risk non-existent.
[ Risks ]
The fix declares a package conflict with a package that is no longer part of
bookworm (or bullseye, for that matter), so it will have no effect on new or
existing bookworm installs.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[ ] the issue is verified as fixed in unstable
[ Changes ]
The binary package python3-numpy will now declare a conflict on python-numpy.
This will ensure that python-numpy is uninstalled during the bookworm upgrade.
[ Other info ]
Regarding a potential fix for unstable:
As the python-numpy package is no longer shipped, it cannot be reintroduced
after a proper upgrade to bookworm, which is why I decided to not declare the
conflict in trixie/sid.
There is a remote possibility that another package will gain a new dependency
on python3-numpy going from bookworm to trixie, so technically, a python-numpy
package could survive the bookworm upgrade and then conflict with the trixie
upgrade. If that is a concern, I will add the conflict in trixie/sid as well.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmY3Q7oACgkQzIxr3RQD
9Mr3nxAAycMncFSAnDkiqT/Cu1AWs5RtECLt94UZ862GUi3WkkhSBMEbkxpI5ums
2CvpfA2CRAp2FkoaNY23YmL+yo8JpN5iAHHEvVKsabvNytV+PDkM4bXLe58O9llp
87TIxohuMUAjsW7huizYRJlvNTqPcwSYLDaM/V6Cr2tbeV8cSFdoUfCIoR+10F6q
B9Whp9x+kJaXiNMJ6tIG3uvK0C2FsHMArqNUBVrqDXOakjFgBajwJcuh9fs6/cLQ
Ur2ZlW8clTbIdltZGGmU+pc3Syg5QTUTHQ7JQP59MrLs7AqqqN1N7VssEetOJikS
bnjc9oiVlYzCQVKCabaYJWm/2qw0fUESSyBxH47RAZqTZ5U/NvSgRyWVnumDBYpT
3tkgVcRDJQwksKH07IdCBlOXjlGsm6awa7O45j1Gz0UMXLR7/zhBX3STm4+cF/78
Jk+tNREQ/UGZkjxwhWC910/JcdxsSN4iUXZKWhdMipJSqmBHeAKdBILB4A7ShFuH
dSneIl2vTOo/kC8dhdXSXN2Gzs1t4JuNrQRAs5hKLtj9ABwFwea9FzEDiWJHnygs
MK+o+ILto3c6DS/p24DgkyoGrxw7NlHAxl0Jl1WBnFv4YeuOtJoCVLNHbY4pSbyt
jOklCDgF81Ib2o7nxUXw5I8euRCq/NSpfEgXhGhEFFnUCt/lowI=
=IcBC
-----END PGP SIGNATURE-----
diff --git a/debian/changelog b/debian/changelog
index 9953311b..776d076f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+numpy (1:1.24.2-1+deb12u1) bookworm; urgency=medium
+
+ * Declare conflict with python-numpy due to f2py (Closes: #1053649)
+
+ -- Timo Röhling <roehl...@debian.org> Sun, 05 May 2024 09:56:59 +0200
+
numpy (1:1.24.2-1) unstable; urgency=medium
* New upstream release
diff --git a/debian/control b/debian/control
index 6d723b4a..92fd0f24 100644
--- a/debian/control
+++ b/debian/control
@@ -37,6 +37,7 @@ Provides: dh-sequence-numpy3,
python3-numpy-dev,
${numpy3:Provides},
${python3:Provides},
+Conflicts: python-numpy
Description: Fast array facility to the Python 3 language
Numpy contains a powerful N-dimensional array object, sophisticated
(broadcasting) functions, tools for integrating C/C++ and Fortran
diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 00000000..69a939b5
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,4 @@
+[DEFAULT]
+debian-branch = bookworm
+upstream-branch =
+
