Bug 510714 - tar does not interpret --no-wildcards option right
Summary: tar does not interpret --no-wildcards option right
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: tar
Version: 5.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Ondrej Vasik
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks: 456141 578522
TreeView+ depends on / blocked
 
Reported: 2009-07-10 12:29 UTC by Daniel Novotny
Modified: 2010-03-31 14:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 578522 (view as bug list)
Environment:
Last Closed: 2010-03-30 08:19:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2010:0224 0 normal SHIPPED_LIVE tar bug fix and enhancement update 2010-03-29 12:34:02 UTC

Description Daniel Novotny 2009-07-10 12:29:16 UTC
Description of problem:
tar interpret wildcards in the files it has to extract, even if the --no-wildcards option is used

Version-Release number of selected component (if applicable):
1.15.1

How reproducible:
always


Steps to Reproduce:
1. touch with_wildcards\[abc\]
2. tar -cf wild.tar with_wildcards\[abc\]
3. tar --no-wildcards -xf wild.tar with_wildcards[abc]
  
Actual results:
tar: with_wildcards[abc]: Not found in archive
tar: Error exit delayed from previous errors

Expected results:
extract the file

Additional info:
the error is not present in newer versions of tar, i.e. in current Fedora this works

Comment 9 errata-xmlrpc 2010-03-30 08:19:09 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0224.html


Note You need to log in before you can comment on or make changes to this bug.