-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 andi to 0.13 #21578
update andi to 0.13 #21578
Conversation
@bioconda/core in this PR I intend to update andi to 0.13, and at the same time maybe fix a dependency issue, that I get with other packages. For example, I get
So it seems that andi 0.12 can have gsl not above 2.3.0. I am not sure where these version requirements for gsl are stored, I didn't see it in meta.yaml. Now I added gsl >=2.2 as a dependency in the hopes that it will also accept higher versions, resolving the conflict. |
Reposting to enable pings (courtesy of the BiocondaBot):
So it seems that andi 0.12 can have gsl not above 2.3.0. I am not sure where these version requirements for gsl are stored, I didn't see it in meta.yaml. Now I added gsl >=2.2 as a dependency in the hopes that it will also accept higher versions, resolving the conflict. |
@bioconda-bot please fetch artifacts @pmenzel Thanks, the GSL restriction comes from a global pinning file. I'm surprised the old version didn't get rebuilt when we updated the GSL pinning. |
No artifacts found on the most recent CircleCI build. Either the build failed or the recipe was blacklisted/skipped. |
Ah, I bet the recipe is blacklisted due to compilation issues. That'd explain things. |
Thanks for looking into it, Devon.
Maybe the used gcc is too old not have C11 threads? |
It's gcc 7. I'm guess that we need to pass |
Actually, glibc only added support in 2018 or so, so that'd be after the version we're using (HPCs don't exactly update frequently, we're building basically with centos 6). |
would it be helpful to ask the author for statically linked binaries, that could instead be used? |
That'd be one option |
Hi all, andi (or to be precise, its FASTA parser pasta) can be compiled without threads.h. Newer C version set Hope this helps, |
trying this: -D__STDC_NO_THREADS__=1
hurray, it seems to have worked! |
Thanks for your fast fix! :) quick question: Would you recommend to use phylonium (once it is available in bioconda) over andi when only having a handful of genomes? My understanding was that phylonium is "just" faster, but not more accurate. |
One could say that phylonium is andi, but faster. As long as your genomes are closely related you should not see a big difference in the estimated substitution rates. Note that “faster” means 2× for small data sets and minutes instead of hours for thousands of bacterial genomes. |
@BiocondaBot please merge |
I will attempt to upload artifacts and merge this PR. This may take some time, please have patience. |
Sorry, this PR cannot be merged at this time. |
@bioconda-bot please fetch artifacts |
Package(s) built on CircleCI are ready for inspection:
You may also use
Docker image(s) built:
|
@bioconda-bot please merge |
I will attempt to upload artifacts and merge this PR. This may take some time, please have patience. |
Thanks everyone for your work! |
Describe your pull request here
update andi to 0.13
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>
.