2022-11-04T08:22:19 highfive-mpi 2.4.1 -> 2.5.0 https://github.com/BlueBrain/HighFive/releases 2022-11-04T08:22:22 attrpath: highfive-mpi 2022-11-04T08:22:22 Checking auto update branch... 2022-11-04T08:22:22 No auto update branch exists 2022-11-04T08:22:27 [version] 2022-11-04T08:22:30 [version] updated version and sha256 2022-11-04T08:22:30 [rustCrateVersion] 2022-11-04T08:22:30 [rustCrateVersion] No cargoSha256 found 2022-11-04T08:22:30 [golangModuleVersion] 2022-11-04T08:22:30 [golangModuleVersion] Not a buildGoModule package with vendorSha256 2022-11-04T08:22:30 [updateScript] 2022-11-04T08:22:30 [updateScript] skipping because derivation has no updateScript 2022-11-04T08:22:30 2022-11-04T08:22:30 [quotedUrls] 2022-11-04T08:22:30 [quotedUrls] nothing found to replace 2022-11-04T08:22:31 Diff after rewrites: diff --git a/pkgs/development/libraries/highfive/default.nix b/pkgs/development/libraries/highfive/default.nix index 8d219b82e44..32c42769822 100644 --- a/pkgs/development/libraries/highfive/default.nix +++ b/pkgs/development/libraries/highfive/default.nix @@ -12,13 +12,13 @@ assert mpiSupport -> mpi != null; stdenv.mkDerivation rec { pname = "highfive${lib.optionalString mpiSupport "-mpi"}"; - version = "2.4.1"; + version = "2.5.0"; src = fetchFromGitHub { owner = "BlueBrain"; repo = "HighFive"; rev = "v${version}"; - sha256 = "sha256-P60S3UR8wC3BHxRiqFdSjn6Akvykud40g5yEko5dIjw="; + sha256 = "sha256-Ycpjs4a9bBgJMhJScYaIv3Qt336qTjIQgv+oS/keoTU="; }; nativeBuildInputs = [ cmake ]; 2022-11-04T08:24:22 Successfully finished processing 2022-11-04T08:24:22 cachix "/nix/store/kh1wjn68ai407lixzm8j6jys558wa0xk-highfive-mpi-2.5.0" 2022-11-04T08:24:26 [check][nixpkgs-review] 2022-11-04T08:27:33 Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
2 packages built:
2022-11-04T08:27:36 Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://github.com/BlueBrain/HighFive/releases. meta.description for highfive-mpi is: "Header-only C++ HDF5 interface" meta.homepage for highfive-mpi is: "https://bluebrain.github.io/HighFive/" meta.changelog for highfive-mpi is: "" ###### Updates performed - Version update ###### To inspect upstream changes - [Release on GitHub](https://github.com/BlueBrain/HighFive/releases/tag/v2.5.0) - [Compare changes on GitHub](https://github.com/BlueBrain/HighFive/compare/v2.4.1...v2.5.0) ###### Impact
Checks done (click to expand) --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 2.5.0 with grep in /nix/store/kh1wjn68ai407lixzm8j6jys558wa0xk-highfive-mpi-2.5.0 - found 2.5.0 in filename of file in /nix/store/kh1wjn68ai407lixzm8j6jys558wa0xk-highfive-mpi-2.5.0 ---
Rebuild report (if merged into master) (click to expand) ``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath highfive highfive-mpi ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/kh1wjn68ai407lixzm8j6jys558wa0xk-highfive-mpi-2.5.0 \ --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 highfive-mpi https://github.com/r-ryantm/nixpkgs/archive/c276b2a0b3eaa1f504766f0a4abfb320ead6d71c.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/kh1wjn68ai407lixzm8j6jys558wa0xk-highfive-mpi-2.5.0 ls -la /nix/store/kh1wjn68ai407lixzm8j6jys558wa0xk-highfive-mpi-2.5.0/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)
2 packages built:
--- ###### Maintainer pings cc @robertodr 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-11-04T08:27:37 https://api.github.com/repos/NixOS/nixpkgs/pulls/199482