On 5/27/21 12:34 PM, David Yoder wrote:
This change is in the SuSE 12 installed zgrep and is not in your upstream gzip
release or git repository. I guess it's a patch added by SuSE?
Yes, I suppose so. I don't know SuSE's changes. I suggest sending SuSE
your bug report. Closing the GNU bug rep
SHORT ANSWER:
Because your results are so different from mine, I tried reproducing on a
personal machine. I tried
* the installed Debian stable gzip 1.9
* downloading the latest gzip 1.10 packaged source
* the git master head
With all three I reproduce your results. And the reason is that zgre
What platform are you running on? Who built zgrep and gzip on your
platform? In what directories are the zgrep and gzip executables? What
is the output of "gzip --version"?
What is the output of the following shell command?
unset BASH_ENV; bash -x ./zgrep -q fox synthetic.log.bz2
Here's the
I've run into a problem with zgrep -q. On some large bz2 compressed files it
returns false/error for a search that should have returned true. bzgrep and
"bzip2 -cd | grep -q" both work as expected.
Either "-q or -l" are required to show the problem. I suspect that grep is
terminating at the fir
