-
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
Conflicts using conda-forge and bioconda with strict channel priority #17186
Comments
Just to add that if I use channel priority bioconda > conda-forge, and pin the biopython version number to ensure it comes from conda-forge, I then still get conflicts:
|
|
@alimanfoo I can at least narrow down the failure. You should always use conda-forge > bioconda. |
And for me this works :(
But I also have still |
With the newer conda I get:
|
Thanks @simonbray for testing. |
Thanks @bgruening and @simonbray for following this up, sorry I fell of the radar here. This looks fixed to me too so will close. |
I would like to use conda with the
--strict-channel-priority
option, because this helps to ensure packages come from the desired channels.I have a problem regarding channel ordering which means I cannot install certain combinations of packages into the same environment, when using strict channel priority.
For example, if I use channel priority conda-forge > biopython, then I can install biopython and python 3.6 together, no problem:
However, if I try to use channel priority bioconda > conda-forge, I get a conflict:
In this particular case I realise that the problem occurs because biopython is available both channels, but is out of date in bioconda. It's solved in this case by channel priority conda-forge > bioconda. However, I think there is a more general problem, because there are other problems when I try to use conda-forge > bioconda. E.g., if I try to install bcftools with channel priority conda-forge > biopython then I get a conflict, e.g.:
This I particularly do not understand, because I am only asking to install a single package (bcftool), and so am surprised there can even occur a conflict/unsatisfiability.
Any help or advice here much appreciated.
The text was updated successfully, but these errors were encountered: