Ah, thanks for pointing out. I understood it as the changes in grep 2.23
were deliberate, and during xenial this caused quite a lot of fallout
which we fixed.
Reverting the behavior for C makes sense. Thus now we still need to find
the actual fix in gnulib. Applying the doc and test to grep itself is
still worthwhile though and should absolutely be part of the SRU.
** Also affects: grep (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: grep (Ubuntu Yakkety)
Importance: High
Assignee: Martin Pitt (pitti)
Status: Confirmed
--
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/1547466
Title:
grep switches into binary mode while processing a text file
Status in grep package in Ubuntu:
Confirmed
Status in grep source package in Xenial:
New
Status in grep source package in Yakkety:
Confirmed
Bug description:
I noticed this staring to happen in Xenial about two days ago. When
running sbuild (or now the buildd, too), the build breaks when trying
to compile a generated file. I traced the problem down to grep
suddenly acting weird. When not having any language set (or a non-UTF8
mode) it will start printing some lines of a source file and then
suddenly end that by printing "Binary file ... matches".
With the attached file, the difference can be observed (running
Xenial):
LANG=C grep -v xxx grant_table.h
and
LANG=C.UTF-8 grep -v xxx grant_table.h
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466/+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
