Date: Wed, 06 May 2009 21:39:09 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de> Cc: freebsd-current@freebsd.org, openoffice@freebsd.org Subject: Re: gunzip | tar reports broken pipe during OOO build on amd64. Message-ID: <4A0265ED.4070407@freebsd.org> In-Reply-To: <20090506192603.GA56228@wep4035.physik.uni-wuerzburg.de> References: <20090505174831.GA40305@wep4035.physik.uni-wuerzburg.de> <3GBQgy9AhtC1kpgclCTM4BIxKP8@AbNt2aYVonA6XSQc9As8EVwIk24> <20090506032832.GB45796@wep4035.physik.uni-wuerzburg.de> <92cd2ff70905060501vaaf67bdnaee1be72e04f1ef8@mail.gmail.com> <20090506192603.GA56228@wep4035.physik.uni-wuerzburg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexey Shuvaev wrote: > On Wed, May 06, 2009 at 05:01:23AM -0700, Tim Kientzle wrote: >> No, this is simply tar not being very friendly to gunzip. bsdtar is a >> little quick to shutdown when it sees the end of the archive, even though >> gunzip is still decompressing some end-of-archive padding. I'll look at >> this; tar should notice when it's reading from a pipe and read the final >> padding in this case, which would allow gunzip to shut down cleanly. >> > Thanks for looking at it! I did look; bsdtar does do the right thing. (I think I was remembering a bug that got fixed years ago.) I tried but could not reproduce your bug using a recent -CURRENT. I downloaded this file: http://ftp.cse.yzu.edu.tw/pub/FreeBSD/distfiles/openoffice.org2/OOo_OOH680_m18_source.tar.bz2 and extracted ooo_crystal_images-1.tar.gz and got the same MD5 that Eygene reported. $ md5 ooo_crystal_images-1.tar.gz MD5 (ooo_crystal_images-1.tar.gz) = ff0d576d4b0e71c268b1516095a3d085 Where did you download your file from? Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A0265ED.4070407>