[issue3269] hg debuginstall should not check for username in users mercurial configuration
bugs at mercurial.selenic.com
Tue Feb 14 10:49:47 CST 2012
New submission from Matthew Giannini <mgiannini at tridium.com>:
In our company, we have a IT guy who is primarily responsible for upgrading
our Mercurial server to new versions. Part of the instructions we have
provided is to run "hg debuginstall" after upgrading to a new version of
Last night, he upgraded to Mercurial 2.1 and ran hg debuginstall. The script
failed with the error below. Because he is unfamiliar with Mercurial, he
was not aware that this is not actually an installation an error. But he
was concerned and rolled back the entire installation to a backup because he
thought he had messed up the installation.
I don't think this check makes sense in the debuginstall script because
having a username set does not a valid installation make. Further, there is
a good chance (especially in unix systems) that the installation user is not
actually a valid mercurial user and it would not make sense to set up an
.hgrc file for that user in the first place.
Checking encoding (ascii)...
Checking installed modules (/usr/local/lib/python2.6/dist-
Checking templates (/usr/local/lib/python2.6/dist-
Checking commit editor...
no username supplied (see "hg help config")
(specify a username in your configuration file)
1 problems detected, please check your install!
title: hg debuginstall should not check for username in users mercurial configuration
Mercurial issue tracker <bugs at mercurial.selenic.com>
More information about the Mercurial-devel