Bug#808842: glib2.0: FTBFS with PCRE 8.38: regex (?(?<ab)) produces different error

[Simon McVittie]

Source: glib2.0
Version: 2.46.2-1
Severity: serious
Tags: upstream patch
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=759808

GLib 2.46.2-2 FTBFS with a regex test failure on all release architectures
except amd64, where it was built by the maintainer. The same test is also
now failing with the prebuilt 2.46.2-1 on ci.debian.net, so this is not
actually a regression in 2.46.2-2; instead, it's a regression in the new
libpcre3.

The problem appears to be that certain invalid regexes are diagnosed
differently (different error code) with PCRE 8.38.
I have sent a report and patch to GNOME (also attached),
<https://bugzilla.gnome.org/show_bug.cgi?id=759808>

X-Debbugs-Cc set to libpcre3 at packages.debian.org. Matthew, it would be
great if you could upload new pcre3 versions to experimental initially,
and/or run the GLib regex test against them before uploading to unstable
(install libglib2.0-tests and run
"/usr/lib/glib2.0/installed-tests/glib/regex" - no special options are
needed, and it will exit 0 for success or nonzero for failure).

Regards,
    S
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-regex-test-expect-ASSERTION_EXPECTED-for-ab-with-PCR.patch
Type: text/x-diff
Size: 1768 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20151223/55f48737/attachment.patch>