ipxe: 1.21.1-unstable-2025-01-10 -> 1.21.1-unstable-2025-02-28#376533
ipxe: 1.21.1-unstable-2025-01-10 -> 1.21.1-unstable-2025-02-28#376533wegank merged 1 commit intoNixOS:masterfrom
Conversation
r-ryantm
force-pushed
the
auto-update/ipxe
branch
from
9b91df0 to
9f0ecf3
Compare
r-ryantm
changed the title
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript. meta.description for ipxe is: Network boot firmware meta.homepage for ipxe is: https://ipxe.org/ Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
github-actions
bot
added
10.rebuild-darwin: 0
r-ryantm
force-pushed
the
auto-update/ipxe
branch
from
9f0ecf3 to
1f2e7f4
Compare
r-ryantm
changed the title
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript. meta.description for ipxe is: Network boot firmware meta.homepage for ipxe is: https://ipxe.org/ Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
r-ryantm
changed the title
r-ryantm
force-pushed
the
auto-update/ipxe
branch
from
1f2e7f4 to
1c31280
Compare
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript. meta.description for ipxe is: Network boot firmware meta.homepage for ipxe is: https://ipxe.org/ Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
wegank
force-pushed
the
auto-update/ipxe
branch
from
1c31280 to
8343143
Compare
2 participants
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for ipxe is: Network boot firmware
meta.homepage for ipxe is: https://ipxe.org/
Updates performed
To inspect upstream changes
Impact
Checks done
passthru.tests, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from the cache:
(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the
trusted-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-reviewresultGenerated using
nixpkgs-review.Command:
nixpkgs-reviewx86_64-linux⏩ 1 package marked as broken and skipped:
❌ 3 packages failed to build:
✅ 66 packages built:
Maintainer pings
cc @SigmaSquadron for testing.
Tip
As a maintainer, if your package is located under
pkgs/by-name/*, you can comment@NixOS/nixpkgs-merge-bot mergeto automatically merge this update using thenixpkgs-merge-bot.Add a 👍 reaction to pull requests you find important.