Date: Thu, 12 Oct 1995 14:18:35 -0700 From: asami@cs.berkeley.edu (Satoshi Asami) To: FreeBSD-gnats-submit@freebsd.org Cc: mark@grondar.za Subject: bin/778: tar complains "EOF not on block boundary" Message-ID: <199510122118.OAA01432@silvia.HIP.Berkeley.EDU> Resent-Message-ID: <199510122120.OAA29299@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 778 >Category: bin >Synopsis: tar complains "EOF not on block boundary" on a good tarfile.gz >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 12 14:20:01 PDT 1995 >Last-Modified: >Originator: Satoshi Asami >Organization: The FreeBSD Ports Team >Release: FreeBSD 2.2-CURRENT i386 >Environment: This happens on a very recent -current only, not on -stable. >Description: tar says "EOF not on block boundary" when it is given a perfectly fine (I think) tarfile.gz. It happens on Mark Murray (mark@grondar.za)'s machine too. >How-To-Repeat: tar tvzf /usr/ports/distfiles/dvips558.tar.gz The funny thing is, it doesn't complain if you gunzip the file first and "tar tvf" it. It does print out the entire table of contents in either case. This is the only tarfile I found (so far) to have this problem. (I tried the whole /usr/ports/distfile directory on my machine... it has about 180MB worth of distfiles.) >Fix: No idea. MALLOC_OPTIONS=Z didn't help, by the way. :) >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510122118.OAA01432>