[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Duplicity-talk] Re: Re: Re: Re: First restore failing
From: |
Thorsten Kampe |
Subject: |
[Duplicity-talk] Re: Re: Re: Re: First restore failing |
Date: |
Mon, 10 Mar 2008 11:50:39 -0000 |
User-agent: |
MicroPlanet-Gravity/2.70.2067 |
* Peter Schuller (Sun, 9 Mar 2008 15:14:18 +0100)
> And this is confirmed to work over here and for you, based on your previous
> input. Yet for some strange reasons this seems to fail when duplicity runs.
> The output for you after applying the original version of my patch was:
>
> 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
>
> The fact that "https://server/backup/" translates into "//server/backup/"
> being interpreted as the path, seems consistent with https being unknown by
> the urlparse module. I really don't see how the problem can be in the
> backend. With the latest version of the patch:
>
> raw_filename = self._getText(href.childNodes).strip()
> parsed_url = urlparser.urlparse(urllib.unquote(raw_filename))
> filename = parsed_url.path
> log.Debug("webdav path decoding and translation: "\
> "%s -> %s" % (raw_filename, filename))
>
> In other words, other than URL unquoting, the raw filename is passed directly
> to urlparse(), and the 'path' property is accessed thereafter.
>
> So I am at a loss, provided that the scheme in the original url truly is
> exactly the string "https" and nothing else.
Well, it's not (at least on my side): I use "webdavs://address@hidden".
Thorsten
--
"I'm a vet. I'm a pro. Hell, I been here /eight months/."
-- Three Dead Trolls in a Baggie, "Welcome to the Internet helpdesk"
- [Duplicity-talk] Re: First restore failing, (continued)
- [Duplicity-talk] Re: First restore failing, Thorsten Kampe, 2008/03/07
- Re: [Duplicity-talk] Re: First restore failing, Peter Schuller, 2008/03/07
- [Duplicity-talk] Re: Re: First restore failing, Thorsten Kampe, 2008/03/08
- Re: [Duplicity-talk] Re: Re: First restore failing, Peter Schuller, 2008/03/08
- Re: [Duplicity-talk] Re: Re: First restore failing, Peter Schuller, 2008/03/08
- [Duplicity-talk] Re: Re: Re: First restore failing, Thorsten Kampe, 2008/03/08
- Re: [Duplicity-talk] Re: Re: First restore failing, Darik Horn, 2008/03/08
- Re: [Duplicity-talk] Re: Re: First restore failing, Peter Schuller, 2008/03/09
- [Duplicity-talk] Re: Re: Re: First restore failing, Thorsten Kampe, 2008/03/09
- Re: [Duplicity-talk] Re: Re: Re: First restore failing, Peter Schuller, 2008/03/09
- [Duplicity-talk] Re: Re: Re: Re: First restore failing,
Thorsten Kampe <=
- Re: [Duplicity-talk] Re: Re: Re: Re: First restore failing, Peter Schuller, 2008/03/10
- Re: [Duplicity-talk] Re: Re: Re: First restore failing, Kenneth Loafman, 2008/03/10
- Re: [Duplicity-talk] Re: Re: Re: First restore failing, Peter Schuller, 2008/03/10
- Re: [Duplicity-talk] Re: Re: Re: First restore failing, Peter Schuller, 2008/03/14
- [Duplicity-talk] Re: Re: Re: Re: First restore failing, Thorsten Kampe, 2008/03/15
- Re: [Duplicity-talk] Re: Re: Re: Re: First restore failing, Peter Schuller, 2008/03/15