loggerhead: autopkgtest regression: No module named 'pygments'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
loggerhead (Debian) |
Fix Released
|
Unknown
|
|||
loggerhead (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
loggerhead (2.0.0-1) is encountering the following autopkgtest failures in kinetic, on all architectures:
autopkgtest [07:46:21]: test testsuite: [------
running 0 tests...
brz selftest: /usr/bin/brz
/usr/
bzr-3.2.2 python-3.10.7 Linux-5.
unittest.
No module named 'loggerhead.tests'
=======
ERROR: unittest.
-------
Traceback (most recent call last):
File "/usr/lib/
from .loggerhead.tests import test_suite
ModuleNotFoundE
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/
from loggerhead.tests import test_suite
ModuleNotFoundE
-------
Ran 1 test in 0.003s
FAILED (errors=1)
autopkgtest [07:46:22]: test testsuite: -------
Debian bug #1016452 reports this same issue (See https:/
https:/
They indicate it's fixed in their newer version:
loggerhead (2.0.0-2) unstable; urgency=medium
* Run tests from source since they are no longer installed. Closes:
#1019509
-- Jelmer Vernooij <email address hidden> Sun, 11 Sep 2022 02:05:36 +0100
However, it looks like there may still be an issue with pygments:
https:/
There are unrelease changes in git towards a 2.0.0-3 but they look more like packaging cleanup; I don't think they include a fix for the pygments issue.
https:/
https:/
Changed in loggerhead (Debian): | |
status: | Unknown → New |
Changed in loggerhead (Debian): | |
status: | Unknown → New |
Changed in loggerhead (Debian): | |
status: | New → Fix Released |
I've syncpackage'd loggerhead to 2.0.0-2, on the off chance it happens to pass ok, but am leaving this bug open due to the expected pygments issue.
I'm guessing that may need some d/control tweak for the dependency.