Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Previously, when the "--verify" or "-W" option was used, the tar utility always exited with a status of 2, and false warning messages per each archived file were printed. This behavior was a regression introduced in tar-1.23-11.el6. With this update, tar exits with a status of 2 only if there is a real problem with the archived files
Description of problem:
Upgrading from tar-1.23-7.el6.x86_64 to tar-1.23-11.el6.x86_64 introduced a problem with the -W verify switch. Problem seems to have started with tar-1.23-9.el6.x86_64
Version-Release number of selected component (if applicable):
tar-1.23-7.el6.x86_64
How reproducible:
every time
Steps to Reproduce:
1. tar -cvWf mytarfile.tar *
Actual results:
file.txt: Mode differs
file.txt: Gid differs
file.txt: Mod time differs
Expected results:
Verify */file.txt
Additional info:
This is my first bug report. Hopefully I am providing enough information.
We tried to downgrade to tar-1.23-9.el6.x86_64 but the problem did not go away. When we downgraded to tar-1.23-7.el6.x86_64 it went back to normal behavior.
Inspecting the tar file, the contents look correct.
Hi Will, thanks for the report. This is really caused by the RH-tar commit
a309347d41ac4 (longnames patch). Upstream fixed this later by:
http://git.savannah.gnu.org/cgit/tar.git/commit/?id=24214ca5d506f56
There are some other patches fixing/enhancing -W option which should be
observed in upstream but this should fix the major issue.
Note that this bug tracking system is not a mechanism for requesting support,
and we are not able to guarantee the timeliness or suitability of a
resolution.
If this issue is critical or in any way time sensitive, please raise a ticket
through your regular Red Hat support channels to make certain it receives the
proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please
visit:
https://www.redhat.com/support/process/production/#howto
Pavel
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://rhn.redhat.com/errata/RHBA-2015-1285.html