Bug 782628

Summary: tar (1.23) does not remove files when -r flag used (append to tar file)
Product: Red Hat Enterprise Linux 6 Reporter: ashish <anair>
Component: tarAssignee: Pavel Raiskup <praiskup>
Status: CLOSED ERRATA QA Contact: Branislav Blaškovič <bblaskov>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: azelinka, bblaskov, kdudka
Target Milestone: rcKeywords: EasyFix
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: tar-1.23-4.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 13:49:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description ashish 2012-01-18 00:07:27 UTC
Description of problem:
tar (1.23) does not remove files when -r flag used (append to tar file)

Version-Release number of selected component (if applicable):
tar version 1.23 , shipped with RHEl6.1 and RHEL6.2

How reproducible:


Steps to Reproduce:
touch remove_me.txt
tar --remove-files -rvf appendtome.tar remove_me.txt
remove_me.txt

#####the file should be gone now - but is not and  can be seen by the ls command. 
ls r*
remove_me.txt

tar -tf  appendtome.tar
remove_me.txt
##ok when you are creating a tar file tho'
tar --remove-files -cvf appendtome.tar remove_me.txt
remove_me.txt
ls r*
ls: cannot access r*: No such file or directory

  
Actual results:
On issuing below command :
tar --remove-files -rvf appendtome.tar remove_me.txt

The file remove_me.txt is not removed from the current pwd after adding in tar ball.

Expected results:
tar --remove-files -rvf appendtome.tar remove_me.txt

The file remove_me.txt should be  removed from the current pwd after adding in tar ball.

Additional info:

Comment 2 Kamil Dudka 2012-01-18 00:54:07 UTC
upstream commit:

http://git.savannah.gnu.org/cgit/tar.git/commit/?id=45a5741

Comment 9 errata-xmlrpc 2012-06-20 13:49:35 UTC
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.

http://rhn.redhat.com/errata/RHBA-2012-0849.html