Public bug reported:
Hi,
this is a regression in tar 1.28-2.1 -> 1.29-1 and by that it is valid for
Xenial -> Yakkety, but as well for Debian Stretch.
Fortunately there is at least a simple test:
rm -rf dir; mkdir -p dir/subdir; touch dir/subdir/file; tar -c -f /tmp/test.tar
-C dir subdir --exclude subdir/file; tar -tf /tmp/test.tar subdir/file
Correct:
tar: subdir/file: Not found in archive
tar: Exiting with failure status due to previous errors
Wrong:
subdir/file
This could cause quite a few weird/under-the-radar bugs all around -
like in my package which suddenly had more binaries. "Fortunately" one
of them collided with one of the system, so we found this issue.
I'll report to Debian as well and link the bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: tar 1.29-1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
Date: Fri Jun 3 09:46:54 2016
InstallationDate: Installed on 2016-06-01 (1 days ago)
InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Alpha amd64 (20160601)
SourcePackage: tar
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: tar (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug yakkety
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1588690
Title:
Tar fails to --exclude files
Status in tar package in Ubuntu:
New
Bug description:
Hi,
this is a regression in tar 1.28-2.1 -> 1.29-1 and by that it is valid for
Xenial -> Yakkety, but as well for Debian Stretch.
Fortunately there is at least a simple test:
rm -rf dir; mkdir -p dir/subdir; touch dir/subdir/file; tar -c -f
/tmp/test.tar -C dir subdir --exclude subdir/file; tar -tf /tmp/test.tar
subdir/file
Correct:
tar: subdir/file: Not found in archive
tar: Exiting with failure status due to previous errors
Wrong:
subdir/file
This could cause quite a few weird/under-the-radar bugs all around -
like in my package which suddenly had more binaries. "Fortunately" one
of them collided with one of the system, so we found this issue.
I'll report to Debian as well and link the bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: tar 1.29-1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
Date: Fri Jun 3 09:46:54 2016
InstallationDate: Installed on 2016-06-01 (1 days ago)
InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Alpha amd64 (20160601)
SourcePackage: tar
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1588690/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
