From owner-freebsd-bugs@freebsd.org  Wed Dec 16 20:38:38 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 A79B4A491C2
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 16 Dec 2015 20:38:38 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9868710C8
 for <freebsd-bugs@FreeBSD.org>; Wed, 16 Dec 2015 20:38:38 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBGKccP3066320
 for <freebsd-bugs@FreeBSD.org>; Wed, 16 Dec 2015 20:38:38 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 205358] bsdtar(1) does not return an error status when an input
 path is not in the filesystem
Date: Wed, 16 Dec 2015 20:38:38 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: janm@transactionware.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter cc
Message-ID: <bug-205358-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Dec 2015 20:38:38 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205358

            Bug ID: 205358
           Summary: bsdtar(1) does not return an error status when an
                    input path is not in the filesystem
           Product: Base System
           Version: 10.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: janm@transactionware.com
                CC: kientzle@FreeBSD.org

bsdtar(1) emits a warning but does not return an error status when one of the
input files cannot be found. This is a regression vs. the bsdtar in 8.x.

To test:

    tar cf /tmp/file.tar nonexistent-file-name && echo Return value broken

Returning an error is important for unattended scripts that depend on the
return value to get failure conditions -- This was discovered after a file was
missing from an automated build where the build process completed with a
warning only.

The libarchive based cpio(1) does the return an error code in this case.

The difference seems to be that cpio returns and error status for the internal
errors ARCHIVE_FAILED and ARCHIVE_FATAL, while tar only returns errors for
ARCHIVE_FATAL.

-- 
You are receiving this mail because:
You are the assignee for the bug.