Thanks for the hint - that may be due to the fact that mercurial as
package only comes via a repository dating back to SLES 11 SP1 - there
seems to be no newer one. I just looked up the version: instead of
current v2.6.2 it's v1.0.2 (!)
On the other hand I'm glad that this reads like it does not affect
galaxy. btw: just started the server up, no complains yet.
Dannon Baker schrieb:
On Tue, Jun 18, 2013 at 10:54 AM, Sebastian Schaaf
Thus, the cloning process as the LDAP user (did not want to store
the foreign username/password explicitly in the galaxy user files)
worked, although I get this message:
"*** failed to import extension hgext.imerge: no module named imerge"
(once at the process' beginning and once at the end)
Anyway, this seems to be more a warning than an error. I found
possibility to silence it, but would like to understand what the
missing may cause.
Any clue, anyone?
Imerge is an old extension that used to ship with mercurial. Check
your .hgrc file for the [extensions] section and make sure there's no
line for imerge. If there is, remove it -- recent versions of
mercurial don't use this anymore.
Sebastian Schaaf, M.Sc. Bioinformatics
Faculty Coordinator NGS Infrastructure
Chair of Biometry and Bioinformatics
Department of Medical Informatics,
Biometry and Epidemiology (IBE)
University of Munich
Marchioninistr. 15, K U1 (postal)
Marchioninistr. 17, U 006 (office)
D-81377 Munich (Germany)
Tel: +49 89 2180-78178
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: