Re: [Duplicity-talk] Re: Re: First restore failing

[Peter Schuller]

> Did that: still the same error
> ("duplicity.collections.CollectionsError: No backup chains found").
> Although the verbose output has slightly increased:
>
> webdav path decoding and translation:
> https://server/backup/ -> //server/backup/
> https://server/backup/duplicity-full-signatures.2008-02-27T16%3A54%
> 3A29Z.sigtar.gz -> //server/backup/duplicity-full-signatures.2008-02-
> 27T16:54:29Z.sigtar.gz
> https://server/backup/duplicity-full.2008-02-27T16%3A54%3A29Z.manifest
> -> //server/backup/duplicity-full.2008-02-27T16:54:29Z.manifest
> https://server/backup/duplicity-full.2008-02-27T16%3A54%
> 3A29Z.vol1.difftar.gz -> //server/backup/duplicity-full.2008-02-
> 27T16:54:29Z.vol1.difftar.gz

Hmm. This indicates urlparse does not know about the "https" scheme and 
therefore does not know that the component following "//" is a hostname. This 
is strange given that duplicity uses its own internal urlparse_2_5 module 
which should be consistent regardless of Python version. Observe:

>>> import duplicity.urlparse_2_5 as urlparse
>>> urlparse.urlparse("http://host/path.ext";)
('http', 'host', '/path.ext', '', '', '')
>>> urlparse.urlparse("https://host/path.ext";)
('https', 'host', '/path.ext', '', '', '')
>>> urlparse.urlparse("unknownscheme://host/path.ext")
('unknownscheme', '', '//host/path.ext', '', '', '')

I cannot figure out why https would not be known for you. Anyone else have an 
idea of what's going on here?

Anyways, it can be worked around if nothing else. Probably won't do much 
tonight though - calling it a day early.

-- 
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <address@hidden>'
Key retrieval: Send an E-Mail to address@hidden
E-Mail: address@hidden Web: http://www.scode.org

signature.asc
Description: This is a digitally signed message part.