[Duplicity-tracker] [bug #21753] cleanup w/ --archive-dir fails when out of synch

[Peter Schuller]

URL:
  <http://savannah.nongnu.org/bugs/?21753>

                 Summary: cleanup w/ --archive-dir fails when out of synch
                 Project: duplicity
            Submitted by: scode
            Submitted on: Saturday 12/08/2007 at 09:11
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

There is some kind of interaction between cleanup and --archive-dir.

I have a remote directory that would clean up without --archive-dir, but
won't clean up with --archive-dir. With --archive-dir set, I get:

sftp command: 'mkdir scripts'
sftp command: 'cd scripts'
sftp command: 'ls -1'
Warning, found the following orphaned signature files:
duplicity-new-signatures.2007-08-22T22:01:53+02:00.to.2007-11-25T13:30:01+02:00.sigtar.gz
Last full backup date: Sat Dec  8 09:41:33 2007
Deleting this file from backend:
duplicity-new-signatures.2007-08-22T22:01:53+02:00.to.2007-11-25T13:30:01+02:00.sigtar.gz
Running 'sftp  CENSORED' (attempt #1)
sftp command: 'cd scripts'
sftp command: 'rm
duplicity-new-signatures.2007-08-22T22:01:53+02:00.to.2007-11-25T13:30:01+02:00.sigtar.gz'
Remote file or directory 'scripts' does not exist
Running 'sftp  CENSORED' failed (attempt #1)
^C

I have not yet tracked down the details, but I believe the problem is that
the 'rm' fails since the remote and is out-of-synch with the archive dir, and
the failure is incorrectly reported as if it was the 'cd' operation that
failed.

Note however that the remote end being out of synch with the archive dir is
an expected condition. Even if I had not manually ran a cleanup without
--archive-dir, the two can easily be left out of synch as a result of
interruptions.

I have not yet evaluated if the fix is simple, but filing the bug for now at
least. Perhaps the easiest fix is to just allow deletions to fail silently
(perhaps with a warning suggesting that it should not happen repeatedly), in
case treating the archivedir as a separate entity needs redesigns.





    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?21753>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/