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

[Ben Escoto]

>>>>> "RB" == Rob Browning <address@hidden>
>>>>> wrote the following on Sun, 09 Mar 2003 13:27:05 -0600

  RB> Sure.  It happens every time I run duplicity on the machine for
  RB> an incremental backup.  I've even tried deleting the full backup
  RB> and starting over.

  RB> If I wanted to go about debugging this, do you have any
  RB> suggestions for the best way to start?  By default I was going
  RB> to just start with some annotations to the code around the
  RB> failure point.

The problem seems to be that duplicity is making a bad signature file.
If this is true, and it happens whenever you make an incremental
backup, then the problem must be in the initial signatures.  You can
confirm this by getting the sig file from the backup repository,
decrypting it with gpg "manually" and then listing its contents with
tar.  For instance:

$ gpg --output - 
duplicity-full-signatures.1970-01-01T19\:46\:40-07\:00.sigtar.gpg | tar -tf -
gpg: CAST5 encrypted data
snapshot/         
signature/changeable_permission
signature/deleted_file
snapshot/directory_to_file
signature/directory_to_file/file
snapshot/directory_to_file/subdir
signature/directory_to_file/subdir/file
signature/executable
signature/executable2
snapshot/fifo
signature/file_to_directory
signature/largefile
signature/regular_file
signature/regular_file.sig
snapshot/symbolic_link
signature/test
signature/two_hardlinked_files1
signature/two_hardlinked_files2

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.

    Another strategy would be to try to narrow the error down so it
can be reproduced in just a few files.  Then you could send me the
files and the command, and get me to fix it.


-- 
Ben Escoto

pgpj8cpOoy03t.pgp
Description: PGP signature