-
Notifications
You must be signed in to change notification settings - Fork 992
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
Conda dependency resolver auto_installer fails if conda_prefix is too long #2537
Comments
@pvanheus I think this was fixed upstream: conda/conda-build#877 |
@bgruening The broken conda packages still need to be rebuilt, see conda/conda#2353 (comment) |
Sure, but this is a larger effort. It only happens for users with a large prefix afaik. |
I've written a new test (part of #2538) that will fail when we use a conda with this issue fixed) and added a warning message if the prefix is > 50 characters. This issue should be mentioned in the conda dependency manager docs too. |
This seems to be fixed with recent conda upgrade and is included in 17.01. xref #3482 |
But, there is still the message if the prefix is to long and galaxy.ini also contains text on to long prefix. Should be changed if the bug is fixed (also for job_working_directory). |
@bernt-matthias What message are you seeing? If it looks something like:
You may need to ping someone on bioconda to rebuild the package - this shouldn't happen with newer packages. |
Sorry, I should have been more specific. The warning message that is printed during galaxy (17.01) startup is:
galaxy.ini contains the following comment:
|
|
@mvdbeek Not in |
The conda dependency resolver (unsurprisingly) is affected by this conda issue: readthedocs/readthedocs.org#1902 . In short, if the conda_prefix and resulting environment name is longer than the name of the prefix used during package build time, the installer will fail. A typical error message is:
I doubt there is anything that can be done from the Galaxy side to fix this, but perhaps a documentation patch is in order.
The text was updated successfully, but these errors were encountered: