2022-10-28T19:52:44 hyperrogue 12.1a -> 12.1d https://github.com/zenorogue/hyperrogue/releases 2022-10-28T19:52:46 attrpath: hyperrogue 2022-10-28T19:52:46 Checking auto update branch... 2022-10-28T19:52:46 An auto update branch exists with message `hyperrogue: 12.1a -> 12.1b`. New version is 12.1d. 2022-10-28T19:52:46 The auto update branch does not match or exceed the new version. 2022-10-28T19:52:50 [version] 2022-10-28T19:52:58 [version] updated version and sha256 2022-10-28T19:52:58 [rustCrateVersion] 2022-10-28T19:52:58 [rustCrateVersion] No cargoSha256 found 2022-10-28T19:52:58 [golangModuleVersion] 2022-10-28T19:52:58 [golangModuleVersion] Not a buildGoModule package with vendorSha256 2022-10-28T19:52:58 [updateScript] 2022-10-28T19:52:58 [updateScript] skipping because derivation has no updateScript 2022-10-28T19:52:58 2022-10-28T19:52:58 [quotedUrls] 2022-10-28T19:52:58 [quotedUrls] nothing found to replace 2022-10-28T19:52:59 Diff after rewrites: diff --git a/pkgs/games/hyperrogue/default.nix b/pkgs/games/hyperrogue/default.nix index 2370b008225..26a2de22479 100644 --- a/pkgs/games/hyperrogue/default.nix +++ b/pkgs/games/hyperrogue/default.nix @@ -3,13 +3,13 @@ stdenv.mkDerivation rec { pname = "hyperrogue"; - version = "12.1a"; + version = "12.1d"; src = fetchFromGitHub { owner = "zenorogue"; repo = "hyperrogue"; rev = "v${version}"; - sha256 = "sha256-VmWZkIjDy/yv0g9YCW9x8b0LE5guHIA/KZc3OXJoCdA="; + sha256 = "sha256-jKGdQwctPJ5zRqN7NwQPAzptpe6AMDFR6Eh6PmD/3jc="; }; CXXFLAGS = [ 2022-10-28T19:57:46 Successfully finished processing 2022-10-28T19:57:46 cachix "/nix/store/jgdxr8d035w3801n6k0zq113jj2mbpnd-hyperrogue-12.1d" 2022-10-28T19:58:21 [check][nixpkgs-review] 2022-10-28T20:01:24 Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package built:
2022-10-28T20:01:28 Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://github.com/zenorogue/hyperrogue/releases. meta.description for hyperrogue is: "A roguelike game set in hyperbolic geometry" meta.homepage for hyperrogue is: "http://www.roguetemple.com/z/hyper/" meta.changelog for hyperrogue is: "" ###### Updates performed - Version update ###### To inspect upstream changes - [Release on GitHub](https://github.com/zenorogue/hyperrogue/releases/tag/v12.1d) - [Compare changes on GitHub](https://github.com/zenorogue/hyperrogue/compare/v12.1a...v12.1d) ###### Impact
Checks done (click to expand) --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 12.1d with grep in /nix/store/jgdxr8d035w3801n6k0zq113jj2mbpnd-hyperrogue-12.1d - found 12.1d in filename of file in /nix/store/jgdxr8d035w3801n6k0zq113jj2mbpnd-hyperrogue-12.1d ---
Rebuild report (if merged into master) (click to expand) ``` 1 total rebuild path(s) 1 package rebuild(s) First fifty rebuilds by attrpath hyperrogue ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/jgdxr8d035w3801n6k0zq113jj2mbpnd-hyperrogue-12.1d \ --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \ --option trusted-public-keys ' nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (The Cachix cache is only trusted for this store-path realization.) For the Cachix download to work, your user must be in the `trusted-users` list or you can use `sudo` since root is effectively trusted. Or, **build yourself**: ``` nix-build -A hyperrogue https://github.com/r-ryantm/nixpkgs/archive/dff76979acaca16920e130645eb3a0c14486df59.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/jgdxr8d035w3801n6k0zq113jj2mbpnd-hyperrogue-12.1d ls -la /nix/store/jgdxr8d035w3801n6k0zq113jj2mbpnd-hyperrogue-12.1d/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. Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package built:
--- ###### Maintainer pings cc @rardiol for [testing](https://github.com/ryantm/nixpkgs-update/blob/master/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do). 2022-10-28T20:01:30 Updated existing PR 2022-10-28T20:01:30 https://api.github.com/repos/NixOS/nixpkgs/pulls/194967