tag:support.hglabhq.com,2012-10-18:/discussions/problems/728-tortoisehg-error-command-returned-code-255HgLab: Discussion 2018-10-19T08:11:30Ztag:support.hglabhq.com,2012-10-18:Comment/352641752014-11-13T00:01:37Z2014-11-13T00:01:39ZTortoiseHg error - [command returned code 255 ...]<div><p>BTW - what is the difference between .hgrc and mercurial.ini in
a windows setting of c:\users\myUsername</p>
<p>Do we need them both?<br>
Are they read sequentially where last read has precedence, ala css
files?</p>
<p>Best practice is what?</p></div>pdavidsontag:support.hglabhq.com,2012-10-18:Comment/352641752014-11-13T09:20:58Z2014-11-13T09:20:58ZTortoiseHg error - [command returned code 255 ...]<div><p>Paul,</p>
<p>You're just pasting the wrong thing and HgLab is a bit confusing
here. To <a href=
"https://hglabhq.com/documentation/user-guide/repositories#cloning-using-tortoisehg">
clone using TortoiseHg</a>, you only need the URL part, i.e.
everything after the <code>hg clone</code> substring:</p>
<p><img src=
"https://hglabhq.com/content/documentation/img/cloning-using-tortoisehg.png"
alt="Cloning in TortoiseHg"></p>
<p>Storing passwords in plain-text anywhere is not exactly the best
idea. There's an excellent extension called <a href=
"http://mercurial.selenic.com/wiki/KeyringExtension">Keyring</a>,
which ships with TortoiseHg and which can be enabled from within
TortoiseHg Workbench in <em>File</em> - <em>Settings</em> -
<em>Extensions</em> by checking the "mercurial_keyring"
checkbox.</p>
<p>As for configuration files, they are very much like CSS, with
more "specific" files overriding less "specific" ones. Here's a
<a href="http://www.selenic.com/mercurial/hgrc.5.html#files">full
list</a>:</p>
<ul>
<li>/.hg/hgrc (per-repository)</li>
<li>%USERPROFILE%.hgrc (per-user)</li>
<li>%USERPROFILE%\Mercurial.ini (per-user)</li>
<li>%HOME%.hgrc (per-user)</li>
<li>%HOME%\Mercurial.ini (per-user)</li>
<li>\Mercurial.ini (per-installation)</li>
<li>\hgrc.d*.rc (per-installation)</li>
<li>HKEY_LOCAL_MACHINE\SOFTWARE\Mercurial (per-installation)</li>
</ul>
<p>Settings from earlier paths override later ones.</p>
<p>There's no "best practice" -- everyone picks whatever works in
their specific cases. For example, a System Administrator can tweak
Mercurial settings (via Group Policy or somesuch) in the Registry,
you can enable the extensions you use all the time in
<code>Mercurial.ini</code> from your <code>%USERPROFILE%</code> and
then you can fine-tune the settings on a per-repository basis.</p></div>Anton Gogolevtag:support.hglabhq.com,2012-10-18:Comment/352641752014-11-14T02:21:40Z2014-11-14T02:21:40ZTortoiseHg error - [command returned code 255 ...]<div><p>Well, I feel stupid. I must have stared at the documentation
examples many times and modified that line in TortoiseHg over and
over without cluing into the fact that it says Source</p>
<p>Thanks for the keyring hint. I was considering a jump to AD to
get around text passwords. Even if we are behind firewalls, bad
idea. keyring is trivial to implement and very helpful.</p></div>pdavidsontag:support.hglabhq.com,2012-10-18:Comment/352641752014-11-14T16:37:09Z2014-11-14T16:37:09ZTortoiseHg error - [command returned code 255 ...]<div><p>Glad I could help!</p></div>Anton Gogolevtag:support.hglabhq.com,2012-10-18:Comment/352641752014-11-17T07:53:20Z2014-11-17T07:53:20ZTortoiseHg error - [command returned code 255 ...]<div><p>Anton:<br>
Regarding the per-user level usage of %USERPROFILE%.hgrc vs
%USERPROFILE%\Mercurial.ini<br>
I see the [auth] section that HgLab makes use of, does it matter if
that is in mercurial.ini instead of .hgrc?<br>
I guess in other words, does HgLab search mercurial.ini for the
[auth] section?</p>
<p>In writing up a quick start for our coders, it would be easier
to refer to dealing with just one ini file…<br>
Not a big deal but I am curious.<br>
Thanks</p>
<ul>
<li>Paul Davidson GIS IT Lead<br>
(505) 768-2635 - Desk (505) 506-5960 - Cell</li>
</ul></div>pdavidsontag:support.hglabhq.com,2012-10-18:Comment/352641752014-11-28T09:23:03Z2014-11-28T09:23:03ZTortoiseHg error - [command returned code 255 ...]<div><p>Paul,</p>
<p>The .hgrc in %USERPROFILE% is there to mimic the way Unix/Linux
software is<br>
configured (with so-called "dotfiles"), so unless your developers
use both<br>
Windows and non-Windows platforms, there's no need to use .hgrc and
a<br>
single INI file will do just fine.</p>
<p>HgLab, being a server-side piece of software, can't possibly use
any of the<br>
client-side configuration files. It can only use server-side hgrc
files<br>
that are repository-specific to configure ACLs. See more here:</p>
<p><a href=
"https://hglabhq.com/documentation/user-guide/repositories#configuring-access-control">
https://hglabhq.com/documentation/user-guide/repositories#configuri...</a></p>
<p>To sum up, on Windows it's preferable to use Mercurial.ini in
%USERPROFILE%<br>
to configure global per-user settings.</p>
<p>On Monday, November 17, 2014, pdavidson <<br>
<a href=
"mailto:tender2+da8fec70500e131a05eb31bcb4706e734a2a2b1a3@tenderapp.com">
tender2+da8fec70500e131a05eb31bcb4706e734a2a2b1a3@tenderapp.com</a><br>
><br>
wrote:</p></div>Anton Gogolevtag:support.hglabhq.com,2012-10-18:Comment/352641752014-11-28T18:12:44Z2014-11-28T18:12:44ZTortoiseHg error - [command returned code 255 ...]<div><p>Thanks<br>
I should have caught the server side issue.</p>
<p>Sent from my iPhone</p></div>pdavidsontag:support.hglabhq.com,2012-10-18:Comment/352641752015-01-03T08:55:51Z2015-01-03T08:55:51ZTortoiseHg error - [command returned code 255 ...]<div><p>I am out of the office until Jan 5th, 2015</p>
<p>In the meantime, please contact:<br>
Bryan Ngyuen at<br>
<a href="mailto:bngyuen@abcwuq.org">bngyuen@abcwuq.org</a><br>
(505) 289-3203 or<br>
Michael Haley at<br>
<a href="mailto:mhaley@abcwuq.org">mhaley@abcwuq.org</a><br>
(505) 289- 3204</p>
<p>for all of your GIS IT or IR needs.</p>
<p>Thank you<br>
Paul Davidson</p></div>pdavidsontag:support.hglabhq.com,2012-10-18:Comment/352641752015-01-06T02:06:28Z2015-01-06T02:06:28ZTortoiseHg error - [command returned code 255 ...]<div><p>Anton:<br>
Please delete that re-opened email above and close the discussion
again.<br>
I was out of country and had an auto-reply system going which
clearly creates issues in this type of forum :-)</p>
<p>Thanks</p></div>pdavidson