openvswitch 0 -> 1
attrpath: openvswitch
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:
 - openvswitch-3.2.2

Press Enter key to continue...
Running update for:
 - openvswitch-3.2.2: UPDATING ...
 - openvswitch-3.2.2: DONE.

Packages updated!

Diff after rewrites:
diff --git a/pkgs/os-specific/linux/openvswitch/default.nix b/pkgs/os-specific/linux/openvswitch/default.nix
index 89149027d3b8..0ea5b6391605 100644
--- a/pkgs/os-specific/linux/openvswitch/default.nix
+++ b/pkgs/os-specific/linux/openvswitch/default.nix
@@ -1,4 +1,4 @@
 import ./generic.nix {
-  version = "3.2.2";
-  hash = "sha256-BCesNAYE3RyxfBAzK2/6+PcV1W+1ZEZQKVSLSq/pWC8=";
+  version = "3.3.0";
+  hash = "sha256-Gvy4H7lHwL6IWGaZXWwIjmHfQ1YRFXiSBqKzP3vBsF8=";
 }

No auto update branch exists
Successfully finished processing
cachix "/nix/store/0rw149478l1wn7ihpnq9xd02fz9qr5vb-openvswitch-3.3.0"
[check][nixpkgs-review]
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>2 packages built:</summary>
  <ul>
    <li>openvswitch</li>
    <li>pipework</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 openvswitch is: A multilayer virtual switch

meta.homepage for openvswitch is: https://www.openvswitch.org/

meta.changelog for openvswitch is: https://www.openvswitch.org/releases/NEWS-3.3.0.txt


###### 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 3.3.0 with grep in /nix/store/0rw149478l1wn7ihpnq9xd02fz9qr5vb-openvswitch-3.3.0
- found 3.3.0 in filename of file in /nix/store/0rw149478l1wn7ihpnq9xd02fz9qr5vb-openvswitch-3.3.0

---

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

```
21 total rebuild path(s)

21 package rebuild(s)

First fifty rebuilds by attrpath
libvmi
openvswitch
pipework
qemu_xen
qemu_xen-light
qemu_xen_4_15
qemu_xen_4_15-light
qubes-core-vchan-xen
xen
xen-guest-agent
xen-light
xen-slim
xenPackages.xen-light
xenPackages.xen-slim
xenPackages.xen-vanilla
xenPackages.xen_4_15-light
xenPackages.xen_4_15-slim
xenPackages.xen_4_15-vanilla
xen_4_15
xen_4_15-light
xen_4_15-slim
```

</details>

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

---

Either **download from Cachix**:
```
nix-store -r /nix/store/0rw149478l1wn7ihpnq9xd02fz9qr5vb-openvswitch-3.3.0 \
  --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 openvswitch https://github.com/r-ryantm/nixpkgs/archive/7ade924af4a96e0632165b219f7e236712516282.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/7ade924af4a96e0632165b219f7e236712516282#openvswitch
```

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

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

---

###### Maintainer pings

cc @netixx @kmcopper for [testing](https://github.com/ryantm/nixpkgs-update/blob/master/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do).
https://api.github.com/repos/NixOS/nixpkgs/pulls/289696