I am trying to push my Mercurial repository to Bitbucket using hg push <web address of my repo on bitbucket> and am getting:
abort: error: _ssl.c:507: error:14094410:SSL
routines:SSL3_READ_BYTES:sslv3 alert handshake failure
This only started happening after I updated Yosemite 10.10.1 (which I think is only available for developers).
Does anyone have any clue of how to fix this?
If you are using Mercurial 2.7 or 2.7.1 (time to upgrade!), you can experience this issue.
It's a bug causing Mercurial to only try SSLv3, instead of other options. If the server doesn't have SSLv3 (perhaps Bitbucket doesn't have this), the push will fail.
More details here...
Related
I am using SourceTree with Bitbucket.
I used to be able to push without errors.
Now I get
hg push --new-branch default
pushing to https://bitbucket.org/myusername/myrepository/branch/default
abort: HTTP Error 404: Not Found
Completed with errors, see above.
I can see the repository in the browser.
I can push from a different machine. It works correctly on a machine where the url is myusername#bitbucket.org/myusername/myrepository.
You have to drop the branch/default part of the URL. The canonical repository URL is https://bitbucket.org/myusername/myrepository/.
For some reason, bitbucket allows read operations from URL/more/stuff but not write operations.
I'm having this problem when trying to push to a remote server. It is a Mercurial repository on Phabricator. Here are my output.
hg commit -m "udpate README"
hg push
pushing to ssh://company.server
searching for changes
remote: abort: stream ended unexpectedly (got 0 bytes, expected 4)
I'm using the latest version of Mercurial 3.5.2+20151001 on Mac OS 10.10.
I have this problem from yesterday. During that time, I could successfully committed two times, although I did nothing.
Why the output somewhat looks like this question, the problem here is different, because I have deleted the repository and cloned again many times without any problem. (my first attempt to solve the problem)
The system admin and the server is at another city, so he can't take a look at my machine. Any help would be greatly appreciated.
This looks like there may be a problem with the server and client disagreeing on the new bundle2 format for the wire protocol introduced in 3.5. I'd recommend trying to temporarily downgrade to 3.4.2 (e.g. with pip install mercurial==3.4.2) to see if it fixes this. See this discussion on Phabricator. If it doesn't work, hg push --debug --traceback can provide more information on what exactly went wrong.
I'm getting errors when pushing and pulling from a repo on a server. We have a repository (a folder) on a LAN-server which we push our commits to. This worked from the beginning but now it seems to not find the changesets on the server anymore, so tortoisehg ends up by trying to push all the revisions it locally has, to the server.
Also, when I view the repository on the LAN-server in HG workbench, it doesn't show any revision, the only one I can see is a revision -1?
So my question is, what have could gone wrong? And is there a way to fix this? I already replaced the repository on the server with my local one, and that went well for a few days until it happened again.
Revision -1 is what mercurial shows on an empty repository right after a hg init without any commit whatsoever.
If your LAN server exports the repository over a windows network share, indeed it might have been a serious bug fixed in Mercurial 3.3.2 (see https://bz.mercurial-scm.org/show_bug.cgi?id=4546 - maybe you can reproduce that with a new test repo. Upgrade, if that's the case for you)
What Mercurial version are you using?
It's possible that you have been impacted by the bug fixed in Mercurial 3.3.2 (released yesterday).
The solution in that case is to upgrade to Mercurial 3.3.2.
I am on ubuntu 12.04 and using hg 2.5.2
I did a hg init and am trying to clone a repository using hg clone, hg dies with the following error
transaction abort!
rollback completed
abort: integrity check failed on 00changelog.i:16630!
I am pretty sure the repository isn't corrupted because I cloned the same repository on three or four other machines, this is specific to my machine.
Sometimes it fails with different errors (corrupted MAC on input) or at different points integrity check failed on 00changelog.i:11090!
Please help. Thanks
Try to run hg verify on remote repository and on your local copy. What does it say?
Update your Mercurial to the newest version.
Do you clone on hard drive? Then try to clone on another hard drive or on USB drive. And vice versa: if you clone on USB drive then try to clone on hard drive. Bad storage devices are a common reason of repository corruption as people say in comments to this answer.
Looks like there is some optimization that is turned on by default in Ubuntu 12.04 onwards.
This fixed the problem
ethtool -K eth0 rx off tx off
I use RhodeCode for a web-based frontend for mercurial. Clone work with successful auth, but all commits with tortoisehg end in /dev/null, like they never have existed. No error shown in tortoisehg, even in any log file. Commiting dirctly with the webinterface is working ....
Please check your rhodecode log for any messages when doing Push via Tortoise maybe it fails on authentication ? From our side there are no compatibilty issues with TurtoiseHG.