-
Notifications
You must be signed in to change notification settings - Fork 3
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
new DESI LS commit, but no update on galaxy #149
Comments
It's not in pypi either. @volodymyrss could you have a look, why this is stuck? In any case, Galaxy tools don't use pip dependencies by design. The only thing the bot does is adding a comment about the packages that are not in conda to the tool description xml. Then, it's up to tool(workflow) developer to decide on an action to take |
I understand better now. I will wait for update of oda-api to be done, then. Thanks! |
@dsavchenko @volodymyrss it seems to me that starting 1.2.30 the build test is failing : https://dev.azure.com/conda-forge/feedstock-builds/_build?definitionId=20327&_a=summary and the latest version on conda-forge 1.2.28. So I suppose that given the failed tests, the oda-api package is not updated. Could this be the case? Thanks! |
I think this issue is done, isn't it? The oda-api version is good now. |
@dsavchenko I have pushed a newer version of DESI workflow, where I moved the oda-api requirement as "pip" requirement (still in environment.yml) since I saw that the newest version of oda-api is not on conda. However, I did not see any update on galaxy. the error about imghdr is still there. Should I force the oda-api version in env.yml?
The text was updated successfully, but these errors were encountered: