Confusion on Updating Code
Hi guys, I'm trying to do my first update on my local galaxy install (it's been a few months at least since I installed) I'm trying to follow the instructions here to update the code: http://wiki.galaxyproject.org/Admin/Get%20Galaxy#Keep_your_code_up_to_date My first question is how do I roll back if something goes wrong in the upgrade? My second question is that this page http://wiki.galaxyproject.org/DevNewsBriefs/2013_02_08 says that I need to do something to get onto the stable branch? Right now when I run hg branch it says default. I'd prefer to be on stable. Any idea what I should do? (and again how can I roll back to the code i have now if something goes wrong?) Thanks, Greg Summary information: [galaxy@vm244]/usr/local/galaxy/galaxy-dist>hg summary parent: 7986:12fcd068b12e tip Do not hide failed datasets with HideDatasetAction post job action. branch: default commit: 3721 modified, 9 unknown update: (current)
On Feb 15, 2013, at 10:45 AM, greg wrote:
Hi guys,
I'm trying to do my first update on my local galaxy install (it's been a few months at least since I installed)
I'm trying to follow the instructions here to update the code: http://wiki.galaxyproject.org/Admin/Get%20Galaxy#Keep_your_code_up_to_date
My first question is how do I roll back if something goes wrong in the upgrade?
Hi Greg, Collect your current changeset with: % hg parents changeset: 8563:a4113cc1cb5e tag: release_2013.01.13 parent: 8529:ce62bf5a91f8 user: Daniel Blankenberg <dan@bx.psu.edu> date: Thu Jan 10 14:57:37 2013 -0500 summary: Fixes for Tool.check_and_update_param_values_helper() to check that the type of value provided is valid for the input parameter currently declared. Fixes an issue where rurun would select the wrong input dataset. Update: % hg pull % hg update release_2013.02.08 Migrate: % sh manage_db.sh upgrade Pay attention to whatever the first revision you are migrating from is. Probably 109 if you were at the 1/13 release. If you need to downgrade: % sh manage_db.sh downgrade <old_db_version> % rm lib/galaxy/model/migrate/versions/*.pyc % hg update <old_changeset>
My second question is that this page http://wiki.galaxyproject.org/DevNewsBriefs/2013_02_08 says that I need to do something to get onto the stable branch? Right now when I run hg branch it says default. I'd prefer to be on stable. Any idea what I should do? (and again how can I roll back to the code i have now if something goes wrong?)
The stable branch is new, so your old clone won't have it until you pull new changesets. As long as you do `hg pull` rather than `hg pull -u` and then explicitly update to the release tag or stable branch (`hg update release_2013.02.08` or `hg update stable`), you'll be on the stable branch. --nate
Thanks,
Greg
Summary information:
[galaxy@vm244]/usr/local/galaxy/galaxy-dist>hg summary parent: 7986:12fcd068b12e tip Do not hide failed datasets with HideDatasetAction post job action. branch: default commit: 3721 modified, 9 unknown update: (current) ___________________________________________________________ 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:
Thanks! One followup, see below. -Greg On Fri, Feb 15, 2013 at 11:01 AM, Nate Coraor <nate@bx.psu.edu> wrote:
On Feb 15, 2013, at 10:45 AM, greg wrote:
Migrate:
% sh manage_db.sh upgrade
Pay attention to whatever the first revision you are migrating from is. Probably 109 if you were at the 1/13 release.
Where would the "109" come from? How would I find my number?
If you need to downgrade:
% sh manage_db.sh downgrade <old_db_version> % rm lib/galaxy/model/migrate/versions/*.pyc % hg update <old_changeset>
What would I use for <old_db_version>?
On Feb 15, 2013, at 11:13 AM, greg wrote:
Thanks! One followup, see below.
-Greg
On Fri, Feb 15, 2013 at 11:01 AM, Nate Coraor <nate@bx.psu.edu> wrote:
On Feb 15, 2013, at 10:45 AM, greg wrote:
Migrate:
% sh manage_db.sh upgrade
Pay attention to whatever the first revision you are migrating from is. Probably 109 if you were at the 1/13 release.
Where would the "109" come from? How would I find my number?
Prior to running the database upgrade, you can use the `version` subcommand to determine your current database version: % sh manage_db.sh version 109
If you need to downgrade:
% sh manage_db.sh downgrade <old_db_version> % rm lib/galaxy/model/migrate/versions/*.pyc % hg update <old_changeset>
What would I use for <old_db_version>?
109 in my example, it might be different for you if you're running an older version of Galaxy. --nate
participants (2)
-
greg
-
Nate Coraor