-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error for creating conda env #8
Comments
Maybe it is a platform dependent issue. Which platform are you developing Mozart? Linux? I am testing on macOS Catalina 10.15.7 |
I'm using Linux 5.10.15-1-MANJARO and tested it on other Linux platforms and Windows works fine but didn't test it on macOS. |
Thank you so much for your information. I will try on a Linux machine. I believe Mozart is a great open source project, I really appreciate your team have put things together and a lot of people will benefit from this work. It will be nice to get Mozart working on macOS, as a lot of high-end developers for music are using Mac. |
Same issue for me on Windows 64-bit: `(base) C:\Users\Ken\Downloads\Mozart>conda env create -f requirements.yml Collecting package metadata (repodata.json): done Solving environment: failed` |
I am having the same issue as @ken830 , on Windows 10: ResolvePackageNotFound:
|
@AndyTQ @ken830
|
@aashrafh: Thank you. I tried with new requirements.yml from above, and this is what I see. It's a much shorter list.
|
Mostly, they are platform-specific packages. I already deleted them and tested the code on my Windows 10 machine but it seems that I posted the file content before saving it. Sorry for that.
|
@aashrafh: That worked! I was able to setup the environment. Thank you! |
@aashrafh Small request. Please push last worked requirements file to repository, it's realy works on macOS Catalina. Thanks! |
@dzen-it Done. Thank you for the macOS confirmation |
I got the following error:
conda env create -f requirements.yml
Collecting package metadata (repodata.json): done
Solving environment: failed
I tried on two different MacBook Pro, and got the same errors.
It will be great to provide some hints how to solve this problem.
Thanks!
The text was updated successfully, but these errors were encountered: