You can verify this with 'hg branch', but it looks like you're tracking the
default branch of -dist, where you want to be on stable. 'hg update
stable' should fix this, and the issue you're seeing.
You should only have to do this once, next time you update (with just hg
pull -u) you'll stay on st
Dear Dannon,
Here is the 'hg tip' result:
changeset: 9312:788cd3d06541
tag: tip
parent: 9310:19f6e62bd372
parent: 9311:d7f37a2fe690
user:Nate Coraor
date:Mon Apr 08 12:30:08 2013 -0400
summary: Merged stable.
--
Olivia
Le 29/04/13 15:05, Dannon Baker
Hey, it is not just me! Your commits are definitely in galaxy-dist,
they just might not be part of the most recent stable tag.
https://bitbucket.org/galaxy/galaxy-dist/commits/80291f7ad4576c95f70eaed2f36cc5a95cf303fb
The hg new workflow is easy to mess up, it use to be that you could
just trust w
Olivia,
There's a fix for this available in galaxy-central, but I'm surprised
you're seeing it in -dist as I thought the problem was introduced after the
dist freeze. Can you provide the output of 'hg tip'?
-Dannon
On Mon, Apr 29, 2013 at 6:53 AM, Olivia Doppelt
wrote:
> Hello to All,
>
> I w
Hello to All,
I would like to reiterate this problem because it is causing major
problems in tha managment of our Galaxy instance
Are there some clues on how to solve this issue ?
Best regards,
--
Olivia Doppelt-Azeroual, PhD
Pasteur Institute, Paris
Le 23/04/13 22:38, Fabien Mareuil a écr
Hi all,
We encountoured an error with the galaxy api since the last galaxy-dist
revision.
here is an example of a command line that doesn't work (xxx stand for the
admin key) :
./display.py xx http://localhost:18084/api/users
we obtain the following error:
HTTP Error 50
