Bug 484213 - zdiff /tmp/a.gz /tmp/b.gz shows no output
Summary: zdiff /tmp/a.gz /tmp/b.gz shows no output
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gzip
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ivana Varekova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-05 13:36 UTC by Jakub Jelinek
Modified: 2009-03-25 16:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-13 14:50:30 UTC


Attachments (Terms of Use)

Description Jakub Jelinek 2009-02-05 13:36:07 UTC
zdiff both in Fedora 7, 10 and rawhide is buggy, when both files are gzipped, it has correct exit status, but prints no output.
See http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=434275
and zdiff.in.diff patch in recent debian packages.
--- gzip-1.3.12.orig/zdiff.in
+++ gzip-1.3.12/zdiff.in
@@ -104,7 +104,7 @@
                          exec 4>&1
                          (gzip -cdfq -- "$1" 4>&-; echo $? >&4) 3>&- |
                            ( (gzip -cdfq -- "$2" 4>&-; echo $? >&4) 3>&- 5<&- </dev/null |
-                              eval "$cmp" /dev/fd/5 -) 5<&0
+                              eval "$cmp" /dev/fd/5 - >&3) 5<&0
                        )
                        case $gzip_status in
                          *[1-9]*) gzip_status=1;;

Haven't checked RHEL whether the same bug exists there or not.

Comment 1 Ivana Varekova 2009-03-13 14:50:30 UTC
Thanks. For now fixed in gzip-1.3.12-9.fc11. f10 will be soon.

Comment 2 Fedora Update System 2009-03-16 11:39:39 UTC
gzip-1.3.12-8.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/gzip-1.3.12-8.fc10

Comment 3 Fedora Update System 2009-03-25 16:09:59 UTC
gzip-1.3.12-8.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.