Based on http://www.selenic.com/repo/index.cgi/hg/rev/59acb9c7d90f , it appears the very latest Mercurial versions work around the Python bug. While recompiling Python would be something of a hassle, building Mercurial is relatively straightforward, so I'd recommend trying the latest Mercurial and seeing if the problem goes away. If it doesn't, posting the --debug output from hg would help us determine whether it's something on our end.
Also, it's the same repository whether accessed via http or https; you only have to access the repository over https if you are pushing changes. So if all else fails, you can stay synced over http while inside the proxy and push over https when you have a direct connection available. -- Jacob Lee [email protected] On Tue, Jun 2, 2009 at 3:39 PM, Janne Härkönen <[email protected]> wrote: > > Hello, > > I tried to clone my projects (rfdoc) wiki with hg. > I have to connect through proxy, but it seems that cloning the https > repository does not work through proxy. > I can clone the http repository just fine. > > Based on this issue: > http://www.selenic.com/mercurial/bts/issue967 > > and this conversation: > http://www.nabble.com/https-over-proxy-and-other-stuff--)-td14729475.html > > it seems that the only way to get this working is patching mercurial > and possibly also Python. > > Am I correct, or is there a simpler way to get this working? > > > __janne > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
