Bug 6665 – tar fails to properly parse exclude patterns...

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 6665 - tar fails to properly parse exclude patterns...

Summary:	tar fails to properly parse exclude patterns...

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	tar (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-11-02 17:28 EST by bmacy
Modified:	2008-05-01 11:37 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-01-18 06:14:33 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description bmacy 1999-11-02 17:28:06 EST

Assuming a /usr/local/src tree exists try:
tar -cvpf fred.tar --exclude='*/src/*' /usr/local

It still archives /usr/local/src. Same occurs if you use
'-X' flag and refer to a file with the pattern in it.

Excluding /usr/local/src/* does work. This is a change from
RedHat versions 5.0, 5.1, 5.2, and 6.0 and appears to be a
bug.

Comment 1 Preston Brown 2000-01-13 22:43:59 EST

bero, I can verify this, even with tar-1.13.17-1.  Shall we downgrade?

Comment 2 Bernhard Rosenkraenzer 2000-01-18 06:14:59 EST

I've passed the bug on to bugs-tar@gnu.org - hope they get it fixed for 1.13.18
in time. I don't really want to downgrade because that would get back some bugs
that were fixed in between.

Comment 3 Bernhard Rosenkraenzer 2000-07-17 11:34:03 EDT

The tar maintainers claim it's not a bug, but a feature (better POSIX
compliance).

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