From charnier@lirmm.fr  Sat May 27 01:12:44 1995
Received: from pcdif01.lirmm.fr ([193.49.106.70])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA14163
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 27 May 1995 01:12:42 -0700
Received: (root@localhost) by pcdif01.lirmm.fr (8.6.11/8.6.9) id KAA10281; Sat, 27 May 1995 10:10:02 +0200
Message-Id: <199505270810.KAA10281@pcdif01.lirmm.fr>
Date: Sat, 27 May 1995 10:10:02 +0200
From: Philippe CHARNIER <charnier@lirmm.fr>
Reply-To: charnier@lirmm.fr
To: FreeBSD-gnats-submit@freebsd.org
Subject: tar --exclude -c doesn't work
X-Send-Pr-Version: 3.2

>Number:         450
>Category:       gnu
>Synopsis:       tar --exclude -c doesn't work
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    n_hibma
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 27 01:20:02 1995
>Closed-Date:    Mon Jul 19 01:42:12 PDT 1999
>Last-Modified:  Mon Jul 23 01:12:29 PDT 2001
>Originator:     Philippe CHARNIER
>Release:        FreeBSD 2.0.950412-SNAP i386
>Organization:
>Environment:

	Also in my current machine

>Description:

	tar can't use --exclude feature when creating archives

>How-To-Repeat:

	$ tar --exclude a -cvf t a b
	a
	b
	$ tar --exclude a -tvf t
	b

>Fix:
	
	

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: scrappy 
State-Changed-When: Sun May 26 15:51:24 PDT 1996 
State-Changed-Why:  
problem still exists in 1.11.8 (newest version)...will look into it 


Responsible-Changed-From-To: freebsd-bugs->scrappy 
Responsible-Changed-By: scrappy 
Responsible-Changed-When: Sun May 26 15:51:24 PDT 1996 
Responsible-Changed-Why:  
cause I'll look into it? 
Responsible-Changed-From-To: scrappy->freebsd-bugs 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Wed Mar 24 08:17:48 PST 1999 
Responsible-Changed-Why:  
scrappy obviously isn't looking at it. 

From: Sheldon Hearn <sheldonh@iafrica.com>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: gnu/450: tar --exclude -c doesn't work
Date: Wed, 24 Mar 1999 19:40:31 +0200

 Just tested this with tar-1.12 and the misfeature exists in that version
 too. Also got a report from someone using tar-1.12 on Irix 6.5; the
 problem exists there too.
 
 Ciao,
 Sheldon.
 
Responsible-Changed-From-To: freebsd-bugs->n_hibma 
Responsible-Changed-By: n_hibma 
Responsible-Changed-When: Fri Jul 16 11:01:01 PDT 1999 
Responsible-Changed-Why:  
I've sent off a bug report to the maintainers of tar. let's see what they 
say of this change in functionality. 

From: Nick Hibma <n_hibma@webweaving.org>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: gnu/450: tar --exclude -c doesn't work
Date: Sat, 17 Jul 1999 20:26:49 +0200 (CEST)

 The reply from GNU bug-traq.
 
 ---------- Forwarded message ----------
 Date: Fri, 16 Jul 1999 19:33:05 -0700 (PDT)
 From: Paul Eggert <eggert@twinsun.com>
 To: nick.hibma@jrc.it
 Cc: bug-gnu-utils@gnu.org, bug-tar@gnu.org
 Subject: Re: tar: exclusion does not work on listed files
 
    Date: Fri, 16 Jul 1999 19:59:54 +0200 (MET DST)
    From: Nick Hibma <nick.hibma@jrc.it>
 
 	   tar --exclude a -cf /dev/null a b 
 
    will include the file a. This is inconvenient if the command line is
    specified like this:
 
 	   tar --exclude a -cf /dev/null ?
 
    For your reference the problem
    report in the FreeBSD bug database:
 
 	   http://www.freebsd.org/cgi/query-pr.cgi?pr=450
 
 That's the way that GNU tar is documented, but I agree that the
 behavior is inconvenient and irregular, so I've written up some code
 that behaves the way that you expect.  (Your proposed patch wasn't
 enough, as it didn't affect extraction or appending, and it didn't
 update the documentation.)  Please try:
 
 ftp://alpha.gnu.org/gnu/tar/tar-1.13.3.tar.gz
 
 and see whether it does the trick.
 
 
State-Changed-From-To: analyzed->closed 
State-Changed-By: n_hibma 
State-Changed-When: Mon Jul 19 01:42:12 PDT 1999 
State-Changed-Why:  
This has been solved in tar 1.13.3 (alpha) see the URl in the last message of 
this PR. 
Or actually, the default behaviour of tar has been changed. 
>Unformatted:


