Adjust K nix caching#4844
Merged
automergerpr-permission-manager[bot] merged 4 commits intoJul 17, 2025
Merged
Conversation
tothtamas28
approved these changes
Jul 17, 2025
75b3b89
into
develop
18 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, the K repository caches two nix build on k-framework-binary.cachix.org for
kup:kandk.openssl.procps.secp256k1. While a proper build seems to be cached fork, the build fork.openssl.procps.secp256k1seems to be different than requested by kup. This kind of issue had been observed and fixed previously for kup packages.To debug this, I download dependencies that were pushed to the nix cache k-framework.cachix.org. But the K repository does not yet push dependencies to this cache. Therefore, this repository adjusts the GitHub release workflow to also push nix build dependencies to k-framework.cachix.org.
In addition, caching is introduced for the package
k.openssl.secp256k1, which is a version that users are instructed to install in, e.g., the kontrol repository. This is why version should be cashed in the nix binary cache as well.