-
-
Notifications
You must be signed in to change notification settings - Fork 17.7k
gomtree: 0.6.0 -> 0.7.0 #478272
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
gomtree: 0.6.0 -> 0.7.0 #478272
Conversation
|
phanirithvij
left a comment
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.
lgtm
|
@NixOS/nixpkgs-merge-bot merge |
|
@phanirithvij wants to merge this PR. Requirements to merge this PR with
|
|
Successfully created backport PR for |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/vbatts/go-mtree/releases.
meta.description for gomtree is: File systems verification utility and library, in likeness of mtree(8)
meta.homepage for gomtree is: https://github.com/vbatts/go-mtree
meta.changelog for gomtree is: https://github.com/vbatts/go-mtree/releases/tag/v0.7.0
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
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-review --extra-nixpkgs-config '{ allowBroken = false; }'Commit:
1c215329d41aa1608c1e8733eeededd3ab70b8ccx86_64-linux✅ 1 package built:
Maintainer pings
cc @phanirithvij 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.