Red Hat Bugzilla – Bug 1319820
Tar does not honor --directory option for --remove-files
Last modified: 2017-08-01 13:01:03 EDT
Description of problem: Tar does not honor --directory option for --remove-files, it tries to remove files in the current working directory instead. Version-Release number of selected component (if applicable): tar-1.26-29.el7.x86_64 How reproducible: always Steps to Reproduce: 1. cd $HOME 2. rm -f tartest.tar 3. mkdir -p indirectdir/test 4. touch indirectdir/test/afile 5. tar --remove-files --append --atime-preserve --directory $HOME/indirectdir --mode 444 --file $HOME/tartest.tar test/afile 6. ls indirectdir/test/afile Actual results: ls indirectdir/test/afile shows the file still exists Expected results: ls: indirectdir/test/afile: No such file or directory Additional info: tar-1.15.1-32.el5_8 in RHEL 5 and tar-1.23-14.el6.x86_64 in RHEL 6 work as expected strace in RHEL 6 (similar in RHEL 5) shows: getcwd("/home/user/indirectdir", 4096) = 26 write(3, "test/afile\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 10240) = 10240 clock_gettime(CLOCK_REALTIME, {1458573540, 334576437}) = 0 clock_gettime(CLOCK_REALTIME, {1458573540, 334595612}) = 0 close(3) = 0 unlink("/home/user/indirectdir/test/afile") = 0 close(1) = 0 close(2) = 0 exit_group(0) = ? +++ exited with 0 +++ strace in RHEL 7: getcwd("/home/user", 4096) = 14 write(3, "test/afile\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 10240) = 10240 close(3) = 0 unlinkat(4, "/home/user/test/afile", 0) = -1 ENOENT (No such file or directory) close(1) = 0 close(2) = 0 exit_group(0) = ? +++ exited with 0 +++
The major fix for this is: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=e3d28d84 But there needs to be done better inspection as this feature (-C together with --remove-files was fixed many times in post v1.26 time).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2012