Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: deterministic-zip 6.0.2 -> 6.0.3 https://github.com/timo-reymann/deterministic-zip/releases attrpath: deterministic-zip Checking auto update branch... No auto update branch exists [version] [version] generic version rewriter does not support multiple hashes [rustCrateVersion] [rustCrateVersion] No cargoHash found [golangModuleVersion] [golangModuleVersion] Found old vendorHash = "sha256-hEPZrS2D6YqlaaJXF8uyt+fJ38Adi3WvOq7v9dZuovI=" [golangModuleVersion] Replaced vendorHash with sha256-hEPZrS2D6YqlaaJXF8uyt+fJ38Adi3WvOq7v9dZuovI= [golangModuleVersion] Finished updating vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] skipping because derivation has no updateScript Diff after rewrites: diff --git a/pkgs/by-name/de/deterministic-zip/package.nix b/pkgs/by-name/de/deterministic-zip/package.nix index b529cc49014a..a7e23a4ef569 100644 --- a/pkgs/by-name/de/deterministic-zip/package.nix +++ b/pkgs/by-name/de/deterministic-zip/package.nix @@ -6,13 +6,13 @@ }: buildGoModule (finalAttrs: { pname = "deterministic-zip"; - version = "6.0.2"; + version = "6.0.3"; src = fetchFromGitHub { owner = "timo-reymann"; repo = "deterministic-zip"; tag = finalAttrs.version; - hash = "sha256-yuwy3t2iWBXBwsj0Psy4/1YJ/V/vuNiBVzYzGQXUnkA="; + hash = "sha256-YQCJ2nAE9/wt+KiU2eXdGXVxFiHZzBMyNX+1sSPtxt4="; }; vendorHash = "sha256-hEPZrS2D6YqlaaJXF8uyt+fJ38Adi3WvOq7v9dZuovI="; Successfully finished processing [check][nixpkgs-review] ## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `93e98cb2a0c329d2f61c3822498ac7143c3ec8b8` --- ### `x86_64-linux`
:white_check_mark: 1 package built:
Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from https://github.com/timo-reymann/deterministic-zip/releases. meta.description for deterministic-zip is: Simple (almost drop-in) replacement for zip that produces deterministic files meta.homepage for deterministic-zip is: https://github.com/timo-reymann/deterministic-zip ###### Updates performed - Golang update ###### To inspect upstream changes ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 6.0.3 with grep in /nix/store/2ii9c3hkqlrfaw6r92mlafnsvvwjzl5h-deterministic-zip-6.0.3 - found 6.0.3 in filename of file in /nix/store/2ii9c3hkqlrfaw6r92mlafnsvvwjzl5h-deterministic-zip-6.0.3 ---
Rebuild report (if merged into master) (click to expand) ``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath deterministic-zip ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/2ii9c3hkqlrfaw6r92mlafnsvvwjzl5h-deterministic-zip-6.0.3 \ --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \ --option trusted-public-keys ' nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (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-users` list or you can use `sudo` since root is effectively trusted. Or, **build yourself**: ``` nix-build -A deterministic-zip https://github.com/r-ryantm/nixpkgs/archive/93e98cb2a0c329d2f61c3822498ac7143c3ec8b8.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/93e98cb2a0c329d2f61c3822498ac7143c3ec8b8#deterministic-zip ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/2ii9c3hkqlrfaw6r92mlafnsvvwjzl5h-deterministic-zip-6.0.3 ls -la /nix/store/2ii9c3hkqlrfaw6r92mlafnsvvwjzl5h-deterministic-zip-6.0.3/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` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `93e98cb2a0c329d2f61c3822498ac7143c3ec8b8` --- ### `x86_64-linux`
:white_check_mark: 1 package built:
--- ###### Maintainer pings cc @rhysmdnz for [testing](https://github.com/nix-community/nixpkgs-update/blob/main/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do). > [!TIP] > As a maintainer, if your package is located under `pkgs/by-name/*`, you can comment **`@NixOS/nixpkgs-merge-bot merge`** to automatically merge this update using the [`nixpkgs-merge-bot`](https://github.com/NixOS/nixpkgs/blob/master/ci/README.md#nixpkgs-merge-bot). https://api.github.com/repos/NixOS/nixpkgs/pulls/504554