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

[Scott Hannahs]

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