Closed Crampon16 closed 10 months ago
Dear @Crampon16
Thank you for pointing out this issue.
Do you get the same Problem if you do not install TRIQS at all?
I personally can't reproduce the issues on my M1 MacBook Pro.
We are investigating your problem.
Dear @Crampon16,
I assume you installed everything into the conda base environment? Can you try installing triqs and jupyter into a new environment? So after installing miniconda, you could do something like
conda create -n triqs
conda activate triqs
conda install jupyter
conda install -c conda-forge triqs
Note, if you install triqs before jupyter, you need to install jupyter from conda-forge, i.e.
conda install -c conda-forge jupyter
@Wentzell Installing Jupyter first (in the base environment) does not seem to break things, and notebooks look usable.
@Thoemi09 Using your commands and creating triqs in a separate environment removes completely the conda error message about libmamba and dynamic libraries, and the installation works. Installing jupyter from conda-forge makes it possible to complete the installation, but the error message stays.
I also just checked and the error message also appears if I install mamba using conda install -c conda-forge mamba
in the base environment. Maybe this is actually not a triqs problem ?
Installing jupyter from conda-forge makes it possible to complete the installation, but the error message stays.
Do you still get the error message in a separate environment? Or just in the base?
I also just checked and the error message also appears if I install mamba using conda install -c conda-forge mamba in the base environment. Maybe this is actually not a triqs problem ?
Yes, I think so too. I can reproduce similar errors when installing other packages in the base env. I don't think it is written somewhere explicitly, but it is probably best to always create separate environments when possible.
I just checked, installing triqs then jupyter, both through conda-forge, in a separate environment yields no error message.
Except if you have further tests to propose, I think we can close this. Thanks for your help !
No problem!
Just to wrap things up: The error seems to be related to: https://github.com/conda-forge/libarchive-feedstock/issues/69, which comes from a general compatibility issue between conda-forge and the defaults channel as described in https://conda-forge.org/docs/user/tipsandtricks.html.
In fact, adding conda-forge as a channel and setting the channel priority to strict before installing triqs and jupyter gets rid of the error message, even in the base env:
conda config --add channels conda-forge
conda config --set channel_priority strict
conda install triqs
conda install jupyter
However, it is recommended to use new environments anyway (see https://conda-forge.org/docs/user/introduction.html).
Thank you @Thoemi09 for the clarifications, and for providing instructions for a workaround!
This looks to be more of an anaconda issue than a triqs issue, so we are closing this.
We updated the documentation accordingly https://github.com/TRIQS/triqs/commit/39e05060a31fa0f5a8a9f2834cf1adf5c9fc8ae0
I am using minconda3 to install triqs on a MacBook. Installing triqs first prevents later installation of Jupyter. The other way around works fine.
Steps to Reproduce
conda install -c conda-forge triqs
conda install jupyter
Expected behavior: I can run
jupyter notebook
andimport triqs
inside.Actual behavior: I get the following error message:
Versions
Latest triqs version I suppose ? I am running this on a completely clean (nothing except triqs has been installed yet) M1 MacBook Air Sonoma. I got a similar issue on an Intel MacBook Pro running MacOS Sierra then Big Sur.
Additional Information
In the case I described but also when installing jupyter first then triqs (which successfully installs both), any later call to conda will display the error message