-
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
Update the scripts used to generate the ucsc-XYZ recipes #50325
Update the scripts used to generate the ucsc-XYZ recipes #50325
Conversation
@bgruening This is the result of your suggestion at #50106 (comment) What would be the best way to rebuild the recipes ?
|
Oh cool, I didn't realize these scripts existed. I could run this on bulk once it's merged. Should be relatively quick since these aren't interdependent like bioconductor recipes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks a lot!
@@ -23,14 +26,14 @@ requirements: | |||
- libpng | |||
- libuuid | |||
- mysql-connector-c | |||
- openssl | |||
- libopenssl-static |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting why is this needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tools require libssl.a instead of libssl.so. I am not sure since when though.
I have seen some recipes using includes.patch
to change .a
to .so
. I decided to keep the original build, i.e. to not patch it, and use the new dependency instead.
doc_url: "https://github.com/ucscGenomeBrowser/kent/blob/master/README" | ||
|
||
extra: | ||
additional-platforms: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add a doi as reference here: https://genome.ucsc.edu/cite.html#ref
Maybe the bigwig, bigbed paper? https://doi.org/10.1093/bioinformatics/btq351
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please give me the YAML snippet that I should add? Or please push it yourself to this PR!
scripts/ucsc/template-build-cp.sh
Outdated
mkdir -p "$PREFIX/bin" | ||
cp {program_source_dir}/{program} "$PREFIX/bin" | ||
chmod +x "$PREFIX/bin/{program}" | ||
cp -f {program_source_dir}/{program} "${{PREFIX}}/bin" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the force needed, or are we masking potential error here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an improvement by @mencian to one of my previous PRs.
I could remove it if there is a chance to mask some problem!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about the reason, so I would rather remove.
This is super cool, thanks for updating them. We should use the |
Thanks, @aliciaaevans ! There are ~200 disabled ucsc- recipes in |
Done! |
scripts/ucsc/template-build-cp.sh
Outdated
mkdir -p "$PREFIX/bin" | ||
cp {program_source_dir}/{program} "$PREFIX/bin" | ||
chmod +x "$PREFIX/bin/{program}" | ||
cp -f {program_source_dir}/{program} "${{PREFIX}}/bin" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about the reason, so I would rather remove.
bioconda#50325 (review) Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found a better one, sorry.
Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
…h known build issues on aarch64 Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
Co-authored-by: Björn Grüning <[email protected]>
bioconda#50325 (review) Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
Co-authored-by: Björn Grüning <[email protected]>
19753d4
to
12d77ef
Compare
Set -x for easier debugging Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
@BiocondaBot please add label |
To be consistent with the SKIP list Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @martin-g
@@ -198,6 +197,12 @@ def program_subdir(program, names): | |||
'gfServer', | |||
] | |||
|
|||
# A list of programs which have problems to build on linux-aarch64 | |||
SKIP_AARCH64 = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think at some point we should have a global list, that script like this one can consume.
@martin-g I've got time today to get this started on bulk. |
Still working though timeouts and disk space limits, but here are failures so far: https://github.com/bioconda/bioconda-recipes/wiki/build-failures-bulk I think the aarch failures are all that |
(I'm still using this PR for notes about this bulk update for ucsc.) I've removed |
Thank you, @aliciaaevans ! In #50368 @mencian added support for osx-64 to one of the ucsc recipes. |
This PR updates the scripts used to generate the
ucsc-xyz
recipes.See #50323 and #50324 for examples of the changes in the recipes.
Once this PR is merged the other recipes may be pushed in bulk ?!
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
General instructions
@BiocondaBot please add label
command.@bioconda/core
in a comment.Instructions for avoiding API, ABI, and CLI breakage issues
Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify
run_exports
(see here for the rationale and comprehensive explanation).Add a
run_exports
section like this:with
...
being one of:{{ pin_subpackage("myrecipe", max_pin="x") }}
{{ pin_subpackage("myrecipe", max_pin="x.x") }}
{{ pin_subpackage("myrecipe", max_pin="x.x") }}
(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin="x.x.x") }}
(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin=None) }}
while replacing
"myrecipe"
with eithername
if aname|lower
variable is defined in your recipe or with the lowercase name of the package in quotes.Bot commands for PR management
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.
Note that the
@BiocondaBot please merge
command is now depreciated. Please just squash and merge instead.Also, the bot watches for comments from non-members that include
@bioconda/<team>
and will automatically re-post them to notify the addressed<team>
.