We now have the bot: 1. Doing the automated upgrade (bump version, src, recomputing hash) 2. Doing a full nixpkgs-review reverse closure rebuild The next step for a human is to review the upstream changelog. Right now they have to find it manually, but if `meta.changelog` is set, this commit adds a link to it directly in the PR description . Resolves #44
1.7 KiB
Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://update-site.com.
meta.description for foobar is: "Foobar package description"
meta.homepage for foobar is: "https://foobar-homepage.com"
meta.changelog for foobar is: "https://foobar-homepage.com/changelog/v1.2.3"
Updates performed
- Version Update
- Other Update
To inspect upstream changes
Impact
Checks done (click to expand)
- built on NixOS
- Some other check
Rebuild report (if merged into master) (click to expand)
123 total rebuild path(s)
Instructions to test this update (click to expand)
nix-build -A foobar https://github.com/r-ryantm/nixpkgs/archive/af39cf77a0d42a4f6771043ec54221ed.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/some-hash-path
ls -la /nix/store/some-hash-path/bin
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 comment body
Maintainer pings
cc @maintainer1 for testing.