v@lists.galaxyproject.org>
Subject: Re: [galaxy-dev] ERROR: PIP is not a legl parament of an Ansible Play
Hi Bill, can you describe what exactly you have done?
What would be good is if you could post the beginning of your tool_list.yml
file,
the command that you used to run the playbook, the ver
s.yaml
>>
>> The playbook was downloaded end of March, following the link given on the
>> Galaxy tool installation guide.
>>
>> Manual installation of the tools one-by-one from the Admin web page
>> works. The tools installed show up on the web page.
>>
>>
>&
lect the installed tools? How can I make the
> tools installed with the Ansible playbook visible on the web front end?
>
> Thanks,
>
> Bill
>
>
>
> *From:* Enis Afgan [mailto:enis.af...@irb.hr]
> *Sent:* Friday, April 8, 2016 9:19 AM
>
>
> *To:* Willia
: William Ge
Cc: Enis Afgan ; galaxy-dev@lists.galaxyproject.org
Subject: Re: [galaxy-dev] ERROR: PIP is not a legl parament of an Ansible Play
Hi Bill, can you describe what exactly you have done?
What would be good is if you could post the beginning of your tool_list.yml
file,
the command that you
laxy-dev@lists.galaxyproject.org
> *Subject:* Re: [galaxy-dev] ERROR: PIP is not a legl parament of an
> Ansible Play
>
>
>
> The location of that dir is defined in shed_tool_conf.xml[.sample] and
> defaults to ../shed_tools. The reasoning is described here, under item #2
, April 8, 2016 9:19 AM
To: William Ge
Cc: Marius van den Beek ;
galaxy-dev@lists.galaxyproject.org
Subject: Re: [galaxy-dev] ERROR: PIP is not a legl parament of an Ansible Play
The location of that dir is defined in shed_tool_conf.xml[.sample] and defaults
to ../shed_tools. The reasoning is
van den Beek ;
galaxy-dev@lists.galaxyproject.org
Subject: Re: [galaxy-dev] ERROR: PIP is not a legl parament of an Ansible Play
The location of that dir is defined in shed_tool_conf.xml[.sample] and defaults
to ../shed_tools. The reasoning is described here, under item #2:
https
.@irb.hr]
> *Sent:* Thursday, April 7, 2016 7:06 AM
> *To:* William Ge
> *Cc:* Marius van den Beek ;
> galaxy-dev@lists.galaxyproject.org
>
> *Subject:* Re: [galaxy-dev] ERROR: PIP is not a legl parament of an
> Ansible Play
>
>
>
> Hi Bill,
>
> Do you have the value
Cc: Marius van den Beek ;
galaxy-dev@lists.galaxyproject.org
Subject: Re: [galaxy-dev] ERROR: PIP is not a legl parament of an Ansible Play
Hi Bill,
Do you have the value set in Galaxy's $GALAXY_ROOT/config/galaxy.ini file for
setting tool_config_file option? I believe this variable shou
ny resulst.
> Please point me to the right directions.
>
>
>
> Thanks,
>
> Bill
>
>
>
> *From:* Marius van den Beek [mailto:m.vandenb...@gmail.com]
> *Sent:* Friday, March 4, 2016 12:27 PM
> *To:* William Ge
> *Cc:* Dannon Baker ;
> galaxy-dev@list
any resulst. Please point me to
the right directions.
Thanks,
Bill
From: Marius van den Beek [mailto:m.vandenb...@gmail.com]
Sent: Friday, March 4, 2016 12:27 PM
To: William Ge
Cc: Dannon Baker ; galaxy-dev@lists.galaxyproject.org
Subject: Re: [galaxy-dev] ERROR: PIP is not a legl parament
From: Marius van den Beek
Sent: Friday, March 4, 2016 12:26 PM
To: William Ge
Cc: Dannon Baker; galaxy-dev@lists.galaxyproject.org
Subject: Re: [galaxy-dev] ERROR: PIP is not a legl parament of an Ansible Play
Thanks, Marius! That got me through!
The Galaxy
-
> *From:* Marius van den Beek
> *Sent:* Friday, March 4, 2016 11:03 AM
> *To:* William Ge
> *Cc:* Dannon Baker; galaxy-dev@lists.galaxyproject.org
> *Subject:* Re: [galaxy-dev] ERROR: PIP is not a legl parament of an
> Ansible Play
>
> The list of tools inst
uess this is Python 2.6
issue. Any solutions known?
Thanks,
Bill
From: Marius van den Beek
Sent: Friday, March 4, 2016 11:03 AM
To: William Ge
Cc: Dannon Baker; galaxy-dev@lists.galaxyproject.org
Subject: Re: [galaxy-dev] ERROR: PIP is not a legl parament o
this script somewhere?
>>
>>
>> Best regards,
>> Bill
>>
>> --
>> *From:* Marius van den Beek
>> *Sent:* Friday, March 4, 2016 7:25 AM
>> *To:* Dannon Baker
>> *Cc:* William Ge; galaxy-dev@lists.galaxyp
e. Is there a
> step-by-step guide for using this script somewhere?
>
>
> Best regards,
> Bill
>
> --
> *From:* Marius van den Beek
> *Sent:* Friday, March 4, 2016 7:25 AM
> *To:* Dannon Baker
> *Cc:* William Ge; galaxy-dev@lists.gala
somewhere?
Best regards,
Bill
From: Marius van den Beek
Sent: Friday, March 4, 2016 7:25 AM
To: Dannon Baker
Cc: William Ge; galaxy-dev@lists.galaxyproject.org
Subject: Re: [galaxy-dev] ERROR: PIP is not a legl parament of an Ansible Play
Hi Bill,
I think you&#x
Hi Bill,
I think you're trying to use the ansible-galaxy-tools role as a playbook:
This won't work, you can only include the role in your playbook,
or use this playbook https://github.com/afgane/galaxy-tools-playbook
You can also directly use the python script in
https://github.com/galaxyproject/a
I haven't seen this before but did a little googling. What version is your
ansible installation? If it's a little bit older, (
https://github.com/ansible/ansible/issues/5412) might be what you're seeing.
It's a bit of a long read, but it looks like reinstalling or updating your
ansible (or inst
Hi, all,
Sorry to bother you again. I am trying to install tools using the script. I
have downloaded the playbook, but stuck here:
[galaxy@Pegasus ansible-galaxy-tools]$ ansible-playbook tasks/tools.yml -i
"localhost," --extra-vars galaxy_tools_api_key=xcd2Glx
ERROR: pip is not a legal parame
20 matches
Mail list logo
