[Bug 1940996]

[Vincent-srcware]

(In reply to eggert from comment #15)
> glibc bug 11053 is fixed,

Shouldn't this bug be resolved as fixed, then?

> but Debian bug 884075 is not fixed. Perhaps a better match for 
> Debian bug 884075 is glibc bug 10844.

It seems different. With Debian bug 884075, the "|^1?$" part is
important (it yields the incorrect output, even though this part isn't
matched), and there is nothing like that in glibc bug 10844:

vinc17 at gcc92:~$ echo 11111111111 | grep --color=auto -E '^(11+)\1+$|^1?$'
11111111111
vinc17 at gcc92:~$ echo 11111111111 | grep --color=auto -E '^(11+)\1+$'
vinc17 at gcc92:~$ 

Note that for the first command, nothing is colored in "11111111111",
i.e. the line is output as appeared to be matched, but no matches are
shown by colors. As a comparison, with ten 1s instead of eleven, the
line is output and the ten 1s are colored.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1940996

Title:
  test failure - test-regex

Status in grep:
  Fix Released
Status in grep package in Ubuntu:
  New

Bug description:
  'test-regex' fails when building grep against glibc 2.34.
  Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, 
  the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1940996/+subscriptions