duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] What happened to "file:" protocol?


From: Scott Hannahs
Subject: Re: [Duplicity-talk] What happened to "file:" protocol?
Date: Sun, 30 Aug 2009 22:07:23 -0400

Incredibly foolish....

it needed
PYTHONPATH=/sw/lib/python2.5/site-packages

not
PYTHONPATH=/sw/lib/python2.5/

as an environmental variable. Go figure, it is just my python inexperience. Thanks for the advice, it was good to know that this wasn't a general problem but just my installation issues.

-Scott


On Aug 30, 2009, at 1:43 PM, address@hidden wrote:

Maybe something went wrong on installation? You could try to manually delete duplicity from your filesystem and reinstall with
python setup.py install

I guess there is an old duplicity 0.6.0 hanging around in the default location for the python libs. A very wild guess, but might be worth a try.

....ede


On 28.08.2009 17:42, Scott Hannahs wrote:

On Aug 28, 2009, at 09:50, Gabriel Ambuehl wrote:

Scott Hannahs wrote:

My test command is
/sw/bin/duplicity full --encrypt-key XXXXXXXX --sign-key XXXXXXXX $HOME/Documents/ file:///tmp/Documents/
and I get a response

"UnsupportedBackendScheme: scheme not supported in url: file:///tmp/Documents "/

When did file: become unsupported? Or am I doing something incredibly foolish?

I think you can do without the file:///  to use local storage

No, tried that already.  Doesn't like none URL versions.

% /sw/bin/duplicity full --encrypt-key XXXXXXXX --sign-key XXXXXXXX $HOME/Documents/ /tmp/Documents/ Command line error: One of the arguments must be an URL. Examples of URL strings are
"scp://address@hidden:1234/path" and "file:///usr/local".  See the man
page for more information.
Enter 'duplicity --help' for help screen.
%

Note also that this claims version 6.00 but it was installed from the 6.04 source tarball. This is all on Mac OS X if that makes a difference.
% /sw/bin/duplicity --version
duplicity 0.6.00
%

On Aug 28, 2009, at 10:03, Kenneth Loafman wrote:

It's file: not file::.  That's the problem.


That is just my typo in the text comment. The actual command list was a true cut and paste into the mail message. The command line has a single colon ":", here is the exact screen text (keys redacted).

% /sw/bin/duplicity full --encrypt-key XXXXXXXX --sign-key XXXXXXXX $HOME/Documents/ file:///tmp/Documents/
UnsupportedBackendScheme: scheme not supported in url: file:///tmp/Documents/
%

This is a problem with the install on Mac OS X that happened in moving from 0.5X to 0.6.X ?? I now tried a backup to a remote system and got the same error % /sw/bin/duplicity full --encrypt-key XXXXXXXX --sign-key XXXXXXXX $HOME/Sites scp://my.remote.host/testbackup
UnsupportedBackendScheme: scheme not supported in url: scp://sthmac/testbackup

My installation command completes without errors. The variable PYTHONPATH=/sw/lib/python2.5, and the actual directory, "/sw/lib/ python2.5/site-packages/duplicity" seems to have all the python code in it.

Here is the duplicity build command:
sudo python setup.py install --prefix=/sw --librsync-dir=/sw


-Scott



_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk



_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk





reply via email to

[Prev in Thread] Current Thread [Next in Thread]