-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07. 10. 2011 08:55, Alexander Zangerl wrote:
> On Thu, 06 Oct 2011 13:30:40 +0200, Toma? ?olcx writes:
>> $ duplicity --file-to-restore avian/dev/femtotype/bin/ft 
>> file:///media/Backup/duplicity/orion foo
>> Local and Remote metadata are synchronized, no sync needed.
>> Last full backup date: Fri Aug 19 11:39:05 2011
>> avian/dev/femtotype/bin/ft not found in archive, no files restored.
> 
> i can't confirm that problem, here --file-to-restore works just fine. 
> 
> would you please retry this with the officially approved commandline, ie.
> with restore as the command?

I have also tried this with "duplicity restore ..." and it gives the
same result.

> duplicity restore --file-to-restore .... works in my test environment without
> any hitch. if you can't get it to work i'll need the output of 
> * the last full backup run with -v9 and
> * an ls -la of the file in question
> * the failed restoration attempt also with -v9 in order to do any further
> diagnostics.

It appears I have somehow ended up with a corrupted backup chain. I also
get some assertion failures when trying to restore some other files.

I've written a longer report that includes backtraces and my attempts to
debug them:

https://lists.nongnu.org/archive/html/duplicity-talk/2011-10/msg00007.html

After a new full backup, restore works without any problems. As I can't
reproduce this broken state with a new backup, I can't give you a -v9
output of the backup run that produced this.

If it's a bug in Duplicity, I'm quite certain it's something that
happens at backup, not restore.

Thanks
Tomaž
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFOjzzLsAlAlRhL9q8RAtSMAJ9+YNJ3l4iFBdQmkCZV4W8KVvrkVACeIf7z
u8WJUZFK+gRjUK6REmseRVI=
=tI8c
-----END PGP SIGNATURE-----



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to