frr: 10.6.1 -> 10.7.0

[r-ryantm]

Automatic update generated by 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

• Compare changes on GitHub

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 10.7.0 with grep in /nix/store/585c3mr8inyfq2mh16bwwa47s1mzxmvf-frr-10.7.0
• found 10.7.0 in filename of file in /nix/store/585c3mr8inyfq2mh16bwwa47s1mzxmvf-frr-10.7.0

---

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

frr

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/585c3mr8inyfq2mh16bwwa47s1mzxmvf-frr-10.7.0 \
  --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/428927359e184ec3b37172f193d48e5b3fe72802.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/428927359e184ec3b37172f193d48e5b3fe72802#frr

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/585c3mr8inyfq2mh16bwwa47s1mzxmvf-frr-10.7.0
ls -la /nix/store/585c3mr8inyfq2mh16bwwa47s1mzxmvf-frr-10.7.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.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'
Commit: 428927359e184ec3b37172f193d48e5b3fe72802

---

x86_64-linux

✅ 1 package built:

• frr

---

Maintainer pings

cc @woffs @thillux for testing.

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.

[thillux]

@NixOS/nixpkgs-merge-bot merge

[nixpkgs-ci]

@thillux wants to merge this PR.

Requirements to merge this PR with @NixOS/nixpkgs-merge-bot merge:

• ✅ PR targets a development branch.
• ✅ PR touches only files of packages in pkgs/by-name/.
• ✅ PR is at least one of:
  • ⬜ Approved by a committer.
  • ⬜ Backported via label.
  • ⬜ Opened by a committer.
  • ✅ Opened by @r-ryantm.
• ✅ PR is not a draft
• ✅ PR is not blocked by a "changes requested" review from a committer.
• ✅ thillux is a member of @NixOS/nixpkgs-maintainers.
• ✅ thillux is a maintainer of all touched packages on the master branch.

✔️ Queued for merge (#306934)

[LeSuisse]

This includes the fix for #505331 / CVE-2026-5107. Is this something acceptable to backport?