-
Notifications
You must be signed in to change notification settings - Fork 44
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
Annoying warnings abour replacing existing signature after moving ~/.spack contents into code tree #1018
Comments
@climbfuji can you try adding these to setup.sh and see if it clears things up? export SPACK_DISABLE_LOCAL_CONFIG=true
export SPACK_USER_CONFIG_PATH=/dev/null |
Thanks @AlexanderRichert-NOAA. I tried but with that
Since that is by now so deeply enshrined in our user's brains (and mine!) I would had to change that unless it makes the process simpler. |
Ah right. How about just the SPACK_USER_CONFIG_PATH setting (skip setting SPACK_DISABLE_LOCAL_CONFIG)? |
With only
|
Googling for "replacing existing signature" it appears to be a MacOS thing, not a Spack thing. Somewhere there are settings that need to be removed/refreshed, but I don't know where (it's something to do with Apple's 3rd party developer system, but that's all I can figure out... maybe there's some certificates in your Keychain settings that can be reset..?). Unless you're able to identify what/where that is, can we either disable this on MacOS for now, or give it an optional flag which we will just use when deploying on the tier-1 systems? |
I’ll turn this feature off for macOS (in setup.sh) - will do shortly. Thanks!
… On Mar 13, 2024, at 2:40 PM, Alex Richert ***@***.***> wrote:
Googling for "replacing existing signature" it appears to be a MacOS thing, not a Spack thing. Somewhere there are settings that need to be removed/refreshed, but I don't know where (it's something to do with Apple's 3rd party developer system, but that's all I can figure out... maybe there's some certificates <https://stackoverflow.com/questions/66427145/is-there-a-way-to-fix-error-replacing-existing-signaturewarning-unable-to-buil> in your Keychain settings <https://forums.developer.apple.com/forums/thread/119071> that can be reset <https://stackoverflow.com/questions/56889119/replace-existing-signature-error-when-deploying>..?). Unless you're able to identify what/where that is, can we either disable this on MacOS for now, or give it an optional flag which we will just use when deploying on the tier-1 systems?
—
Reply to this email directly, view it on GitHub <#1018 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5C2RIUQTGXDDJNGLKNAOLYYC2S5AVCNFSM6AAAAABEGME7QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJVG4ZDOOJTG4>.
You are receiving this because you were mentioned.
|
Is your feature request related to a problem? Please describe.
After we move the contents of
~/.spack
into the current code tree, I get these warnings when I runspack concretize
:Describe the solution you'd like
No such warnings
Additional context
n/a
The text was updated successfully, but these errors were encountered: