Resolve conflicts in conda with priority to conda-forge#282
Resolve conflicts in conda with priority to conda-forge#282TomKellyGenetics wants to merge 4 commits intoENCODE-DCC:masterfrom
Conversation
|
Thanks for the contribution. Testing your PR on my end. |
|
Thanks, the installer script works apart from the I've updated the PR to prioritise the default channel. The cause of the issue was outdated bioconda packages conflicting with conda-forge. I hope this will save others the time of installing the pipeline with current releases of dependencies. |
|
I tested with your PR but failed with tons of conflicts. My Conda/Python version is 4.8.3/3.7.7. |
|
Thanks for looking into it. Have you tried running the pipeline on Python 3.8? I've managed to get it to work by installing the dependencies separately and thought the bioconda / conda-forge conflict was causing the problem. I can run the pipeline without errors in this environment. In case it helps to troubleshoot the issue for others, here are the details: Note some packages were installed by pip(3). This is a Linux Debian 9 server used for bioinformatics analyses so it's possible dependencies missing from conda were already installed on this system. |
|
Base python3 (in |
|
Thanks for explaining. If I understand correctly, the python version is fixed in If you don't think this is necessary, you may close the PR. I'm okay to simply leave it here in case it helps others running into same issue. |
|
Can we merge this in please? this seems to resolve all the install issues we have been having |
|
For convenience, I've merged the latest version of the pipeline into my branch and resolved conflicts, i.e., applied the changes to both conda and mamba calls. 😄 |
|
Test this PR again but failed with lots of conflicts. Let me drop |
See issue here: bioconda/bioconda-recipes#17186