Bug#1118572: libpcre2-8-0: pcre2 10.47 behaviour change: different error for ^(a)\g{3
Matthias Klose
doko at debian.org
Fri Sep 4 15:18:46 BST 2026
On 9/4/26 15:36, Simon McVittie wrote:
> Control: block -1 by 1146418
> Control: tags -1 = ftbfs fixed-upstream
>
> On Fri, 04 Sep 2026 at 15:17:24 +0200, Matthias Klose wrote:
>> raising severity, blocking now the re2 migration:
>
> Do you mean the pcre2 migration, or some other transition? (re2 is also
> a package that exists, but it seems to be at the same version in testing
> and unstable)
yes, sorry, pcre2.
>> see https://ci.debian.net/packages/g/glib2.0/testing/amd64/75122155/
>
> This should be fixed by a binNMU rather than by source changes. The
> upstream source handles either the old or new pcre2, but it can only
> handle the new error codes from the updated pcre2 if it was built
> against a suitable pcre2 version.
>
> If we need to do a sourceful upload of glib2.0 for some other reason,
> then that would also resolve this automatically, but a binNMU would
> migrate sooner than a sourceful upload.
>
> smcv
More information about the pkg-gnome-maintainers
mailing list