fix(nix): pin dudumini to nixpkgs-26.05-darwin, keep dudupro on unstable#89
Closed
emaiax wants to merge 1 commit into
Closed
fix(nix): pin dudumini to nixpkgs-26.05-darwin, keep dudupro on unstable#89emaiax wants to merge 1 commit into
emaiax wants to merge 1 commit into
Conversation
nixpkgs-unstable dropped x86_64-darwin support as of the 26.11 cycle, breaking dudumini (Intel) builds. Add a second nixpkgs input tracking the 26.05-darwin branch (security fixes until end of 2026) and use nix-darwin's nixpkgs.source option to pin dudumini to it, while dudupro (Apple Silicon) keeps following nixpkgs-unstable as before.
2 tasks
emaiax
added a commit
that referenced
this pull request
Jul 13, 2026
nixpkgs-unstable dropped x86_64-darwin support in the 26.11 cycle, breaking every dudumini CI build. Per-host nixpkgs pinning was explored (see closed PR #89) but nix-darwin's own internal branch-match checks (documentation, darwin-uninstaller) fire from nested eval-config.nix calls that don't respect per-host overrides, making the mismatch unworkable without a matching second nix-darwin input. Decommissioning dudumini from CI for now; nix/hosts/dudumini.nix is left in place. Co-authored-by: Eduardo Maia <[email protected]>
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
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.
Summary
nixpkgs-unstabledropped x86_64-darwin support in the 26.11 cycle, which brokedudumini(Intel) CI builds in chore(deps): update dependencies #87.watchexec-2.5.1on aarch64-darwin (dudupro) — reproduced locally, not CI flakiness.nixpkgs-darwin-stableinput trackingnixpkgs-26.05-darwin(security fixes until end of 2026) and pinsduduminito it via nix-darwin'snixpkgs.sourceoption.duduprokeeps followingnixpkgs-unstableunchanged.Test plan
dudupro(Apple Silicon, matches local hardware): full localdarwin-rebuild build --flake .#duduprosucceeded.watchexec-2.5.1builds successfully onnixpkgs-26.05-darwinlocally (the linker crash from chore(deps): update dependencies #87 does not reproduce there).dudumini(Intel): could not be natively build/tested locally (no Intel hardware available) — needs CI on themacos-15-intelrunner to confirm. A local cross-arch (aarch64→x86_64) eval hit an unrelated pre-existing self-reference inmodules/core/nixpkgs.nix(permittedInsecurePackagesreferencingpkgs.arc-browser) that only manifests under cross-compilation bootstrap, not native eval — out of scope for this fix.Closes the broken-CI PR #87 (closed without merging; its dependency bump was reverted here in favor of this per-host pin).