Hide Forgot
Description of problem: Using tar --verify (or -W) to verify an archive after creating it fails. Version-Release number of selected component (if applicable): GNU tar 1.25 How reproducible: Always, regardless of -p, etc. Steps to Reproduce: 1. echo 'asdf' > temp 2. tar -cpvWf temp.tar temp 3. check exit status and output Actual results: temp Verify temp temp: Mode differs temp: Uid differs temp: Gid differs temp: Mod time differs return code: 1 Expected results: Should verify w/out problems. Additional info: Apparently this was introduced in 1.24 and has been fixed upstream in 1.26. See http://lists.gnu.org/archive/html/bug-tar/2010-11/msg00065.html http://savannah.gnu.org/forum/forum.php?forum_id=6746 Would it be possible to switch to 1.26 or backport the fix to the current one?
Thanks for report and upstream info links. Both possibilities... 1.26 is bugfix only release and it fixes more than just this one bug. In addition, 1.26 is in Rawhide for more than 4 months. On other hand - backport is small, just 2 lines (or ~20 if both related patches are taken). I'll do an update next week (I'm on vacation now).
Sounds good, thanks. Enjoy the rest of your vacation!
tar-1.26-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/tar-1.26-1.fc15
Package tar-1.26-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing tar-1.26-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/tar-1.26-1.fc15 then log in and leave karma (feedback).
tar-1.26-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
Sorry I couldn't leave karma on the update before it was pushed to stable. Looks like it works just fine now, thanks!