[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tar-bug
Subject:    Re: [Bug-tar] leading / included in incremental snapshot rename code
From:       Joerg.Schilling () fokus ! fraunhofer ! de (Joerg Schilling)
Date:       2007-09-29 11:11:24
Message-ID: 46fe32dc.WOofrZ1EewbC9ji6%Joerg.Schilling () fokus ! fraunhofer ! de
[Download RAW message or body]

Nicholas Cole <nick@colecp.com> wrote:

> A leading / is being included in incremental snapshot rename codes
> when a member name has a leading / and tar removes leading / from
> member names when the archive is created
>
> Is this a bug or am I doing something incorrect?
>
> Tested on debian etch with gnu tar versions 1.16 (debian etch) and
> 1.18 (source)
>
> When I extract the full then the incremental archive in the example
> below, tar deletes both /backup/two and /restore/backup/two
>
> If I specify backup as the archive member instead of /backup the
> last extract works as expected by only deleteing backup/two
>
> debian:/# mkdir -p backup/one backup/two
> debian:/# mkdir restore
> debian:/# tar -v -c -f backup.tar --listed-incremental=backup.snapshot /backup
> tar: /backup/one: Directory is new
> tar: /backup/two: Directory is new
> tar: Removing leading `/' from member names
> /backup/
> /backup/one/
> /backup/two/
> debian:/# mv /backup/two /backup/three

The last time I checked, GNU tar was unable to deal with renamed directories 
regardless of whether there is a leading slash or not.

GNU tar does not archive enough file meta data to be able to do it correctly
so even if it works somethimes, this may not work always.

Jörg

-- 
 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de                (uni)  
       schilling@fokus.fraunhofer.de     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily



[prev in list] [next in list] [prev in thread] [next in thread]