After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 689791 - update to pcre 8.35+
update to pcre 8.35+
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gregex
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on: 684222
Blocks: 679155
 
 
Reported: 2012-12-06 18:13 UTC by Christian Persch
Modified: 2018-05-24 14:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Persch 2012-12-06 18:13:34 UTC 
PCRE 8.32 has just been released. Apart from many bug fixes, it has improved unicode case-insensitive matching, and now supports \X.

The update is not trivial since it depends on bug 684222 for the unicode grapheme cluster data, and it also will also need to access the internal special casing table from glib. I may have to rewrite how PCRE accesses the glib unicode data for that...
Comment 1 Simon McVittie 2014-07-20 19:30:27 UTC 
Also, some tests are failing with a system PCRE 8.35: Bug #733325.
Comment 2 Simon McVittie 2015-12-23 11:05:42 UTC 
PCRE 8.38 was recently uploaded to Debian, and the GLib installed-tests are failing (with a previously-compiled GLib now linked at runtime to the new PCRE):

ERROR:/build/glib2.0-ocmJ1Y/glib2.0-2.46.2/./glib/tests/regex.c:129:test_new_fail: assertion failed (error == (g-regex-error-quark, 142)): Error while compiling regular expression (?(?<ab)) at char 3: assertion expected after (?( (g-regex-error-quark, 128)

I haven't yet investigated whether this is a PCRE or GLib bug. If it seems to be GLib's fault, I'll open a separate bug for that.
Comment 3 Christian Persch 2015-12-23 11:40:22 UTC 
That's due to a bug fix in pcre: svn://vcs.exim.org/pcre/code/trunk@1539
Comment 4 Simon McVittie 2015-12-23 14:45:56 UTC 
(In reply to Simon McVittie from comment #2)
> I haven't yet investigated whether this is a PCRE or GLib bug. If it seems
> to be GLib's fault, I'll open a separate bug for that.

Bug #759808
Comment 5 GNOME Infrastructure Team 2018-05-24 14:53:11 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/642.