-
Notifications
You must be signed in to change notification settings - Fork 1
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
Trouble installing using Mamba #16
Comments
Hey @cwinsnes, please excuse the late response. In the mean time, there are two solutions: Either switch to osx (or disable the M2 chip somehow, there's a way to get this done, but I'm not a Mac-User so, I don't know how) or install datasail from source by cloning the repo, removing the problematic dependencies from the |
I thought working within the Docker container would alleviate that issue as it's Linux x64. If compiling from source is the way, I'll try that |
That's actually a good point. Intuitively, I'd also assume mamba should go for the linux-64 build. Maybe some interference between the M2 chip and Docker? I have another idea: Can it be a problem with python? You're not specifying the version, so mamba may fall back to some default version, maybe python3.7? |
The problem unfortunately persists when I run the command with Could definitely be some interference between M2-chip and Docker. Not fully sure on how to approach it otherwise. |
Starting from v1, we will provide a |
Issue description
I am having trouble installing
DataSAIL
through mamba. It is unable to find the package datasail because it "does not exist".I run the command
mamba create -n sail -c conda-forge -c kalininalab -c bioconda DataSAIL
Which yields the following
The problem persists whether or not I run the create command with the additional
-c mosek
or not.System specifications
mamba 1.5.5
conda 23.11.0
python 3.10.13
Running on a Debian Bullseye (Debian 11.8) Docker image, with a MacOS Sonoma (M2 chip) as the underlying system.
It is not possible to install the package on the MacOS system directly due to the package
cd-hit
being unavailable on such a system.The text was updated successfully, but these errors were encountered: