Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: fosrl-gerbil 1.4.0 -> 1.4.1 https://github.com/fosrl/gerbil/releases
attrpath: fosrl-gerbil
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-k5G8mkqrezRYY2lH1kbMMcW8GsUkyDaPglLEAzJIxYo="
[golangModuleVersion] Replaced vendorHash with sha256-S5olgsmX0uZR9P/u/8Rf3lzRCSIwPDcmlvSzJhhJM3w=
[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/fo/fosrl-gerbil/package.nix b/pkgs/by-name/fo/fosrl-gerbil/package.nix
index 6795a2c62b3e..e602d599da8a 100644
--- a/pkgs/by-name/fo/fosrl-gerbil/package.nix
+++ b/pkgs/by-name/fo/fosrl-gerbil/package.nix
@@ -7,16 +7,16 @@
buildGoModule (finalAttrs: {
pname = "gerbil";
- version = "1.4.0";
+ version = "1.4.1";
src = fetchFromGitHub {
owner = "fosrl";
repo = "gerbil";
tag = finalAttrs.version;
- hash = "sha256-SKpXWlpMkmo5Qwdi/MylqNIBvP4jEHSZfP5BjQD1nVs=";
+ hash = "sha256-wKqJfiCzmMbKZXJGB7BWoXRNDukc4t+PX60XyynJNAU=";
};
- vendorHash = "sha256-k5G8mkqrezRYY2lH1kbMMcW8GsUkyDaPglLEAzJIxYo=";
+ vendorHash = "sha256-S5olgsmX0uZR9P/u/8Rf3lzRCSIwPDcmlvSzJhhJM3w=";
# patch out the /usr/sbin/iptables
postPatch = ''
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: `1a5525f304079040a91cc1a3f0782eafa033456f`
---
### `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/fosrl/gerbil/releases.
meta.description for fosrl-gerbil is: Simple WireGuard interface management server
meta.homepage for fosrl-gerbil is: https://github.com/fosrl/gerbil
meta.changelog for fosrl-gerbil is: https://github.com/fosrl/gerbil/releases/tag/1.4.1
###### Updates performed
- Golang update
###### To inspect upstream changes
###### Impact
Checks done
---
- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 1.4.1 with grep in /nix/store/mswyxwlbkraf516ggnn4nmvcjggnsvfp-gerbil-1.4.1
- found 1.4.1 in filename of file in /nix/store/mswyxwlbkraf516ggnn4nmvcjggnsvfp-gerbil-1.4.1
---
Rebuild report (if merged into master) (click to expand)
```
2 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
fosrl-gerbil
```
Instructions to test this update (click to expand)
---
Either **download from the cache**:
```
nix-store -r /nix/store/mswyxwlbkraf516ggnn4nmvcjggnsvfp-gerbil-1.4.1 \
--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 fosrl-gerbil https://github.com/r-ryantm/nixpkgs/archive/1a5525f304079040a91cc1a3f0782eafa033456f.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/1a5525f304079040a91cc1a3f0782eafa033456f#fosrl-gerbil
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/mswyxwlbkraf516ggnn4nmvcjggnsvfp-gerbil-1.4.1
ls -la /nix/store/mswyxwlbkraf516ggnn4nmvcjggnsvfp-gerbil-1.4.1/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: `1a5525f304079040a91cc1a3f0782eafa033456f`
---
### `x86_64-linux`
:white_check_mark: 1 package built:
---
###### Maintainer pings
cc @jackrosenberg @water-sucks 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/528127