Description of Problem: TAR creates empty archive when both an exclude pattern file and an absolute path to tar is given. Version-Release number of selected component (if applicable): 1.13.25-4.7.1 How Reproducible: Always Steps to Reproduce: 1. mkdir tarbug;cd tarbug; echo "*.o#" | tr '#' '\n' > exclude;touch foo 2. tar cvZ -X exclude -N "20021103 04:25:36" -f tarbug.tgz `pwd`/foo 3. Actual Results: Empty tar file is created. Expected Results: Tar file containing 'foo' Additional Information: tar-1.13.19-6 does work. Take this as a SERIOUS issue: many backup system rely on explude pattern file + backing up absolute paths. Having empty backup is quite nasty. My backup system just broke on this ! I'm not sure if the -N flag does matter. Didnt checked.
*** Bug 77683 has been marked as a duplicate of this bug. ***