GNU bug report logs - #30597
Bug: error messages from gunzip

Previous Next

Package: gzip;

Reported by: John Docherty <john_docherty <at> hotmail.com>

Date: Sat, 24 Feb 2018 20:52:01 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 30597 in the body.
You can then email your comments to 30597 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-gzip <at> gnu.org:
bug#30597; Package gzip. (Sat, 24 Feb 2018 20:52:01 GMT) Full text and rfc822 format available.
Acknowledgement sent to John Docherty <john_docherty <at> hotmail.com>:
New bug report received and forwarded. Copy sent to bug-gzip <at> gnu.org. (Sat, 24 Feb 2018 20:52:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: John Docherty <john_docherty <at> hotmail.com>
To: "bug-gzip <at> gnu.org" <bug-gzip <at> gnu.org>
Subject: Bug: error messages from gunzip
Date: Sat, 24 Feb 2018 20:39:57 +0000

[Message part 1 (text/plain, inline)]
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


[Message part 2 (text/html, inline)]
Reply sent to Paul Eggert <eggert <at> cs.ucla.edu>:
You have taken responsibility. (Wed, 30 Mar 2022 17:53:02 GMT) Full text and rfc822 format available.
Notification sent to John Docherty <john_docherty <at> hotmail.com>:
bug acknowledged by developer. (Wed, 30 Mar 2022 17:53:02 GMT) Full text and rfc822 format available.

Message #10 received at 30597-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: John Docherty <john_docherty <at> hotmail.com>
Cc: 30597-done <at> debbugs.gnu.org
Subject: Re: Bug: error messages from gunzip
Date: Wed, 30 Mar 2022 10:51:58 -0700

> 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.
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Thu, 28 Apr 2022 11:24:04 GMT) Full text and rfc822 format available.
This bug report was last modified 1 year and 357 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.