On 13-Jan-2022, Stefano Rivera wrote: > https://ci.debian.net/packages/p/python-coverage/unstable/amd64/ > > E: Unable to locate package pypy-coverage > module-scripts FAIL badpkg > blame: python-coverage
Looking at the test log, the failure is traceable to:
autopkgtest [02:39:33]: test module-scripts: preparing testbed
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib >
Broken autopkgtest-satdep:amd64 Depends on pypy-coverage:amd64 < none @un H
>
Removing autopkgtest-satdep:amd64 because I can't find pypy-coverage:amd64
Nothing in the Debian packaging (nor in the upstream) makes any
reference to ‘pypy-coverage’. What is causing ‘autopkgtest-satdep’ to
declare that dependency?
--
\ “Crime is contagious… if the government becomes a lawbreaker, |
`\ it breeds contempt for the law.” —Justice Louis Brandeis |
_o__) |
Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
