mirror of
https://github.com/ryantm/nixpkgs-update.git
synced 2024-09-11 13:57:20 +03:00
1. We should always use `~/.cache/nixpkgs`, since if we do it in PWD the hard resets risk blowing away user work! 2. Previously, we weren't fetching and resetting to up-to-date master, which meant cmds would fail if your nixpkgs checkout was stale. 3. Previously, we were ignoring the `--pr` option entirely. This fixes that bug by passing the bool into the UpdateEnv, and also cleans up the selected options in the logger so it's easier to see. 4. We were including the title PR twice, like this: https://github.com/NixOS/nixpkgs/pull/86624 There are still some issues and things to improve, but with this PR I've managed to get a working usage here: https://github.com/NixOS/nixpkgs/pull/86625
1.6 KiB
1.6 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"
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.