-
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
samtools: Use same openssl for host and run #13909
Conversation
Not pinning openssl for runtime sometimes caused openssl-1.1 to be installed breaking samtools samtools: Bump build to rebuild after openssl change
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.
Looks good. I'm eager to try this.
(GitHub was blocked, so I rebased onto master
and force-pushed this. I'll try to merge after the re-test.)
I don't understand why this is sticking around. It seem trivial to merge. I'll try closing a competing samtools PR... Ah, that worked. |
Note: One user found a work-around which involves installing specific versions of openssl and ncurses. |
#13903 was following the same road. Though this shouldn't be necessary. |
Still no joy. I will rebuild pb-assembly and try again. |
I think this is what's causing the problem:
It's downgrading samtools instead of upgrading it to Alternatively checking which packages still build against |
ugh! |
Not pinning openssl for runtime sometimes caused openssl-1.1 to be installed breaking samtools
Related to #12100 and #13903
ℹ️ :
Bioconda has finished the GCC7 migration. If you are dealing with C/C++ or Python package it can be that you need to rebuild other dependent packages. Bioconda utils - update-pinning will assist you with that. If you have any questions please use issue 13578.