-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
install_tool_dependencies: False
is not working
#29
Comments
These config values just get passed on to Galaxy: https://github.com/galaxyproject/ansible-galaxy-tools/blob/master/files/install_tool_shed_tools.py#L580. When you say "not reliable", does this mean running the script multiple times for the same Galaxy or just independent runs on different Galaxy instances? |
@afgane it actually never worked for me. I see the repositories in the Galaxy admin menue but they are just white and I need to trigger every installation manually. |
I will try to look at this at some point, just wanted to note it somewhere. |
Following up with this; this happens to repositories with "complex repository dependencies" which also happens when you trigger the installation through the UI. I'd say this is probably something that should be fixed in galaxy, but I'm not sure that's easy. |
Do we have any updates on this? |
Nope, not really. galaxyproject/galaxy#3745 |
So, ahm, maybe we should close the issue.
has always been working fine, if you define Problem is still the repository type dependencies, like suites and packages that get cloned and enter the database in status |
Is not working reliable. I get repositories added to the database but the installation is not triggered. This option get more and more important as we try to get first flavours up and running with pure conda/docker dependencies.
The text was updated successfully, but these errors were encountered: