Last modified: 2013-02-06 10:29:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T27986, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25986 - Using PCRE Nested named refs do not work
Using PCRE Nested named refs do not work
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.17.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: platformeng, upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-18 10:41 UTC by Sam Reed (reedy)
Modified: 2013-02-06 10:29 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Sam Reed (reedy) 2010-11-18 10:41:58 UTC
Creating as tracking bug against r76938 reversion of r76928
Comment 1 Sam Reed (reedy) 2010-11-18 10:43:32 UTC
Cheers guys for posting the bug upstream
Comment 2 Aaron Schulz 2010-11-24 03:55:53 UTC
Fixed upstream: http://bugs.exim.org/show_bug.cgi?id=1035
Comment 3 Antoine "hashar" Musso (WMF) 2012-03-04 11:04:15 UTC
Since that is fixed upstream an Aaron did a workaround with r77067, maybe we can fix this bug report ?

Tagging bugreport for platform eng since everyone there is part of that team :-)
Comment 4 Tim Starling 2013-02-04 02:03:04 UTC
If by "fixing the bug" you mean reverting the workaround so that MW will segfault if used with PCRE 8.0.1, then we might need to wait a bit longer, since there are still a lot of Linux servers using a distro from 2010. Once we do switch to the new regex, we will have to add an installer environment check for the old library version.
Comment 5 Antoine "hashar" Musso (WMF) 2013-02-06 10:29:15 UTC
No no! I do not want us to break on old PHP setups.

I am just saying our bug report can probably be closed since:
 - our code no more rely on nested named reference
 - upstream has fixed it.

Of course, if we ever want to use nested named reference, we will hit this bug again.

So maybe we are going to keep this bug around till everyone has the fix :-D

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links