Open frankligy opened 1 year ago
As an update, the examination run by conda suggests it might be a conflict for the GNU C library associated with the conda version installed on my cluster, not sure if it is the main issue but just post it here in case helpful
The following specifications were found to be incompatible with your system:
- feature:/linux-64::__glibc==2.17=0
- feature:/linux-64::__unix==0=0
- feature:|@/linux-64::__glibc==2.17=0
- feature:|@/linux-64::__unix==0=0
- bioconda::hhsuite -> libgcc-ng[version='>=10.3.0'] -> __glibc[version='>=2.17']
- pyg::pyg -> pytorch=1.13 -> __glibc[version='>=2.17|>=2.17,<3.0.a0']
- pytorch -> __glibc[version='>=2.17|>=2.17,<3.0.a0']
- pytorch -> sympy -> __unix
Your installed version is: 2.17
Hello,
Thanks a lot for the awesome tool, I am not sure if it's just me, but I am even stuck at the first step trying to use conda to install the RF2 dependencies based on the yml file, The issue is always
finding conflicts
for packages across different conda channels (see full log txt file attached). I found a similar issue in stack overflow (https://stackoverflow.com/questions/58216917/create-conda-environment-found-conflicts-when-solving-environment-and-findi), which they indicate either it is a conda version issue or it is better to rewrite the yml file. I tried two different conda versions on Linux, and they all encountered the same issue.24031436_install.txt 24030912_install.txt
Has anyone else encountered the same problem here? Would it be possible to provide another yml file with a more explicit build version when exporting from the dev environment?
Thanks so much, Frank