Your message dated Sun, 16 Mar 2025 00:31:34 +0200
with message-id <Z9X/xgJStKvao4Mn@localhost>
and subject line Fixed in 1:2.2.3+ds-4
has caused the Debian Bug report #1099078,
regarding dh_numpy3 should emit ABI dependencies only when necessary
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 [email protected]
immediately.)
--
1099078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099078
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-numpy-dev
Severity: normal
Maintainers often don't understand whether or not an ABI
dependency is necessary.
Fixing the missing-dependency-on-numpy-abi lintian check (#1094364)
is the most important part since missing dependencies can cause
breakage.
But packages that needlessly build depend on dh-sequence-numpy3
(we already have such packages in the archive) should not require
manual changes, dh_numpy3 should automatically detect whether or
not an ABI dependency is necessary.
dh_numpy3 should do something similar to missing-dependency-on-numpy-abi
for determining whether or not an ABI dependency is necessary.
A further step would be dh_python3 automatically calling dh_numpy3
when python3-numpy-dev is installed, removing the manual work
as well as the need for a lintian tag that checks this manual work.
--- End Message ---
--- Begin Message ---
Version: 1:2.2.3+ds-4
numpy (1:2.2.3+ds-4) unstable; urgency=medium
* Add --force option to dh_numpy3 and improve detection
...
-- Timo Röhling <[email protected]> Sat, 01 Mar 2025 22:25:17 +0100
numpy (1:2.2.3+ds-3) unstable; urgency=medium
* Make dh_numpy3 smarter about adding ABI dependencies
...
-- Timo Röhling <[email protected]> Fri, 28 Feb 2025 14:47:44 +0100
--- End Message ---
