This should work to get you an update-able galaxy instance going forward, without having
to manually migrate anything.
Please note that this method will clobber any existing changes to code, so if you've
modified any of the core galaxy you'll need to patch the new files. All of your data
and database settings will remain intact (but still do steps 1 and 2).
1) Back up everything, just in case
2) Make sure you did step #1
2) cd into the root galaxy directory and `hg init`
3) create a file, <galaxy_root>/.hg/hgrc with the following two lines:
default = https://bitbucket.org/galaxy/galaxy-dist
4) And again from the galaxy root `hg pull`
5) Finally `hg update -C`
And you should be good to go.
On Jul 31, 2012, at 6:05 AM, Makis Ladoukakis <makis4ever(a)hotmail.com> wrote:
Dear Galaxy users,
I am running a Galaxy instance in my institution's server and I want to keep it up to
date with the latest release. Nevertheless when i try hg incomingi get the following
abort: There is no Mercurial repository here (.hg not found)!
Most probably the administrator of the server has downloaded the Galaxy-dist directory
without the use of Mercurial (I was suspicious of that all along as the directory of the
Galaxy installation is named galaxy_dist and not galaxy-dist). Is there another way to
update my instance?
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: