-
Notifications
You must be signed in to change notification settings - Fork 206
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
pixi add
only works on the project's supported platform
#650
Comments
pixi add
only works on the projects platformpixi add
only works on the project's supported platform
Using the I can't remember that we supported the adding of a package without also being on that platform but that might be something we want to get in there. |
I think intially we didnt also install the environment during add. I think we could consider not installing the environment if the platform is not supported. Possibly with a warning? WDYT? |
Just FYI: it worked for me in 0.6.1 (big jump I know, I just upgraded yesterday). I think not installing with a warning would be great! The use case of creating lockfiles for another platform might be quite common if the actual code runs on a remote machine with a potentially different OS than the local one. |
I think it would be better to make the |
…668) fixes #650 reproducible case (on Linux): ```yaml channels = ["conda-forge"] platforms = [ # "linux-64", "osx-arm64", ] name = "bug" [dependencies] python = "=3.11.*" ``` Run: ``` $ pixi add --no-install ruff WARN pixi::environment: Adding dependency for unsupported platform (linux-64). ✔ Added ruff ``` `ruff = ">=0.1.13,<0.2"` added to `pixi.toml` 🎉 --------- Co-authored-by: Ruben Arts <[email protected]>
Checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
Output:
Issue description
E.g. when on M1 Macs,
pixi add ruff
would fail when"osx-arm64"
is commented out.pixi add --no-install ruff
also fails.Expected behavior
I know
pixi
supported building lockfiles for another platform some time ago. Is this intended? I am using version0.11.0
.The text was updated successfully, but these errors were encountered: