-
Notifications
You must be signed in to change notification settings - Fork 0
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
Cannot concretize with an existing environment install #10
Comments
The workaround is do a spack uninstall access-om-nuopc before concretising. Its not a very feasible solution long-term. You can only have one environment per spack instance if you have can only have one install of a binary. |
It looks like Spack environments, by default, restrict the same package being installed even if it is a different version. Using
|
Hi @CodeGat , Is this what you found with CI/CD? |
Note: new versions (new hashes) of packages where installed in the process:
|
Note: There appears to be no need to remove and recreate the environment after a dependency change in the
|
Indeed, this is what we do in the CI/CD - the And yes, you don't have to remove the environment - editing the |
Doing a |
I think the error message should be better though :) |
When I create a new environment from https://github.com/ACCESS-NRI/ACCESS-OM3/tree/4ee6f99ef02163ef233cb8f0db13c6b1cb3ff4e8, it fails to concretise with this error:
This is the currently installed pacakges:
I believe the expected result is we can have two versions of
access-om3-nuopc
installedThe text was updated successfully, but these errors were encountered: