When I click and post it to ReviewBoard it just hangs and does nothing. How to get Tortoise to work with ReviewBoard?
Versions: Tortoisehg 2.1.2
Reviewboard: 1.5.5
Reviewboard from repositories was giving errors,
hg clone https://bitbucket.org/mdelagra/mercurial-reviewboard
Worked fine.
Related
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 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...
I have the all-in-one download with TortoiseHg 2.6.1 and Mercurial 2.4.1 installed on windows server 2k8. I created a repository, served it on port 8000. There are no mercurial configuration files setup right now for this repository. No global config files either. When I try to clone this repos through eclipse (MercruialEclipse plugin) from a remote computer over the internet, I get:
abort: HTTP Error 404: Not Found
What does this mean?
Thanks.
Found the solution. The command syntax was incorrect. The incorrect syntax I was using was
hg clone http://www.xyz.com:8000/<dirname for the repo clone>
The correct command is:
hg clone http://www.xyz.com:8000/ <dirname for the repo clone>
Should also mention that I am using version 2.3.2(mercurial)
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.
Here's the steps I take:
Clone mercurial project at the head.
On local repository, perform hg status (no results), then hg in (no changes).
mvn clean install. Build is successful.
mvn release:prepare.
Get's to the point where it's excuting a push
[INFO] EXECUTING: cmd.exe /X /C "hg push http://remoterepo/hg.project"
[ERROR]
EXECUTION FAILED
Execution of cmd : push failed with exit code: -1
Your Hg installation seems to be valid and complete. Hg version: 1.8.4 (OK)
Doing a hg status I now have:
? pom.xml.releaseBackup
? release.properties
From my understanding is that this happens when it could be creating a branch on the remote repo and the fix is to make sure I'm on the head. I'm on the head.
I've done this several times before and now this happens. Let me reiterate, I cloned the head and I couldn't clone a branch if I wanted to as none exist.
Now what? How do I fix this?
Thanks for any suggestions.
Joe
I figured it out. It was a authentication thing. The Maven release plugin does not use the authentication details in <project>/.hg/hgrc but it DOES in /<Users>/<UserName>/.hgrc. After I updated my password everything worked just fine.
First of all what happens when you try to do an hg push yourself on the command line ? If everything's fine you definitively have a problem, otherwise the error message should help you determine what is going wrong.
If I were you, I would check if I have the right to push to the remote destination.
Is http://remoterepo/hg.project the real output or did you changed it for confidentiality reason ? If it's the real output, you should check your Maven configuration to put the real repository path.
Concerning the output of hg status after the steps, it's totally normal, Maven creates some file in the directory. You can add them to your .hgignore file so Mercurial won't show them to you. More information about that in the documentation.