Package: python3-aiostream
Version: 0.5.2-1
Severity: important
X-Debbugs-Cc: stu...@debian.org
Dear Maintainer,
In version 0.5.2-1, there is an attempt to remove coverage outputs from
the binary package. Unfortunately, this is ineffective when there is
more than one Python interpreter in the archive.
The coverage output is originally in an interpreter-specific directory
debian/*/usr/lib/python3.x/dist-packages, and then dh_python3 moves it
to debian/*/usr/lib/python3/dist-packages/ only if the files are
identical. If the files differ for each interpreter, then dh_python3
complains loudly and leaves them where they are.
execute_after_dh_python3:
# Drop cov-generated files
rm -fv debian/*/usr/lib/python3/dist-packages/.coverage
rm -fvr debian/*/usr/lib/python3/dist-packages/htmlcov
When python3-all started to include python3.12 as a supported
interpreter, these files came back, for example:
2
usr/lib/python3.12/dist-packages/htmlcov/d_880e183adc9afb61___init___py.html
3
usr/lib/python3.12/dist-packages/htmlcov/d_880e183adc9afb61_advanced_py.html
4
usr/lib/python3.12/dist-packages/htmlcov/d_880e183adc9afb61_aggregate_py.html
5
usr/lib/python3.12/dist-packages/htmlcov/d_880e183adc9afb61_combine_py.html
Widening the removal pattern to be 'python3*' is sufficient. (Perhaps
dh_python3 should add these directories to its list of well-known
directories to not include in the package.)
Thanks to Paul Gevers for noticing this in various tests with britney to
include reproducibility output in migrations.
