ovn-lts 0 -> 1
attrpath: ovn-lts
Checking auto update branch...
[version] 
[version] skipping because derivation has updateScript
[rustCrateVersion] 
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] Success
[updateScript] 
Going to be running update for following packages:
 - ovn-24.03.2

Press Enter key to continue...
Running update for:
 - ovn-24.03.2: UPDATING ...
 - ovn-24.03.2: DONE.

Packages updated!

Diff after rewrites:
diff --git a/pkgs/by-name/ov/ovn/lts.nix b/pkgs/by-name/ov/ovn/lts.nix
index 42ab99ff7cc0..0d2b02dfc64e 100644
--- a/pkgs/by-name/ov/ovn/lts.nix
+++ b/pkgs/by-name/ov/ovn/lts.nix
@@ -1,5 +1,5 @@
 import ./generic.nix {
-  version = "24.03.2";
-  hash = "sha256-pO37MfmvlSd/bU9cGngFEJLnXtZFTqyz1zcYLvFLrrQ=";
+  version = "24.03.3";
+  hash = "sha256-W25Tq5Z7SYIBkq6doNz9WPiPsdDhnbys03rmF4m02eM=";
   updateScriptArgs = "--lts=true --regex '24.03.*'";
 }

No auto update branch exists
Successfully finished processing
cachix "/nix/store/hlmjhan81yvzsl99hdgjscv3lz1c5wbm-ovn-24.03.3"
[check][nixpkgs-review]
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>ovn-lts</li>
  </ul>
</details>

Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from passthru.updateScript.


meta.description for ovn-lts is: Open Virtual Network

meta.homepage for ovn-lts is: https://github.com/ovn-org/ovn

meta.changelog for ovn-lts is: https://github.com/ovn-org/ovn/blob/refs/tags/v24.03.3/NEWS


###### Updates performed
- Ran passthru.UpdateScript

###### To inspect upstream changes





###### Impact

<b>Checks done</b>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 24.03.3 with grep in /nix/store/hlmjhan81yvzsl99hdgjscv3lz1c5wbm-ovn-24.03.3
- found 24.03.3 in filename of file in /nix/store/hlmjhan81yvzsl99hdgjscv3lz1c5wbm-ovn-24.03.3

---

<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

ovn-lts
```

</details>

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

---

Either **download from Cachix**:
```
nix-store -r /nix/store/hlmjhan81yvzsl99hdgjscv3lz1c5wbm-ovn-24.03.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '
```
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix 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 ovn-lts https://github.com/r-ryantm/nixpkgs/archive/77805c3f4064dd9d6c42545add7d33102ffcb0ef.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/77805c3f4064dd9d6c42545add7d33102ffcb0ef#ovn-lts
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/hlmjhan81yvzsl99hdgjscv3lz1c5wbm-ovn-24.03.3
ls -la /nix/store/hlmjhan81yvzsl99hdgjscv3lz1c5wbm-ovn-24.03.3/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.

Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>ovn-lts</li>
  </ul>
</details>

---

###### Maintainer pings

cc @adamcstephens for [testing](https://github.com/ryantm/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-merge-bot).

---

Add a :+1: [reaction] to [pull requests you find important].

[reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/
[pull requests you find important]: https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+sort%3Areactions-%2B1-desc
https://api.github.com/repos/NixOS/nixpkgs/pulls/336782