RE: [Duplicity-talk] duplicity 0.5.14 - No signatures found - really strange...

[François FOURRIER]

Hello,

Thanks for you answer, I dit it again using the double // with the same
result... 

The log is invasive you'll find it here :

http://www.fourrier.com/duplicity.log

Thanks for your help !

François FOURRIER
-----------------
Sites Web - E-commerce
Outils de veille tarifaire pour les professionnels du e-commerce.
http://www.fourrier.com

-----Message d'origine-----
De : address@hidden
[mailto:address@hidden De la part
de Kenneth Loafman
Envoyé : mardi 7 avril 2009 22:16
À : Discussion of the backup program duplicity
Objet : Re: [Duplicity-talk] duplicity 0.5.14 - No signatures found - really
strange...

François FOURRIER wrote:
> What Am I doing wrong there ??? I'm getting nuts...

I don't see anything wrong.

Is sda2/test really what you meant, or do you mean /sda2/test?  Given the
sda2 device name, I'm guessing you mean /sda2/test, in which case the target
should be ftp://address@hidden//sda2/test (note double slash).

If that's not it, then run with -v9 on the command line and post the log
(zipped) for a list-current-files run.  Try to munge as little as possible,
especially do not munge format.  Include the command line in the log.

> Also why do I get get traceback errors when I just type duplicity 
> --version

This one's an "error" I introduced (again!).  Ignore it.  It's not really an
error, it's a Catch-22, big time.  You have to use sys.exit() if you want to
get job status out to the system, but Python insists on treating it as an
exception, so you have to trap it.  I forgot about it when I modified the
exception list and changed the order.

...Ken