From owner-freebsd-stable@freebsd.org  Wed Jul  6 01:33:00 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 217B6B20248
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed,  6 Jul 2016 01:33:00 +0000 (UTC)
 (envelope-from janm@transactionware.com)
Received: from mail3.transactionware.com (mail.transactionware.com
 [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id A6DCE11DB
 for <freebsd-stable@freebsd.org>; Wed,  6 Jul 2016 01:32:58 +0000 (UTC)
 (envelope-from janm@transactionware.com)
Received: (qmail 36833 invoked by uid 907); 6 Jul 2016 01:26:15 -0000
Received: from Unknown (HELO jmmacpro.tmst.com.au) (203.14.245.130)
 (smtp-auth username janm, mechanism plain)
 by mail3.transactionware.com (qpsmtpd/0.84) with (ECDHE-RSA-AES256-SHA
 encrypted) ESMTPSA; Wed, 06 Jul 2016 11:26:15 +1000
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Is tar Broken In 10.3-STABLE?
From: Jan Mikkelsen <janm@transactionware.com>
In-Reply-To: <36b73290-0714-d5e5-6740-3318ff1055ec@tundraware.com>
Date: Wed, 6 Jul 2016 11:26:59 +1000
Cc: FreeBSD Stable Maling List <freebsd-stable@freebsd.org>
Message-Id: <97B23D8F-B8A3-4460-8AF7-D7393055DA96@transactionware.com>
References: <36b73290-0714-d5e5-6740-3318ff1055ec@tundraware.com>
To: Tim Daneliuk <tundra@tundraware.com>
X-Mailer: Apple Mail (2.3124)
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.22
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2016 01:33:00 -0000

Hi,

Tar should complain and die if an input path doesn=E2=80=99t exist. So, =
no, the behaviour you=E2=80=99re seeing isn=E2=80=99t broken. See also:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205358 =
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205358>

This bug has been fixed upstream seems to have been imported into =
stable/10 in r302075. =46rom the commit message:
- tar and cpio should fail if an input file named on the command line is
  missing (vendor issue 708)
I agree the message could be a bit clearer about what=E2=80=99s going =
on!

Regards,

Jan.


> On 6 Jul 2016, at 02:39, Tim Daneliuk <tundra@tundraware.com> wrote:
>=20
> I just upgraded to r302342 today to verify a problem I saw=20
> after a 10.3-STABLE upgrade yesterday.  Upgrade was=20
> accomplished via makeworld/kernel & installworld/kernel.
>=20
>=20
> When using tar with the -T argument to provide a list=20
> of backup sources, it blows out with the following=20
> error if a source in the file list is missing:
>=20
>   tar: INTERNAL ERROR: Function 'archive_read_disk_open' invoked with =
archive structure in state 'header', should be in state 'new/closed': =
Unknown error: -1
>=20
> In the past, tar would make some noise if it was asked
> to copy a nonexistent file or directory, but it would=20
> continue the remainder of the archive operation.
>=20
> Thoughts?
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to =
"freebsd-stable-unsubscribe@freebsd.org"