-
-
Notifications
You must be signed in to change notification settings - Fork 292
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
suggested replacement for binary_cache_secret_key_file is dysfunctional #679
Comments
|
Okay, then what is the recommended setting for serving signed binaries from the local store via Hydra? |
twhitehead
added a commit
to twhitehead/hydra
that referenced
this issue
Jan 7, 2020
Using the output path to avoid repeating previously failued builds results to changes in fixed output paths not being rebuilt (e.g., updating a src url). Use the derivation path instead to fix this.
twhitehead
added a commit
to twhitehead/hydra
that referenced
this issue
Jan 9, 2020
Using the output path to avoid repeating previously failued builds results to changes in fixed output paths not being rebuilt (e.g., updating a src url). Use the derivation path instead to fix this.
Sorry for the noise on this ticket. I accidentally typed 679 instead of 697 in my commit message. |
See also #548 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was using
binary_cache_secret_key_file=some_file
and, after upgrading Hydra, this stopped working with the message:I have replaced it with
store_uri=auto?secret-key=some_file
and it is still unhappy:What is the proper replacement for
binary_cache_secret_key_file=some_file
?Why does hydra print confusing messages here?
The text was updated successfully, but these errors were encountered: