loggerhead: autopkgtest regression: No module named 'pygments'

[Bryce Harrington]

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/lib/python3/dist-packages/breezy
   bzr-3.2.2 python-3.10.7 Linux-5.19.0-15-generic-x86_64-with-glibc2.36

unittest.loader._FailedTest.breezy.plugins.loggerheadERROR 1ms
    No module named 'loggerhead.tests'
======================================================================
ERROR: unittest.loader._FailedTest.breezy.plugins.loggerhead
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/breezy/plugins/loggerhead/__init__.py", line 122, in load_tests
    from .loggerhead.tests import test_suite
ModuleNotFoundError: No module named 'breezy.plugins.loggerhead.loggerhead'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/breezy/plugins/loggerhead/__init__.py", line 124, in load_tests
    from loggerhead.tests import test_suite
ModuleNotFoundError: No module named 'loggerhead.tests'
----------------------------------------------------------------------
Ran 1 test in 0.003s

FAILED (errors=1)
autopkgtest [07:46:22]: test testsuite: -----------------------]

Debian bug #1016452 reports this same issue (See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016452), and lists it as fixed in the changelog for 2.0.0-1 however we're still seeing the issue. Debian also sees the same failure in their 2.0.0-1 build logs, e.g.:

https://ci.debian.net/data/autopkgtest/testing/amd64/l/loggerhead/25906806/log.gz

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://ci.debian.net/data/autopkgtest/testing/amd64/l/loggerhead/26647914/log.gz

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://ci.debian.net/data/autopkgtest/testing/amd64/l/loggerhead/26647914/log.gz

https://ci.debian.net/data/autopkgtest/testing/amd64/l/loggerhead/26647914/log.gz

[Bryce Harrington (bryce)]

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.

[Bryce Harrington (bryce)]

python3-pygments is listed as an installation Recommends for the loggerhead binary.
If the tests complain about pygments missing, then python3-pygments may also need to be added as a Depends for testsuite in d/t/control.

[Sergio Durigan Junior (sergiodj)]

As Bryce mentioned above, the error now refers to the missing pygments Python module. I filed another bug against the Debian package with a proposed patch, update this bug's title to reflect the new error, and update the Debian bug reference here.