NetBSD Problem Report #36268

From giles-bounce-1178195718.19240-gnats-bugs=gnats.NetBSD.org@epsilon.pair.com  Thu May  3 12:35:22 2007
Return-Path: <giles-bounce-1178195718.19240-gnats-bugs=gnats.NetBSD.org@epsilon.pair.com>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id C6BF663B853
	for <gnats-bugs@gnats.NetBSD.org>; Thu,  3 May 2007 12:35:21 +0000 (UTC)
Message-Id: <20070503123518.19240.qmail@netherstone.net>
Date: 3 May 2007 22:35:18 +1000
From: giles.lean@pobox.com
Reply-To: giles.lean@pobox.com
To: gnats-bugs@NetBSD.org
Subject: NetBSD gzip error message mismatch with GNU gzip
X-Send-Pr-Version: 3.95

>Number:         36268
>Category:       bin
>Synopsis:       NetBSD gzip error message mismatch with GNU gzip
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 03 12:40:01 +0000 2007
>Closed-Date:    Mon Aug 08 06:48:31 +0000 2016
>Last-Modified:  Mon Aug 08 06:48:31 +0000 2016
>Originator:     Giles Lean
>Release:        NetBSD 4.0_BETA2
>Organization:

>Environment:


System: NetBSD amethyst.netherstone.net 4.0_BETA2 NetBSD 4.0_BETA2 (AMETHYST) #8: Tue May 1 22:23:20 EST 2007 unpriv@amethyst.netherstone.net:/usr/local/NetBSD/netbsd-4/obj/sys/arch/i386/compile/AMETHYST i386
Architecture: i386
Machine: i386
>Description:
When NetBSD's gzip sees premature end of file on standard input it
emits a slightly different message to the one GNU gzip prints.

This difference broke a test case in GNU tar 1.16.

GNU gzip prints a blank line, and does not surround (stdin) with
parentheses.
>How-To-Repeat:
$ ./gzip --version
gzip 1.3.9
Copyright (C) 2006 Free Software Foundation, Inc.
Copyright (C) 1993 Jean-loup Gailly.
This is free software.  You may redistribute copies of it under the terms of
the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
There is NO WARRANTY, to the extent permitted by law.

Written by Jean-loup Gailly.
$ ./gzip < /dev/null > /dev/null
$ ./gzip -d < /dev/null > /dev/null

gzip: stdin: unexpected end of file
$ /usr/bin/gzip --version
NetBSD gzip 20060927
$ /usr/bin/gzip -d < /dev/null > /dev/null
gzip: (stdin): unexpected end of file
$

>Fix:


>Release-Note:

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: bin/36268: NetBSD gzip error message mismatch with GNU gzip
Date: Thu, 3 May 2007 14:48:07 +0200

 I personally like the NetBSD gzip message better - so I'd say either gnu zip
 should be adjusted or the tar configure script be fixed.

 Martin

From: Giles Lean <giles.lean@pobox.com>
To: gnats-bugs@NetBSD.org
Cc: gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: bin/36268: NetBSD gzip error message mismatch with GNU gzip 
Date: Fri, 04 May 2007 00:35:02 +1000

 Martin Husemann <martin@duskware.de> wrote:

 >  I personally like the NetBSD gzip message better - so I'd say
 >  either gnu zip should be adjusted or the tar configure script be
 >  fixed.

 I agree that the NetBSD message is neater.

 If the NetBSD gzip(1) command is intended as a drop-in
 replacement for the GNU one, then I think this is one of those
 times when standard is better than better.

 It's not a serious issue either way, and you may note I filed
 the bug report with 'low' severity. :-)

 If it's decided to close the bug report without change (not
 what I recommend, naturally) at least the difference is
 documented in the PR.

 Regards,

 Giles

From: "matthew sporleder" <msporleder@gmail.com>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: bin/36268
Date: Sat, 19 Jan 2008 18:54:09 -0500

 If you just want to close the bug..

 --- gzip.c.orig	2008-01-19 18:51:06.000000000 -0500
 +++ gzip.c	2008-01-19 18:51:22.000000000 -0500
 @@ -1580,7 +1580,7 @@
  		maybe_warn("can't read stdin");
  		return;
  	} else if (bytes_read != sizeof(header1)) {
 -		maybe_warnx("(stdin): unexpected end of file");
 +		maybe_warnx("stdin: unexpected end of file");
  		return;
  	}

State-Changed-From-To: open->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 08 Aug 2016 03:50:00 +0000
State-Changed-Why:
this got fixed at some point


State-Changed-From-To: closed->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 08 Aug 2016 04:38:59 +0000
State-Changed-Why:
no such luck, misread.
not sure this is really worth doing...


State-Changed-From-To: open->closed
State-Changed-By: mrg@NetBSD.org
State-Changed-When: Mon, 08 Aug 2016 06:48:31 +0000
State-Changed-Why:
while the goal is to be bug-compatible, i think after almost a decade
and considerable external adoption since, this is not a problem to
really worry about and given our preferrable output, let's not do this.


>Unformatted:
 	Built from 2007-04-29 source.

Home	PR Database Search