Addendum: if you compile duplicity-0.4.2 from source using python2.4,
detecing present backup sets fails, because of this (I think):
Reading results of 'echo -e 'cd /users/benecke/KLAVIER
ls -1' | sftp -b - [EMAIL PROTECTED]'
Full log:
[EMAIL PROTECTED]:~$ duplicity --no-encryption --verbosity 9 --verify
ssh://[EMAIL PROTECTED]//users/benecke/KLAVIER /
Reading globbing filelist /home/jens/.ftplicity/exclude
Main action: verify
Reading results of 'echo -e 'cd /users/benecke/KLAVIER
ls -1' | sftp -b - [EMAIL PROTECTED]'
Invalid command.
Ignoring file 'bin'
(... several other files ...)
Collection Status
-----------------
Connecting with backend: scpBackend
Archive dir: None
No backup chains with active signatures found
Found 0 backup chains without signatures.
No orphaned or incomplete backup sets found.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 373, in ?
if __name__ == "__main__": main()
File "/usr/bin/duplicity", line 355, in main
elif action == "verify": verify(col_stats)
File "/usr/bin/duplicity", line 262, in verify
collated = diffdir.collate2iters(restore_get_patched_rop_iter(col_stats),
File "/usr/bin/duplicity", line 201, in restore_get_patched_rop_iter
backup_chain = col_stats.get_backup_chain_at_time(time)
File "/usr/lib/python2.4/site-packages/duplicity/collections.py", line 598,
in get_backup_chain_at_time
raise CollectionsError("No backup chains found")
duplicity.collections.CollectionsError: No backup chains found
Command exited with non-zero status 1
I am using SSH connections with the key stored in a key-agent (so
passwordless connection is possible).
Duplicity 0.4.2 works fine on Debian Sarge, using python2.3.
Thanks,
Jens
--
incremental backup does not work
https://bugs.launchpad.net/bugs/88617
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
