Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: frr 10.6.0 -> 10.6.1 https://github.com/FRRouting/frr/releases
attrpath: frr
Checking auto update branch...
No auto update branch exists
[version] 
[version] updated version and sha256
[rustCrateVersion] 
[rustCrateVersion] No cargoHash found
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorHash
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] skipping because derivation has no updateScript
Diff after rewrites:
diff --git a/pkgs/by-name/fr/frr/package.nix b/pkgs/by-name/fr/frr/package.nix
index bd0dd47c3d2a..f3caad2e61d6 100644
--- a/pkgs/by-name/fr/frr/package.nix
+++ b/pkgs/by-name/fr/frr/package.nix
@@ -81,13 +81,13 @@
 
 stdenv.mkDerivation (finalAttrs: {
   pname = "frr";
-  version = "10.6.0";
+  version = "10.6.1";
 
   src = fetchFromGitHub {
     owner = "FRRouting";
     repo = "frr";
     rev = "frr-${finalAttrs.version}";
-    hash = "sha256-o0h9adGvb9FEcAMYrjrjTb7MMozdXriOsK6fE0fGjss=";
+    hash = "sha256-sSvw9tfVNUyQjEOELoUAIQkEvXg765MsWvVKM0gsYUc=";
   };
 
   # Without the std explicitly set, we may run into abseil-cpp

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: `82c0c2cea4d63df222c68a63666ed9eaa221b593`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 1 package built:</summary>
  <ul>
    <li>frr</li>
  </ul>
</details>

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/FRRouting/frr/releases.

meta.description for frr is: FRR BGP/OSPF/ISIS/RIP/RIPNG routing daemon suite

meta.homepage for frr is: https://frrouting.org/




###### Updates performed
- Version update

###### To inspect upstream changes

- [Release on GitHub](https://github.com/FRRouting/frr/releases/tag/frr-10.6.1)

- [Compare changes on GitHub](https://github.com/FRRouting/frr/compare/frr-10.6.0...frr-10.6.1)

###### Impact

<b>Checks done</b>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 10.6.1 with grep in /nix/store/9sx5dwcnh8a4glcf2w784zpvpp41y8w9-frr-10.6.1
- found 10.6.1 in filename of file in /nix/store/9sx5dwcnh8a4glcf2w784zpvpp41y8w9-frr-10.6.1

---

<details>
<summary>
<b>Rebuild report</b> (if merged into master) (click to expand)
</summary>

```
2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

frr
```

</details>

<details>
<summary>
<b>Instructions to test this update</b> (click to expand)
</summary>

---

Either **download from the cache**:
```
nix-store -r /nix/store/9sx5dwcnh8a4glcf2w784zpvpp41y8w9-frr-10.6.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 frr https://github.com/r-ryantm/nixpkgs/archive/82c0c2cea4d63df222c68a63666ed9eaa221b593.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/82c0c2cea4d63df222c68a63666ed9eaa221b593#frr
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/9sx5dwcnh8a4glcf2w784zpvpp41y8w9-frr-10.6.1
ls -la /nix/store/9sx5dwcnh8a4glcf2w784zpvpp41y8w9-frr-10.6.1/bin
```

---

</details>
<br/>



### 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: `82c0c2cea4d63df222c68a63666ed9eaa221b593`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 1 package built:</summary>
  <ul>
    <li>frr</li>
  </ul>
</details>

---

###### Maintainer pings

cc @woffs @thillux 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/515300