Skip to content

fix: cherry-pick upstream fix for bootOrder -> initialBootOrder usage#18

Open
Mic92 wants to merge 1 commit into
tiiuae:march-rebasefrom
Mic92:fix/use-initialBootOrder
Open

fix: cherry-pick upstream fix for bootOrder -> initialBootOrder usage#18
Mic92 wants to merge 1 commit into
tiiuae:march-rebasefrom
Mic92:fix/use-initialBootOrder

Conversation

@Mic92

@Mic92 Mic92 commented Mar 23, 2026

Copy link
Copy Markdown

Cherry-pick of upstream commit d537752 ("flash-script: Update usage of bootOrder -> intialBootOrder").

Commit c5cd5a0 renamed the option hardware.nvidia-jetpack.firmware.bootOrder to initialBootOrder and added a mkRenamedOptionModule compat alias, but forgot to update two usage sites in the implementation. This causes a trace warning on every evaluation:

trace: Obsolete option `hardware.nvidia-jetpack.firmware.bootOrder' is used.
It was renamed to `hardware.nvidia-jetpack.firmware.initialBootOrder'.

This was already fixed upstream in anduril/jetpack-nixos@d537752.

The xorg package set has been deprecated in nixpkgs. Replace all
xorg.libX11, xorg.libXext, xorg.libxcb, etc. references with their
new top-level names (libx11, libxext, libxcb, etc.) to silence
evaluation warnings like:

  evaluation warning: The xorg package set has been deprecated,
  'xorg.libX11' has been renamed to 'libx11'
@Mic92 Mic92 force-pushed the fix/use-initialBootOrder branch from 0889b7e to 9000095 Compare March 23, 2026 18:43
@Mic92 Mic92 changed the base branch from feb-rebase to march-rebase March 23, 2026 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant