[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1002526: python-django-extensions: autopkgtest needs update for new version of pygments: textual change

Source: python-django-extensions
Version: 3.1.5-1
Severity: serious
X-Debbugs-CC: debian-ci@lists.debian.org, pygments@packages.debian.org
Tags: sid bookworm
User: debian-ci@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pygments

Dear maintainer(s),

With a recent upload of pygments the autopkgtest of python-django-extensions fails in testing when that autopkgtest is run with the binary packages of pygments from unstable. It passes when run with only packages from testing. In tabular form:

                         pass            fail
pygments                 from testing    2.10.0+dfsg-1
python-django-extensions from testing    3.1.5-1
all others               from testing    from testing

I copied some of the output at the bottom of this report. Seems like some output was changed a bit.

Currently this regression is blocking the migration of pygments to testing [1]. Of course, pygments shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in pygments was intended and your package needs to update to the new situation.

If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from pygments should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests.

More information about this bug and the reason for filing it can be found on


[1] https://qa.debian.org/excuses.php?package=pygments


=================================== FAILURES =================================== ____ SyntaxColorTagTests.test_should_colorize_noclasses_with_default_lexer _____

self = <tests.templatetags.test_syntax_color.SyntaxColorTagTests testMethod=test_should_colorize_noclasses_with_default_lexer>

        def test_should_colorize_noclasses_with_default_lexer(self):
            ctx = Context({'code_string': '<h1>TEST</h1>'})
            content = """{% load syntax_color %}
    {{ code_string|colorize_noclasses }}
expected_result = '''<div class="highlight" style="background: #f8f8f8"><pre style="line-height: 125%; margin: 0;"><span></span><span style="color: #008000; font-weight: bold">&lt;h1&gt;</span>TEST<span style="color: #008000; font-weight: bold">&lt;/h1&gt;</span>
            result = Template(content).render(ctx)
    >           self.assertHTMLEqual(result, expected_result)

tests/templatetags/test_syntax_color.py:93: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python3/dist-packages/django/test/testcases.py:795: in assertHTMLEqual
    self.fail(self._formatMessage(msg, standardMsg))
E   AssertionError: <div class="highlight" style="background: #f8f8f8">
E <pre style="line-height: 125 [truncated]... != <div class="highlight" style="background: #f8f8f8">
E   <pre style="line-height: 125 [truncated]...
E     <div class="highlight" style="background: #f8f8f8">
E   - <pre style="line-height: 125%;">
E   + <pre style="line-height: 125%; margin: 0;">
E   ?                               +++++++++++
E   E     <span><span style="color: #008000; font-weight: bold">
E     <h1>
E     </span>TEST<span style="color: #008000; font-weight: bold">
E     </h1>
E     </span>
E     </pre>
E     </div>

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply to: