Bug 1271701
| Summary: | awk matches lowercase when searching for uppercase range | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | gawk | Assignee: | David Kaspar // Dee'Kej <deekej> |
| Status: | CLOSED ERRATA | QA Contact: | Filip Holec <fholec> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.6 | CC: | deekej, dkutalek, fholec, fkrska, jkurik, kdudka, msaxena, praiskup, psplicha, scott.rochford, thozza, zpytela |
| Target Milestone: | rc | Keywords: | Patch, Reproducer, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gawk-3.1.7-10.el6_7.1 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: In previous versions, the 'gawk' utility was using the POSIX definition as default, when searching for a range patterns of given regular expression. For example, if you used regular expression '[A-Z]', it also matched lowercase symbols of alphabet.
Consequence: This behaviour was not intuitive and was confusing to many users of 'gawk'
Fix: Upstream of the 'gawk' has already introduced patches to change it to the more intuitive behaviour. We have backported all the related changed to the current version of the 'gawk' utility.
Result: After the fix, the 'gawk' utility's regular expressions match only uppercase characters when '[A-Z]' is used. However, the previous behaviour can be still enabled if needed, by using the '--posix' parameter of the 'gawk'.
|
Story Points: | --- |
| Clone Of: | 1250830 | Environment: | |
| Last Closed: | 2015-11-10 09:14:38 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1250830 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2015-10-14 13:59:36 UTC
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. https://rhn.redhat.com/errata/RHBA-2015-2003.html |