Shouldn't explicitely pulling from a remote https+urllib://... branch just use urllib instead of ignoring the '+urllib' and revert to using pycurl?
I have the following use case:
1. I create a remote branch in a shared repository with: bzr push https+urllib://server/remote-branch
2. Another developer branches this remote branch performs changes and pushed these changes back to https+urllib://server/remote-branch
3. I try to pull the changes from the remote branch to my local branch with: bzr pull https+urllib://server/remote-branch
4. Result: I get the obvious self-signed certificate error from pycurl
The question is: the above workflow seems to be perfectly valid: why is bzr reverting to use 'pycurl' in my 'bzr pull' command if I am telling it explicitly to use 'urllib'? It seems to me that this is a different bug than #924220.
Thanks in advance for any feedback regarding this.
Shouldn't explicitely pulling from a remote https+urllib://... branch just use urllib instead of ignoring the '+urllib' and revert to using pycurl?
I have the following use case:
1. I create a remote branch in a shared repository with: bzr push https+urllib: //server/ remote- branch //server/ remote- branch //server/ remote- branch
2. Another developer branches this remote branch performs changes and pushed these changes back to https+urllib:
3. I try to pull the changes from the remote branch to my local branch with: bzr pull https+urllib:
4. Result: I get the obvious self-signed certificate error from pycurl
The question is: the above workflow seems to be perfectly valid: why is bzr reverting to use 'pycurl' in my 'bzr pull' command if I am telling it explicitly to use 'urllib'? It seems to me that this is a different bug than #924220.
Thanks in advance for any feedback regarding this.