Bug#1118572: pcre2 10.47 behaviour change: different error for ^(a)\g{3

[Matthew Vernon]

Hi

On 11/08/2026 23:27, Simon McVittie wrote:

> So I think that when you're ready to upload a new pcre2 to unstable, 
> glib2.0 will have to be recompiled against it (either asking the release 
> team for a binNMU, or via a sourceful upload), and then they can migrate 
> to testing together. But until then, this bug report doesn't seem 
> actionable: there is nothing reasonable that we can do in unstable that 
> will make glib2.0 handle error codes that don't yet exist in unstable. 
> (I don't think it seems like a good idea to do an #ifndef/#define hard- 
> coding the value we expect newer versions of pcre2 to assign to the new 
> error code...)

Noted.

> If you're checking whether pcre2 (>= 10.48) will make glib2.0 regress, 
> please check that by compiling glib2.0 from source, rather than using 
> its pre-existing binaries.

Thanks for this; I (after a bit of wrangling) have got debusine to 
test-build pcre2 10.47's direct rev-deps (including glib2.0), and 
glib2.0 does build OK there, so I should be able to do equivalent 
testing with a 10.48 RC once it's available.

Regards,

Matthew