Hi Arian
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
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
--
Stuart Prescott http://www.nanonanonano.net/ [email protected]
Debian Developer http://www.debian.org/ [email protected]
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
