Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Cannot add Mercurial repository hosted at Bitbucket
I am facing this issue (https://www.openhub.net/topics/9809) again: I cannot add a Mercurial URL like https://bitbucket.org/scalabench/scalabench; I always get a “Something seems wrong with your URL.”
Cloning locally with hg clone https://bitbucket.org/scalabench/scalabench works fine, though.
Hi Andreas Sewe;
I apologize for this difficulty. We have confirmed there is an issue, at least with adding Mercurial enlistments, and are working on it.
Hi Andreas;
Last week, we deployed a fix to the enlistment issue with Mecurial. May I ask that you try again and let us know if you encounter any difficulty?
Thank,
pdp
It still doesn’t work but I I get a better error message now:
The server did not respond to the 'hg id' command. Is the URL correct?
However, running hg id locally does give a server response, so I think there’s still a bug somewhere:
$ hg id https://bitbucket.org/scalabench/scalabench
3b6f04d61cf5
Hi Andreas;
Yes, I am getting the same behavior on the site.
I ran the command on the web server to see what is happening in production. This is what we get on one of our webservers:
$ hg id https://bitbucket.org/scalabench/scalabench
warning: connecting to bitbucket.org using legacy security technology (TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for more info
3b6f04d61cf5
The corrective action seems to be to upgrade Python to 2.7 according to the Mecurial site; ...users seeing this warning are strongly encouraged to run Mercurial with as new a version of Python 2.7 as possible...
The latest Python is 2.7.14 and we are running 2.7.6 in production. While we can update our Python, we are at least in the 2.7 version. So I added the configuration to disable the warning, and am now getting the same response you got when I run the command in the production environment.
However, that did not address the issue. I am opening a ticket so we can look into this further and I apologize for the inconvenience
FWIW, I’m on Python 2.7.10 here.
Hi Andreas;
I believe we have an answer. Not a solution yet, but an answer.
it seems that Mecurial assumes the existence of a default branch called default
.
Such a branch does not exist in the https://bitbucket.org/scalabench/scalabench repository.
We've not encountered this issue before, as far as I've been able to determine. Is there any chance that a default branch could be created?
pdp