Hide Forgot
Description of problem: Checking /usr/share/man/man3/pcrecpp.3.gz for whitespace: FAIL Checking /usr/share/man/man3/pcrebuild.3.gz for runtime: FAIL Checking /usr/share/man/man3/pcre_compile.3.gz for whitespace: FAIL Checking /usr/share/man/man3/pcresyntax.3.gz for whitespace: FAIL Checking /usr/share/man/man3/pcresyntax.3.gz for formfeed: FAIL Checking /usr/share/man/man3/pcreapi.3.gz for Whitespace: FAIL Checking /usr/share/man/man3/pcreapi.3.gz for whitespace: FAIL Checking /usr/share/man/man3/pcreapi.3.gz for formfeed: FAIL Checking /usr/share/man/man3/pcrepattern.3.gz for whitespace: FAIL Checking /usr/share/man/man3/pcrepattern.3.gz for formfeed: FAIL Checking /usr/share/man/man3/pcre.3.gz for whitespace: FAIL Checking /usr/share/man/man3/pcre_compile2.3.gz for whitespace: FAIL Version-Release number of selected component (if applicable): pcre-devel-7.8-4.el6 How reproducible: ALways Steps to Reproduce: 1. grep man pages from pcre-devel for these misspelled words: 2. whitespace, runtime, formfeed, Whitespace 3. Actual results: These words are present. Expected results: white space, run-time, form feed, White space Additional info:
Patch posted to upstream (http://bugs.exim.org/show_bug.cgi?id=1245).
Created attachment 584369 [details] Fix ported to pcre-7.8
Comment on attachment 584369 [details] Fix ported to pcre-7.8 The patch has been accepted by upstream as SVN revision r968.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause Reading some pcre manual pages (e.g. pcre(3)). Consequence Some misspellings can get linguists dizzy. Fix Form feed, run-time, and white space have been corrected in all pcre manual pages. Result pcre manual pages write form feed, run-time, and white space correctly now.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-1240.html