Re: [Duplicity-talk] Error "Bad tarinfo name ././@LongLink"

[Rob Browning]

Ben Escoto <address@hidden> writes:

> The above output is what tar should say.  All of the files should
> either start with "snapshot/" or "signature/".  If one of them says
> "././@LongLink" or something then we know the problem is with the
> signatures.

Since none of the files in my duplicity backup dir mention LongLink,
I'm wondering if perhaps the python tarfile handling isn't doing the
right thing...

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4