Update Nixpkgs version to 26.05#2457
Open
aidenfoxivey wants to merge 1 commit into
Open
Conversation
https://nixos.org/blog/announcements/2026/nixos-2605/ Signed-off-by: Aiden Fox Ivey <aiden@aidenfoxivey.com>
Contributor
Author
|
|
Contributor
Author
|
Failure seems unrelated to PR: |
baentsch
approved these changes
Jun 6, 2026
baentsch
left a comment
Member
There was a problem hiding this comment.
LGTM. Failure due to apparent new restriction at Intel download sites --> If re-occurring, download Intel files, drop CI step, or re-design the test.
Contributor
Author
|
Unrelated to this, but I have the S390X and PPC64LE self hosting CI PR in the works. I am sincerely sorry about the delay. |
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.
As NixOS's underlying package repository Nixpkgs has been updated from version 25.05 to 26.05, the pin in
liboqs's flake should be updated correspondingly.https://nixos.org/blog/announcements/2026/nixos-2605/
Does this PR change the input/output behaviour of a cryptographic algorithm (i.e., does it change known answer test values)? (If so, a version bump will be required from x.y.z to x.(y+1).0.)
No.
Does this PR change the list of algorithms available -- either adding, removing, or renaming? Does this PR otherwise change an API? (If so, PRs in fully supported downstream projects dependent on these, i.e., oqs-provider will also need to be ready for review and merge by the time this is merged. Also, make sure to update the list of algorithms in the continuous benchmarking files: .github/workflows/kem-bench.yml and sig-bench.yml)
No.