(In reply to [email protected] from comment #13) > The master branch has been updated by Paul Eggert <[email protected]>: > > https://sourceware.org/git/gitweb.cgi?p=glibc.git; > h=0b5ca7c3e551e5502f3be3b06453324fe8604e82 > > commit 0b5ca7c3e551e5502f3be3b06453324fe8604e82 > Author: Paul Eggert <[email protected]> > Date: Tue Sep 21 07:47:45 2021 -0700 [...] > * Fix glibc bug 11053.
What is the status of this bug? The comment says that it is fixed, and I could check on an Ubuntu 22.04.1 LTS machine with libc6 2.35-0ubuntu3.1 that regbug.c and rebug2.c no longer fail, but the result is still incorrect with the grep example from Debian bug 884075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884075 vinc17@gcc92:~$ echo 11111111111 | grep -E '^(11+)\1+$|^1?$' ; echo $? 11111111111 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: In Progress 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
