[Bug 205358] bsdtar(1) does not return an error status when an input path is not in the filesystem

[bugzilla-noreply at freebsd.org]

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 at FreeBSD.org
          Reporter: janm at transactionware.com
                CC: kientzle at 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.