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 what is in galaxy-dist. I have messed up and grabbed the
wrong branch or tag a couple times and landed up with a very broken
Galaxy and I know JJ has done the same, but it looks like it is not
just an MSI problem.

I am not saying the new workflow isn't an improvement or should be
abandoned, I am just saying I am not yet competent enough to use it
properly and I am not the only one :).

-John


On Mon, Apr 29, 2013 at 8:05 AM, Dannon Baker <dannon.ba...@gmail.com> wrote:
> 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 <olivia.dopp...@pasteur.fr>
> wrote:
>>
>> 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 écrit :
>>
>>> 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 xxxxxxxxxxxxxxxxxxxxxxxxxx http://localhost:18084/api/users
>>>
>>> we obtain the following error:
>>>
>>> HTTP Error 500: Internal Server Error
>>>
>>> As you can see, the request is done locally, without going through a
>>> proxy
>>> or apache.
>>>
>>> The galaxy log is the following:
>>>
>>>
>>> 127.0.0.1 - - [23/Apr/2013:19:55:26 +0200] "GET /api/users?key=
>>> xxxxxxxxxxxxxxxxxxxxx HTTP/1.1" 500 - "-" "Python-urllib/2.6"
>>> Error - <type 'exceptions.AssertionError'>: use_remote_user is set but no
>>> HTTP_REMOTE_USER variable
>>>
>>> Do you have an idea to solve this problem?
>>> Thank in advance for your answer.
>>> Best regards
>>>
>>>
>>
>>
>> --
>> Olivia Doppelt-Azeroual, PhD
>> Tel: 92 15
>> CIB - Institut Pasteur
>>
>>
>> ___________________________________________________________
>> 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:
>>  http://lists.bx.psu.edu/
>>
>> To search Galaxy mailing lists use the unified search at:
>>  http://galaxyproject.org/search/mailinglists/
>
>
>
> ___________________________________________________________
> 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:
>   http://lists.bx.psu.edu/
>
> To search Galaxy mailing lists use the unified search at:
>   http://galaxyproject.org/search/mailinglists/

___________________________________________________________
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:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to