From owner-freebsd-stable@FreeBSD.ORG Thu Dec 8 17:29:53 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D127316A41F for ; Thu, 8 Dec 2005 17:29:53 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D5C043D81 for ; Thu, 8 Dec 2005 17:29:48 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002102568.msg for ; Thu, 08 Dec 2005 17:29:11 +0000 Message-ID: <00c701c5fc1c$e6db4220$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: Date: Thu, 8 Dec 2005 17:29:06 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Processed: multiplay.co.uk, Thu, 08 Dec 2005 17:29:11 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: multiplay.co.uk, Thu, 08 Dec 2005 17:29:13 +0000 Subject: bsdtar / libarchive bug? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 17:29:53 -0000 It seems bsdtar can create files it cant read. i.e. it will happily create empty tar.gz files but when it comes to read them the following error is output: tar: Unrecognized archive format: Inappropriate file type or format Having a look at libarchive shows the following code: /* An empty archive is a serious error. */ if (bytes_read == 0) { archive_set_error(a, ARCHIVE_ERRNO_FILE_FORMAT, "Empty input file"); return (ARCHIVE_FATAL); } Which is where I expect the issue is, why would an empty archive be fatal? I can see any reason for this, yes its strange but there's nothing fatal about it imo. Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk.