Your message dated Mon, 03 Nov 2025 22:05:47 +0000
with message-id <[email protected]>
and subject line Bug#1118572: fixed in glib2.0 2.86.1-2
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 ---
Source: glib2.0
Source-Version: 2.86.1-2
Done: Simon McVittie <[email protected]>
We believe that the bug you reported is fixed in the latest version of
glib2.0, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie <[email protected]> (supplier of updated glib2.0 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 03 Nov 2025 18:50:56 +0000
Source: glib2.0
Architecture: source
Version: 2.86.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
<[email protected]>
Changed-By: Simon McVittie <[email protected]>
Closes: 1118572
Changes:
glib2.0 (2.86.1-2) unstable; urgency=medium
.
* d/p/gresolver-Fix-loopback-detection-of-IPv6-addresses.patch,
d/p/glib-tests-regex-Add-a-future-proof-test-case-for-missing.patch,
d/p/gregex-Handle-PCRE2_ERROR_MISSING_NUMBER_TERMINATOR-if-de.patch,
d/p/tests-regex-Add-the-error-messages-to-tests.patch,
d/p/gutils-Strip-all-trailing-slashes.patch:
Add bug fixes from upstream glib-2-86 branch up to 2.86.1-8-g61384f791d.
In particular this should fix test failures with pcre2 10.47
(Closes: #1118572)
* d/control: Drop B-D on docbook-xml, docbook-xsl, xsltproc.
The man pages are now written in reStructuredText rather than Docbook
XML, so we no longer need these.
* d/control: Add comments clarifying the meaning of non-trivial build
profile conditions
* d/watch: Convert to uscan format v5
Checksums-Sha1:
674282104536d312c41c45381892af9fee5082f5 5063 glib2.0_2.86.1-2.dsc
5662ffbaf8b3836bcc4f90fc7053642bdaae3478 143428 glib2.0_2.86.1-2.debian.tar.xz
6beacfee777af25c5e0ce263d3d0f2794641e0c9 16242040 glib2.0_2.86.1-2.git.tar.xz
f4e327303c3af1723ea259944e0b6cb60cd656a2 18222
glib2.0_2.86.1-2_source.buildinfo
Checksums-Sha256:
3c6d7a5546ca1d8dc8b6b35648e1f7aace385f182eee128585b12f8859f5fc3a 5063
glib2.0_2.86.1-2.dsc
51250cbc1dd11b614545f7f0f7248dec1b1ff7bea3954cfe0a51add4a921e1b4 143428
glib2.0_2.86.1-2.debian.tar.xz
21e9036fdb49faef09281cb25facb3ec233932ff85b5d5914f7bbea590b6e0c5 16242040
glib2.0_2.86.1-2.git.tar.xz
a9781e24d9dd236705faadc949a508eb73fb453ca5aa2ddbc4a3b3386875d235 18222
glib2.0_2.86.1-2_source.buildinfo
Files:
3040b8e2da445b8989ef122f73a6df90 5063 libs optional glib2.0_2.86.1-2.dsc
2d95f0798a4beeb6d0a74b269c627dce 143428 libs optional
glib2.0_2.86.1-2.debian.tar.xz
30cdcabfe7861de67abe71cf4e7862fb 16242040 libs optional
glib2.0_2.86.1-2.git.tar.xz
e5f86cf81969940ee87855c60ee5d239 18222 libs optional
glib2.0_2.86.1-2_source.buildinfo
Git-Tag-Info: tag=c258d7e548f32cd31d333251f021b643476f5da9
fp=7a073ad1ae694fa25bff62e5235c099d3eb33076
Git-Tag-Tagger: Simon McVittie <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmkJI3cACgkQYG0ITkaD
wHlS0g/9GLkSa9xCAOhJGIw19Dm4dwQOWvTndjvM5+Hf3O8vjT/POk8oEl5ejkVf
+TtfQi+4dR9zT+8PbpHM+umKmjBNQW/27vg8HWD3TUYsj87ZeSq0LZkgLcfsuQ/q
8RnhfqQUynLwdh6lEyX5vppnewCinOy4stIgIbPC0CrAed8MdnRCXZOrxJlDgTpw
Wp4vck8kjCLCBQzPhZ88TdDapp9tmMzlp4A+bnnmtJy5B1RD0nsQ+cTwNMfvKuTd
QbP1R+kMrJbzN5yDBq5DfQp4A0MIbRn6bfvM/Jt8XXx7EGCGSli+cEy3nMFfK4uo
8ZF2uzibxbYC8GIb/pOaYWeUn64t7hM2xDjE5p2EOCdBI/l/9EKGgrASO5JUriv5
lJdpgDzU0rNCKCvzeS+wGkm4YBEuc+5+kpIA1giPZoNSDTOSctEQtCwCPoI0eOpq
AUlnvIk0QVMJ09x39l8j0qNGtZWROKzEENDw0LlqRo5FA6tim8jtObUYzR346mgn
sgX+7FgKSWWSebiOr31RDfYq90jSqpWOYrUOHZT0bX/ax6sa5wBJsCTIsYDVTFfC
eUs3jIE6+krBQTt15Bz8benoszREYaA8gJB2XwJQ/4S36uaotuaegx/qATqvyQ4M
hYILzh/L41OvyrPXidZUsWwbrgF39yOSV5i/SZCHM8DAiEzIryM=
=ccxT
-----END PGP SIGNATURE-----
pgpk4KhsYbPEr.pgp
Description: PGP signature
--- End Message ---
