-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
ostree: 2025.2 -> 2025.4 #426555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
ostree: 2025.2 -> 2025.4 #426555
Conversation
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ostreedev/ostree/releases. meta.description for ostree is: Git for operating system binaries meta.homepage for ostree is: https://ostreedev.github.io/ostree/ Updates performed
To inspect upstream changesImpactChecks done
Caution A test defined in
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.
|
db29b3a
to
88d4e93
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
passthru tests are failing, going to ping maintainers of some reverse dependencies
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ostreedev/ostree/releases.
meta.description for ostree is: Git for operating system binaries
meta.homepage for ostree is: https://ostreedev.github.io/ostree/
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done
Caution
A test defined in
passthru.tests
did not pass.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.)
For the cached download to work, your user must be in the
trusted-users
list or you can usesudo
since 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-review
resultGenerated using
nixpkgs-review
.Command:
nixpkgs-review
x86_64-linux
⏩ 2 packages marked as broken and skipped:
✅ 64 packages built:
Maintainer pings
Tip
As a maintainer, if your package is located under
pkgs/by-name/*
, you can comment@NixOS/nixpkgs-merge-bot merge
to automatically merge this update using thenixpkgs-merge-bot
.Closes #426556
Add a 👍 reaction to pull requests you find important.