Dear Maintainer,

pynpoint is not compatible with numpy 2.x - it makes use of methods that
are long-since removed from numpy. Running the upstream test suite
shows that the package is quite broken at present:

The Debian packaging for pynpoint doesn't run any tests at build time and,
as noted in #1035214, also does not run any autopkgtest tests. Adding these
tests in would have spotted this problem over a year ago when numpy 2.x was
uploaded to Debian.

Stuart

Hello Stuart,

thanks for raising this.

I have spoken to upstream about this and the problem is that the pytests of
pynpoint all require external assets which cannot be reproduced by us.

https://github.com/PynPoint/PynPoint/issues/432

The absence of autopkgtest isn't ideal. To fix that I suggest to implement a
smoke test which tests pynpoint as a package. That way we have an autopkgtest
which fails whenever pynpoint fails. Not ideal either but at least a step in
the right direction..

What do you think?

Best regards,

Hi Arian

There are a few options for the Debian packaging.

- Build-time tests can't download data, and so some minimalist smoke
tests would be handy.

- If it's only some of the tests that need the remote data files, then
skipping them at build time and running the test would work. That is
most often done from debian/rules (such as PYBUILD_TEST_ARGS) or with a
patch to mark them as skip/skipif on some condition that you can set
from d/rules.

- autopkgtest test _can_ download data for the purposes of running
tests; the test needs to decleare a 'needs-internet' restriction.

A common pattern is that a subset of non-internet-using tests are run on
the buildd but then all tests are run in autopkgtests.

regards
Stuart