[Bug-tar] Re: Problem with updating an archive (Option -u ) (fwd)

[Ingo Lantschner]

Seems as if we have found a bug. I could already reproduce the workaround 
from John. Pls. see below.

Ingo.


---------- Forwarded message ----------
Date: Wed, 31 Dec 2003 12:02:08 +0000
From: John Haxby <address@hidden>
Reply-To: address@hidden
To: address@hidden
Subject: Re: Problem with updating an archive (Option -u )

Ingo Lantschner wrote:

>On Wed, 31 Dec 2003, Cameron Simpson wrote:
>
>  
>
>>RTFM. The info file for tar says:
>>
>>    `--update' `-u' Adds files to the end of the archive, but only if they
>>    are newer than their counterparts already in the archive, or if they do
>>    not already exist in the archive. see "update".
>>    
>>
>
>Believe me, I read this manual several times and I fully understand the 
>above. I even reproduced exactly this behavior of tar. (See my second 
>example in my original mail).
>
>BUT "tar -uvf home.tar ~" adds each time ALL files in ~ to home.tar - NOT
>only the ones which have changed or which are new. So in fact the size of
>home.tar is doubled with the second time I call "tar -u home.tar ~", even
>if just 1% of the files in ~ have changed.
>  
>

I think it's a bug, but it's a function of the leading "/" on the path 
name.   I have a little direcory in /tmp and if I do this:

    $ cd /
    $ tar vuf /tmp/test1.tar tmp/test
    <files added>
    $ tar vuf /tmp/test1.tar tmp/test
    <nothing added>

but

    $ tar vuf /tmp/test2.tar /tmp/test
    tar: Removing leading `/' from member names
    <files added>
    $ tar vuf /tmp/test2.tar /tmp/test
    tar: Removing leading `/' from member names
    <files added again>

If I add the "P" flag it's just fine (assuming you want the leading "/" 
on the path name)   I haven't tried it to see if you get the same 
problem with incremental (-G or -g) operations.

jch

jch
   


-- 
Shrike-list mailing list
address@hidden
https://www.redhat.com/mailman/listinfo/shrike-list