Description of problem: internal error in regular expression engine Version-Release number of selected component (if applicable): python-2.7.5-1.fc19.i686 How reproducible: always Steps to Reproduce: # python Python 2.7.5 (default, May 16 2013, 13:43:50) [GCC 4.8.0 20130412 (Red Hat 4.8.0-2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import re >>> re.compile(".*yz", re.S).findall("xyz") Traceback (most recent call last): File "<stdin>", line 1, in <module> RuntimeError: internal error in regular expression engine Additional info: - Does not affect x86_64. - See http://bugs.python.org/issue17998
This bug is now blocking the rebuild of polybori for the new boost release. Is there an ETA on when the upstream patch might be applied? Guessing m4ri compile flags... yes RuntimeError: internal error in regular expression engine: File "/builddir/build/BUILD/polybori-0.8.3/SConstruct", line 1164: pb_symlinks = SymlinkReadableLibname(libpbShared) File "/builddir/build/BUILD/polybori-0.8.3/SConstruct", line 1111: sonameversion = soPattern.findall(path.basename(env.subst('$LIBRARY_VERSION')))[0] RPM build errors: error: Bad exit status from /var/tmp/rpm-tmp.16oa2q (%build) Bad exit status from /var/tmp/rpm-tmp.16oa2q (%build) Child return code was: 1
It seems that the upstream patch is breaking Python builds [1]. I'd rather wait for a complete solution to not break anything else. [1] http://bugs.python.org/issue17998#msg194276
Bummer. I found a workaround for polybori (shelling out to sed, of all things), so it's no emergency for me. Hopefully upstream can find a good fix soon.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.