Closed heruiyang closed 8 months ago
Hi! Sorry for the late reply -- I just saw this message -- and thank you for the interest in GASTON! I did not realize the build strings are an issue. I just pushed an update which removes the build strings from the environment.yml
file as suggested.
Thanks for figuring this out! Please let me know if installation works now, and also if you have any other questions! (Also feel free to email me directly at uchitra@princeton.edu, I am more likely to see an email)
Hi,
After the update, it fails to correctly install and the setup fails.
@parth2608 Oops, I always forget to remove the gaston package line. I just pushed an update. Can you try installing now?
Hi,
Thanks very much for creating this very interesting and useful method! I've been testing it out on some spatial datasets and just wanted to make a note that I had initially run into some issues with installing the conda environment to run the package from the
environment.yml
file.I ended up fixing the issue by removing the build strings (the strings after the second
=
in the package list) for all packages, as well as some (presumably OS-specific) packages that were causing problems, namelylibcups
,libgcc-ng
,libnsl
,libgfortran-ng
,libstdcxx-ng
,keyutils
,libxkbcommon
, and_openmp_mutex
. After that I could install the environment and run the GASTON package.I'm creating the issue for reference just in case anyone else runs into this problem, and so that the authors can update the yml file (e.g. using
conda env export --no-builds
should create a yml file with no build strings). Thanks again for your hard work in putting this method together!