bug#30597: closed (Bug: error messages from gunzip)

[GNU bug Tracking System]

Your message dated Wed, 30 Mar 2022 10:51:58 -0700
with message-id <d3999279-60f1-eb74-c659-9826b41344bc@cs.ucla.edu>
and subject line Re: Bug: error messages from gunzip
has caused the debbugs.gnu.org bug report #30597,
regarding Bug: error messages from gunzip
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
30597: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30597
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: Bug: error messages from gunzip Date: Sat, 24 Feb 2018 20:39:57 +0000

Hi,

I'm using gunzip 1.5 on Amazon Linux 2017.03.

When running gunzip /nonexistent/*gz, the error message from gunzip is very misleading: gzip:  /nonexistent/*gz.gz: No such file or directory

It's misleadng in two ways:

1. it refers to gzip, when I was running gunzip

2. it refers to a file specification that I did not provide, by naively appending .gz to the file spec

Doubtless you have bigger fish to fry.

Thanks,

John

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: Bug: error messages from gunzip
>
>
>
>
> Date: 
>
> Wed, 30 Mar 2022 10:51:58 -0700
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
>
>
>
>
> > When running gunzip /nonexistent/*gz, the error message from gunzip is very 
> > misleading: gzip:  /nonexistent/*gz.gz: No such file or directory
> >
> > It's misleadng in two ways:
> >
> > 1. it refers to gzip, when I was running gunzip
>
> Yes, gunzip merely calls "gzip -d", so the message is coming from from 
> gzip which does what it does regardless of who calls it.
>
> > 2. it refers to a file specification that I did not provide, by naively 
> > appending .gz to the file spec
>
> Yes, that's what gzip -d does: if you say "gzip -d foo" it wants to 
> decompress foo.gz because "foo" doesn't end in ".gz". In your case the 
> file name was "/nonexistent/*gz" and since that doesn't end in ".gz" it 
> looked for "/nonexistent/*gz.gz" and didn't find it.
>
> > Doubtless you have bigger fish to fry.
>
> Yes, that sounds right. Closing the bug report.
>
>
> --- End Message ---