On Mon, Jan 27, 2025 at 03:48:12PM +0100, Timo Röhling wrote:
> Package: lintian
> Version: 2.121.1
> Severity: normal
> Control: affects -1 src:numpy
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Dear maintainer,
>
> with the new major version, the minor ABI counter has reset and the virtual
> package for the NumPy ABI has been updated.
>
> The check in lib/Lintian/Check/Binaries/Prerequisites/Numpy.pm should be
> adjusted to python3?-numpy2?-abi\d+ (note the "2").
>
> There is an additional wrinkle that the first ABI release of NumPy 2 is
> backwards compatible with NumPy 1, so dh_numpy adds
>
> Depends: python3-numpy2-abi0 | python3-numpy-abi9
>
> at the moment. This will likely change again with future ABI bumps , but
> until
> then, it invalidates lintian's assumption that the virtual ABI package should
> not have alternatives.
>
> Lastly, the explicit dependency on python3-numpy is no longer generated for
> ABI dependent packages, so the check for strictly versioned dependencies on
> python3-numpy is obsolete, too.
Not a regression but an old bug is that the
if ( $item->name=~ m{^usr/lib/(?:pyshared/)?python2\.\d+/.*(?<!_d)\.so$}
|| $item->name
=~ m{^ usr/lib/python3(?:[.]\d+)? / \S+ [.]cpython- \d+ - \S+ [.]so $}x
)
misses libraries like /usr/lib/x86_64-linux-gnu/libboost_numpy313.so.1.83.0
Since there is already an ELF check above, I'd suggest dropping this
filename check when updating the lintian check.
> Cheers
> Timo
cu
Adrian
