Your message dated Sat, 26 Mar 2022 22:34:40 +0100
with message-id <c360dc30-650a-f363-99fe-bea012591...@debian.org>
and subject line Re: mercurial: autopkgtest needs update for new version of
pygments: output changed
has caused the Debian Bug report #1006383,
regarding mercurial: autopkgtest needs update for new version of pygments:
output changed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1006383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mercurial
Version: 6.0.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, pygme...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pygments
Dear maintainer(s),
With a recent upload of pygments the autopkgtest of mercurial 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.11.2+dfsg-2
mercurial from testing 6.0.2-1
all others from testing from testing
I copied some of the output at the bottom of this report.
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 no mistake and your package needs to update to the new
situation.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pygments
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mercurial/19499363/log.gz
---
/tmp/autopkgtest-lxc.ah1_xlbq/downtmp/build.zaO/src/tests/test-run-tests.t
+++
/tmp/autopkgtest-lxc.ah1_xlbq/downtmp/build.zaO/src/tests/test-run-tests.t.err
@@ -176,14 +176,14 @@
running 1 tests using 1 parallel processes \x1b[38;5;124m---
$TESTTMP/test-failure.t\x1b[39m (esc)
- \x1b[38;5;34m+++ $TESTTMP/test-failure.t.err\x1b[39m (esc)
+ \x1b[38;5;28m+++ $TESTTMP/test-failure.t.err\x1b[39m (esc)
\x1b[38;5;90;01m@@ -1,4 +1,4 @@\x1b[39;00m (esc)
- $ echo "bar-baz"; echo "bar-bad"; echo foo
- \x1b[38;5;34m+ bar*baz (glob)\x1b[39m (esc)
- bar*bad (glob)
+ \x1b[38;5;250m \x1b[39m $ echo "bar-baz"; echo "bar-bad"; echo foo (esc)
+ \x1b[38;5;28m+ bar*baz (glob)\x1b[39m (esc)
+ \x1b[38;5;250m \x1b[39m bar*bad (glob) (esc)
\x1b[38;5;124m- bar*baz (glob)\x1b[39m (esc)
\x1b[38;5;124m- | fo (re)\x1b[39m (esc)
- \x1b[38;5;34m+ foo\x1b[39m (esc)
+ \x1b[38;5;28m+ foo\x1b[39m (esc)
\x1b[38;5;88mERROR:
\x1b[39m\x1b[38;5;9mtest-failure.t\x1b[39m\x1b[38;5;88m output
changed\x1b[39m (esc)
!
ERROR: test-run-tests.t output changed
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 6.1-4
Hi,
On Thu, 24 Feb 2022 19:27:56 +0100 Paul Gevers <elb...@debian.org> wrote:
With a recent upload of pygments the autopkgtest of mercurial fails in
testing when that autopkgtest is run with the binary packages of
pygments from unstable.
Apparently this has been fixed with the last upload.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
