From owner-freebsd-bugs@freebsd.org Tue May 8 14:04:19 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2D2DFB7121 for ; Tue, 8 May 2018 14:04:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5106473457 for ; Tue, 8 May 2018 14:04:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 11B3BFB711C; Tue, 8 May 2018 14:04:18 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7FA8FB711B for ; Tue, 8 May 2018 14:04:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DCAB73454 for ; Tue, 8 May 2018 14:04:17 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 85C2C255EB for ; Tue, 8 May 2018 14:04:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w48E4GCg099036 for ; Tue, 8 May 2018 14:04:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w48E4GBi099035 for bugs@FreeBSD.org; Tue, 8 May 2018 14:04:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 228069] tar(1) fails to append newer files only (-u, --update), but always appends all files (like -r). Date: Tue, 08 May 2018 14:04:16 +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: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bugzilla.freebsd@omnilan.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org 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 attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2018 14:04:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228069 Bug ID: 228069 Summary: tar(1) fails to append newer files only (-u, --update), but always appends all files (like -r). Product: Base System Version: 11.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: bugzilla.freebsd@omnilan.de Created attachment 193180 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D193180&action= =3Dedit Simple shell test demo which shows tar(1) failing to append only newer files I guess this simple script is the shortest description (identically attache= d as file, respects TEMP environment variable): #!/bin/sh # # Simple test demo which shows tar(1) failing to append only newer # files to an existing archive. # testdir=3Dtobetestarchived testpath=3D${TEMP:-/tmp} testtarfile=3Dtest.tar [ -e "${testpath}"/"${testdir}" ] && rm -R "${testpath}"/"${testdir}" mkdir "${testpath}"/"${testdir}" || { echo "Can't write into ${testpath} (\$testpath), exiting."; exit = 1; } cp /COPYRIGHT "${testpath}"/"${testdir}" || echo "No COPYRIGHT in root foun= d" >\ "${testpath}"/"${testdir}"/COPYRIGHT date > "${testpath}"/"${testdir}"/date.txt echo echo "Prepared two files for testing tar(1)'s --update feature" echo "(in ${testpath}/${testdir})." echo "One is named COPYRIGHT and" echo -n " " stat -f "modification timestamp of COPYRIGHT is %Fm" \ "${testpath}"/"${testdir}"/COPYRIGHT #sha1 "${testpath}"/"${testdir}"/COPYRIGHT tar cPf "${testpath}"/"${testtarfile}" "${testpath}"/"${testdir}" || exit 1 echo echo "Successfully created a test archive, showing the following content:" tar tf "${testpath}"/"${testtarfile}" echo -n " " stat -f "Size of the archive: %z Bytes" "${testpath}"/"${testtarfile}" echo echo "Now we --update the archive, so only files which have a" echo "modification time newer than the files in the archive" echo "should be appended to the archive (none in our case)." # ?halluzination? #echo #echo "Bu surprisingly, COPYRIGHT reports beeing modified," #echo "so the --update feature seems to be broken, but in fact," #echo "something else is broken:" #stat -f "modification timestamp of COPYRIGHT is %Fm" \ # "${testpath}"/"${testdir}"/COPYRIGHT #sha1 "${testpath}"/"${testdir}"/COPYRIGHT tar uPf "${testpath}"/"${testtarfile}" "${testpath}"/"${testdir}" || exit 1 echo "Done." echo "But all files were appended:" tar tf "${testpath}"/"${testtarfile}" echo -n " " stat -f "Size of the archive: %z Bytes" "${testpath}"/"${testtarfile}" echo echo "No idea why the files were appended, since" echo -n " " stat -f "modification timestamp of COPYRIGHT is %Fm" \ "${testpath}"/"${testdir}"/COPYRIGHT echo " (identical)" echo # I was sure I saw the first tar creation run modifing st_mtime, # which would explain the observed misbehaviour, but I cannot reproduce.=20 Either # I had a typo in this very basic script or I'm losing my mind... # # If I knew how to, I'd attach some dtrace/gdb or the like to tar in order = to # watch which functions/syscalls are happening... But I must hope somebody # else takes over. --=20 You are receiving this mail because: You are the assignee for the bug.=