fix: updated zig FOD #116
Open
fix: updated zig FOD #116
Conversation
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
For whatever reason, the zig tarball URL we were using had changed, compromising the hash integrity. My best guess as to why Zig Software Foundation did this is they must've rolled some security update and saw it fit to break their permalinks... or they were never permalinks to begin with... I however wonder about the comment in flake.nix#L22 as it isn't making much sense to me. It claims that capy requires 2024.11.0-mach, however 0.14.1 is specified... 0.14.1 released on 2025-05-21, not in 2024... futhermore, even one version behind, 0.14.0, was released on 2025-03-05, even *it* wasn't in 2024. I have no clue what is up with this requirement, but for now with this fix capy seems to work just fine. I built a few examples just to check.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
For whatever reason, the zig tarball URL we were using had changed, compromising the hash integrity. My best guess as to why Zig Software Foundation did this is they must've rolled some security update and saw it fit to break their permalinks... or they were never permalinks to begin with...
I however wonder about the comment in flake.nix#L22 as it isn't making much sense to me. It claims that capy requires 2024.11.0-mach, however 0.14.1 is specified... 0.14.1 released on 2025-05-21, not in 2024... futhermore, even one version behind, 0.14.0, was released on 2025-03-05, even it wasn't in 2024. I have no clue what is up with this requirement, but for now with this fix capy seems to work just fine. I built a few examples just to check.