Bug 637940 - breaks backwards compat
Summary: breaks backwards compat
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: grep
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-27 19:42 UTC by Bill Nottingham
Modified: 2014-03-17 03:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-11 13:48:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bill Nottingham 2010-09-27 19:42:34 UTC
Description of problem:

See bug 637594, bug 636552, etc.

We're already well past feature freeze. Any reason this can't be held for F-15?

Version-Release number of selected component (if applicable):

2.7-1

Comment 1 Jaroslav Škarvada 2010-09-27 20:20:03 UTC
It passed testing with enough karma. I am sorry, I and probably all testers have no idea how many packages that uses grep are broken. But please note the catched REs are probably not doing what they are intended for and this observation can prevent many problems and hidden bugs.

In case this is blocker, I can differ from upstream and patch grep not to fail on these REs for F14.

Comment 2 Jaroslav Škarvada 2010-09-27 21:12:44 UTC
Or revert to 2.6.

Comment 3 Jaroslav Škarvada 2010-10-11 13:48:16 UTC
The bug 637594 is currently on QA, the bug 636552 is closed.

There were no change in RE syntax. Rejected REs mostly indicate bugs, that should be fixed and were not noted before. With older greps such REs were silently accepted with in most cases different behaviour than intended. You can force grep-2.7 to do the same by setting POSIXLY_CORRECT environment variable.

I think the failure here is much more better behaviour than silent accept with incorrect/buggy results. Also I consider reverting to be not good idea, thus closing this. If you do not agree feel free to reopen.


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