-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
galaxy-data: initial commit #26365
galaxy-data: initial commit #26365
Conversation
9c5f979
to
1fe5b6c
Compare
1fe5b6c
to
b1b3d9a
Compare
which is now at conda-forge
@natefoo we need also here a new version |
Co-authored-by: Nate Coraor <[email protected]>
@bioconda-bot please merge |
I will attempt to upload artifacts and merge this PR. This may take some time, please have patience. |
Does this perhaps need an explicit dependency on OpenSSL?
|
I guess this is because #17212 .. maybe be should force |
Wondering why conda chooses 0.14 .. |
Ah yes that seems to be the issue. |
TODO:
Describe your pull request here
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
@BiocondaBot please add label
command.@bioconda/core
in a comment.Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:
@BiocondaBot please update
@BiocondaBot please add label
please review & merge
label.@BiocondaBot please fetch artifacts
You can use this to test packages locally.
For members of the Bioconda project, the following command is also available:
@BiocondaBot please merge
Someone must approve a PR first!
This reduces CI build time by reusing built artifacts.
Also, the bot watches for comments from non-members that include
@bioconda/<team>
and will automatically re-post them to notify the addressed<team>
.