Erg... I am pretty ignorant about mercurial so I should probably not
respond to this but I will try. It is pretty common practice for the
Galaxy team to push bug fixes to the last release to the stable branch
of galaxy-central - which is very different than the default branch of
galaxy-central which contains active development. These don't go out
to galaxy-dist automatically to prevent the need to strip truly
egregious stuff out of the stable branch that the galaxy-dev news says
to target.

A quirk of this however is that the stable branch of galaxy-central is
actually a good deal more stable the stable branch of galaxy-dist. It
is what targets and at least a few other high profile
Galaxy maintainers have caught on to this trick as well.

I think you can update (or merge) the latest stable branch by doing
something like the following:

hg pull
hg update stable

We should probably do a better job of keeping the stable branch of
galaxy-dist up-to-date - but right now we just push out updates at
releases and for major security issues as far as I know.


On Fri, Mar 14, 2014 at 2:23 PM, Brian Claywell <> wrote:
> On Fri, Mar 14, 2014 at 9:01 AM, John Chilton <> wrote:
>> I believe this problem was fixed by Nate after the latest dist release
>> and pushed to the stable branch of galaxy-central.
>> If you are eager for this bug fix, you can track the latest stable
>> branch of galaxy-central instead of the galaxy-dist tag mentioned in
>> the dev news. Right now it has some other good bug fixes not in the
>> latest release.
> Ah, got it, thanks! Is it unfeasible to push bug fixes like those back
> to galaxy-dist/stable so those of us that would prefer stable to
> bleeding-edge don't have to cherry-pick commits?
> --
> Brian Claywell, Systems Analyst/Programmer
> Fred Hutchinson Cancer Research Center
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:

Reply via email to