Thanks for the reply. This installation is using supervisor with uwsgi to run Galaxy using a virtualenv, and I did wonder why my install wasn't picking up Mercurial from there.
Based on your suggestion it turned out that I needed to add an 'environment' parameter like e.g.:
environment = VIRTUAL_ENV="/srv/galaxy/venv",PATH="/srv/galaxy/venv/bin:%(ENV_PATH)s"
to the supervisor .ini file in order to get the virtualenv on the PATH.
(I thought I'd tried this before without success but it works now, so I must have done something wrong previously - possibly a type in a path.)
(Also, a comment re the documentation: in the "Scaling and Load Balancing" section of the docs, the 'environment' parameter is only mentioned for handler processes and doesn't appear in the example config for web processes:
and since I don't have any handlers (I'm using the uwsgi + mules strategy) it didn't occur to me that I would need it. It might be useful if the docs clarified that 'environment' is also required for the web processes in this case.)
Thanks again for your help,
Peter Briggs email@example.com
Bioinformatics Core Facility University of Manchester
B.1083 Michael Smith Bldg Tel: (0161) 2751482
From: Marius van den Beek [firstname.lastname@example.org]
Sent: Monday, June 25, 2018 5:30 PM
To: Peter Briggs
Subject: Re: [galaxy-dev] Unable to install tools from toolshed/mercurial issue in release_18.05 instance
Recent galaxy releases are using the `hg` command that should be automatically installed along with other galaxy dependencies.
If you're running galaxy in a virtualenv then that virtualenv should have the `hg` script in the bin folder.
Depending on how you start galaxy you may need to add the virtualenv's `bin` folder to the `PATH`.
Hope that helps,