Conda conflicts install issue with latest qiime2-2020.11 (mac OSX)

Dear Qiimers,

I have been trying to install the latest qiime build (qiime2-2020.11) on my mac (Catalina OS).

After running the conda update I installed via

wget https://data.qiime2.org/distro/core/qiime2-2020.11-py36-osx-conda.yml
conda env create -n qiime2-2020.11 --file qiime2-2020.11-py36-osx-conda.yml
# OPTIONAL CLEANUP
rm qiime2-2020.11-py36-osx-conda.yml

After a very long

Collecting package metadata (repodata.json): done
Solving environment: |
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.

Here is the output (its very long and I could not capture all of it because i did not activate the iunlimited scroll history on this term) Hope it is of interest. https://pastebin.com/8dARMhdW

Please note that I could install the previous build qiime2-2020.8 without problems on the same system.

Many thanks for your help,

PM

Hi @pma
I think you may have run in the same isse discussed here:

They (thanks dev team :clap:) rebuilt the file during last ours, so if you download new copies of the environment files the issue should be fixed
Hope it solve the problem for you as well!
Luca

2 Likes

Thanks @llenzi !

I could install on my side by downgrading python to python=3.6.11 in the environment file (I saw it was python=3.6.11 in the linux and tried) and surprisingly it worked.
I will however rebuild the environment freshly using the new files you provide just to be sure.

For the record I switched to qiime2-2020.11 because I could not install empress within qiime2-2020.08 https://github.com/biocore/empress because of some nasty numpy issues. I can now in qiime2-2020.11

Many thanks !

PM

Hi @pma!

That is certainly an option, but one reason why I would suggest you not manually tamper with the contents of the environment file is because of testing and verification. We rigorously test and verify QIIME 2, the interfaces, and all of the core plugins - after testing, the precise versions of the packages we confirmed with are recorded in the environment file. If you manually change the env, then you are opting into untested conditions. I don’t really expect there to be any issues with your particular manual edits, but just wanted to provide a little context and food for thought (and provide a little warning for anyone else who might come across this discussion).

Thanks!

2 Likes

A post was split to a new topic: Locale issues 2020.11

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.