Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: brook 20240606 -> 20270101 https://github.com/txthinking/brook/releases attrpath: brook 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-dYiifLUOq6RKAVSXuoGlok9Jp8jHmbXN/EjQeQpoqWw=" [golangModuleVersion] Replaced vendorHash with sha256-974jdNwpQbdTbYjY/6KaicwNclizeIQXfyMZI3v/9aA= [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/br/brook/package.nix b/pkgs/by-name/br/brook/package.nix index 7e8f9e8b7f6f..3bb8dce7ae04 100644 --- a/pkgs/by-name/br/brook/package.nix +++ b/pkgs/by-name/br/brook/package.nix @@ -6,16 +6,16 @@ buildGoModule (finalAttrs: { pname = "brook"; - version = "20240606"; + version = "20270101"; src = fetchFromGitHub { owner = "txthinking"; repo = "brook"; rev = "v${finalAttrs.version}"; - sha256 = "sha256-rfCqYI0T/nbK+rlPGl5orLo3qHKITesdFNtXc/ECATA="; + sha256 = "sha256-OIuEJFGOUkvHjxI4FPKWU65VFvgXG0+pu9giGJXYS0w="; }; - vendorHash = "sha256-dYiifLUOq6RKAVSXuoGlok9Jp8jHmbXN/EjQeQpoqWw="; + vendorHash = "sha256-974jdNwpQbdTbYjY/6KaicwNclizeIQXfyMZI3v/9aA="; meta = { homepage = "https://github.com/txthinking/brook"; 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: `34c9f04085cca7b1354a464efd1ee2ae5558724f` --- ### `x86_64-linux`
✅ 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/txthinking/brook/releases. meta.description for brook is: Cross-platform Proxy/VPN software meta.homepage for brook is: https://github.com/txthinking/brook ###### Updates performed - Golang update ###### To inspect upstream changes - [Release on GitHub](https://github.com/txthinking/brook/releases/tag/v20270101) - [Compare changes on GitHub](https://github.com/txthinking/brook/compare/v20240606...v20270101) ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 20270101 with grep in /nix/store/isdi1bkzy115kmz935d102f1q54fpyrk-brook-20270101 - found 20270101 in filename of file in /nix/store/isdi1bkzy115kmz935d102f1q54fpyrk-brook-20270101 ---
Rebuild report (if merged into master) (click to expand) ``` 8 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath brook ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/isdi1bkzy115kmz935d102f1q54fpyrk-brook-20270101 \ --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 brook https://github.com/r-ryantm/nixpkgs/archive/34c9f04085cca7b1354a464efd1ee2ae5558724f.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/34c9f04085cca7b1354a464efd1ee2ae5558724f#brook ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/isdi1bkzy115kmz935d102f1q54fpyrk-brook-20270101 ls -la /nix/store/isdi1bkzy115kmz935d102f1q54fpyrk-brook-20270101/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: `34c9f04085cca7b1354a464efd1ee2ae5558724f` --- ### `x86_64-linux`
✅ 1 package built:
--- ###### Maintainer pings cc @xrelkd 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/563847