Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#28533 - [pcre] After update to 8.30 there are warnings for preg_match

Attached to Project: Arch Linux
Opened by Bill Seremetis (bserem) - Monday, 20 February 2012, 00:13 GMT
Last edited by Allan McRae (Allan) - Saturday, 16 June 2012, 08:59 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



After upgrading pcre to 8.30 the following warnings appear when tryin to install drupal:
Warning: preg_match(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 2112 in truncate_utf8() (line 339 of /home/sites/drupal7/includes/

There is a thread on this on which might provide some helpful information. In this thread the community located the problem to reside in PCRE 8.30.
The discussion on the matter is happening here:

Additional info:
* package version(s)
PCRE 8.30
APACHE 2.2.22
* config and/or log files etc.

Steps to reproduce:
Install a LAMP environment (apache,php,mysql) and try to install Drupal 7
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 16 June 2012, 08:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  Should be fixed in latest drupal release
Comment by Pierre Schmitz (Pierre) - Monday, 20 February 2012, 00:42 GMT
At a first glance I'd say this is actually a bug in drupal code. They seem to use invalid characters here. An obvious solution would be to remove them. So in includes/ remove "\x{D800}-\x{F8FF}" from line 76. You should check back with drupal devs though.
Comment by Bill Seremetis (bserem) - Monday, 20 February 2012, 00:46 GMT
I'm passing it through!
Comment by Bill Seremetis (bserem) - Monday, 20 February 2012, 01:25 GMT
I proposed a patch on the drupal side here:

Let's see how this goes. I'll updated this issue once something new arises.
Comment by Bill Seremetis (bserem) - Tuesday, 28 February 2012, 22:49 GMT
This is being fixed on the drupal side, it will be available (hopefully) in the upcoming releases at the end of March.

This can be marked as closed/works as intented.

Thanks for the help