help-debbugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fix for bug #22945 misteriously vanished from the tree?


From: Fulvio Scapin
Subject: Fix for bug #22945 misteriously vanished from the tree?
Date: Fri, 3 Apr 2020 14:52:42 +0200

Hello.

Today I was about to post a bug for the zstdgrep wrapper of zstd and
as a comparison I was about to quote the fix for bug #22945 which I
myself opened around 4 years ago.
I was using the command to reproduce the bug to show how zgrep
processes things correctly to suddenly discover that it doesn't.
>From the 1.7 changelog of gzip I read, under "Bug fixes"
[...]
 zgrep -f A B C no longer reads A more than once if A is not a regular file.
  This better supports invocations like 'zgrep -f <(COMMAND) B C' in Bash.
  [bug introduced in gzip-1.2]
[...]
In the Savannah cgit I can find commit f0bda0b75a28f6fd2069600f19f7eafa569545e6

( 
http://git.savannah.gnu.org/cgit/gzip.git/commit/?id=f0bda0b75a28f6fd2069600f19f7eafa569545e6
) which affects zgrep.in, NEWS and tests/zgrep-f

However in the history of the current zgrep.in I see no traces of
either the commit or its modifications, while I see both in the other
two files.

Empirically I see, for instance, that the contents of the zgrep
wrapper shipped with versions 1.6 and 1.8 of gzip are identical.

Which means that the bug is not actually close at all AFAIC.

Have I gone mad and started seeing things which are not there?
And if not has anything else been lost along the way?

Regards,
Fulvio Scapin



reply via email to

[Prev in Thread] Current Thread [Next in Thread]