Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: firewalld 2.4.3 -> 2.5.0 https://github.com/firewalld/firewalld/releases
attrpath: firewalld
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/fi/firewalld/package.nix b/pkgs/by-name/fi/firewalld/package.nix
index 646eae599f4e..9d2feb3d738b 100644
--- a/pkgs/by-name/fi/firewalld/package.nix
+++ b/pkgs/by-name/fi/firewalld/package.nix
@@ -43,7 +43,7 @@ let
 in
 stdenv.mkDerivation (finalAttrs: {
   pname = "firewalld";
-  version = "2.4.3";
+  version = "2.5.0";
 
   __structuredAttrs = true;
   strictDeps = true;
@@ -52,7 +52,7 @@ stdenv.mkDerivation (finalAttrs: {
     owner = "firewalld";
     repo = "firewalld";
     tag = "v${finalAttrs.version}";
-    hash = "sha256-S7E0szAZ2MEttL4PdBkoOcDGFVCVrwsTKr9xe+DPPgM=";
+    hash = "sha256-d/mKBkyi9f1/FpD5ECnvC0R/WCtfq6ewWu8kFs6sG9o=";
   };
 
   patches = [

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: `c3bf2b13c2cd5c375895a78cad917c6896b0e574`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 2 packages built:</summary>
  <ul>
    <li>firewalld</li>
    <li>firewalld-gui</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/firewalld/firewalld/releases.

meta.description for firewalld is: Firewall daemon with D-Bus interface

meta.homepage for firewalld is: https://firewalld.org




###### Updates performed
- Version update

###### To inspect upstream changes





###### Impact

<b>Checks done</b>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 2.5.0 with grep in /nix/store/5if4d8gngr9g0q0xs1sb6vxx5mgd8yc8-firewalld-2.5.0
- found 2.5.0 in filename of file in /nix/store/5if4d8gngr9g0q0xs1sb6vxx5mgd8yc8-firewalld-2.5.0

---

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

```
5 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

firewalld
firewalld-gui
```

</details>

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

---

Either **download from the cache**:
```
nix-store -r /nix/store/5if4d8gngr9g0q0xs1sb6vxx5mgd8yc8-firewalld-2.5.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 firewalld https://github.com/r-ryantm/nixpkgs/archive/c3bf2b13c2cd5c375895a78cad917c6896b0e574.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/c3bf2b13c2cd5c375895a78cad917c6896b0e574#firewalld
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/5if4d8gngr9g0q0xs1sb6vxx5mgd8yc8-firewalld-2.5.0
ls -la /nix/store/5if4d8gngr9g0q0xs1sb6vxx5mgd8yc8-firewalld-2.5.0/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: `c3bf2b13c2cd5c375895a78cad917c6896b0e574`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 2 packages built:</summary>
  <ul>
    <li>firewalld</li>
    <li>firewalld-gui</li>
  </ul>
</details>

---

###### Maintainer pings

cc @Prince213 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/539796