Your message dated Wed, 9 Sep 2026 17:58:15 +0200
with message-id
<caaajcmaczmmh+xhtkatv15lmon62p6pmrg3oggctvb678te...@mail.gmail.com>
and subject line Re: Bug#1118572: libpcre2-8-0: pcre2 10.47 behaviour change:
different error for ^(a)\g{3
has caused the Debian Bug report #1118572,
regarding libpcre2-8-0: pcre2 10.47 behaviour change: different error for
^(a)\g{3
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 [email protected]
immediately.)
--
1118572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118572
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpcre2-8-0,libglib2.0-0
Severity: serious
Control: found -1 pcre2/10.47-1
Control: found -1 glib2.0/2.86.1-1
User: [email protected]
Usertags: regression
Tags: ftbfs experimental
Control: block 902060 by -1
With the new pcre2 in experimental, GLib's "as-installed" tests fail
during autopkgtest. This can most easily be reproduced in a container
(in this example Podman, but use whatever is your favourite
chroot/container techology):
$ podman run --rm -it docker.io/debian:sid-slim
# sed -i -e 's/Suites: sid/& experimental/'
/etc/apt/sources.list.d/debian.sources
# apt update
# apt upgrade
# apt install --no-install-recommends libglib2.0-tests
# /usr/libexec/installed-tests/glib/regex; echo $?
...
0
# apt install libpcre2-8-0/experimental
# /usr/libexec/installed-tests/glib/regex ; echo $?
...
not ok /regex/new-fail/78 -
ERROR:../../../glib/tests/regex.c:133:test_new_fail: assertion failed (error ==
(g-regex-error-quark, 157)): Error while compiling regular expression
?^(a)\g{3? at char 8: syntax error in subpattern number (missing terminator?)
(g-regex-error-quark, 0)
Bail out!
Aborted (core dumped) /usr/libexec/installed-tests/glib/regex
134
I'm reasonably sure this would also make glib2.0 FTBFS (hence the ftbfs
tag) although I haven't verified this.
The test failure is that GLib is expecting that compiling the
(incomplete) regex "(a)\g{3" will produce PCRE2_ERROR_BACKSLASH_G_SYNTAX
(which it translates to GRegexError number 157,
G_REGEX_ERROR_MISSING_BACK_REFERENCE), but in fact it saw some error code
that is not specifically handled by translate_compile_error() in
glib/gregex.c, resulting in the default error, G_REGEX_ERROR_COMPILE.
Was this an intentional behaviour change in PCRE?
There might be other assertion failures after this one is addressed, I
haven't checked that yet.
smcv
--- End Message ---
--- Begin Message ---
Version: 2.89.4-2+b1
--- End Message ---
