glusterfs 11.0 -> 11.1 https://repology.org/project/glusterfs/versions
attrpath: glusterfs
Checking auto update branch...
No auto update branch exists
[version] 
[version] updated version and sha256
[rustCrateVersion] 
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] skipping because derivation has no updateScript

[quotedUrls]
[quotedUrls] nothing found to replace
Diff after rewrites:
diff --git a/pkgs/tools/filesystems/glusterfs/default.nix b/pkgs/tools/filesystems/glusterfs/default.nix
index 431be3b79d77..f7e830f3211d 100644
--- a/pkgs/tools/filesystems/glusterfs/default.nix
+++ b/pkgs/tools/filesystems/glusterfs/default.nix
@@ -55,13 +55,13 @@ let
   ];
 in stdenv.mkDerivation rec {
   pname = "glusterfs";
-  version = "11.0";
+  version = "11.1";
 
   src = fetchFromGitHub {
     owner = "gluster";
     repo = pname;
     rev = "v${version}";
-    sha256 = "sha256-K2w8YqpoLzkzUuoOuI7itfC81sJPUf6elOL8LCrxKAI=";
+    sha256 = "sha256-ZClMfozeFO3266fkuCSV04QwpZaYa8B0uq2lTPEN2rQ=";
   };
   inherit buildInputs propagatedBuildInputs;
 

Successfully finished processing
cachix "/nix/store/0dk3l77fn1dh85blbcn3n4l6va9r2i9i-glusterfs-11.1"
[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>glusterfs</li>
    <li>qemu_full</li>
  </ul>
</details>

Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://repology.org/project/glusterfs/versions.


meta.description for glusterfs is: Distributed storage system

meta.homepage for glusterfs is: https://www.gluster.org




###### Updates performed
- Version update

###### To inspect upstream changes



- [Compare changes on GitHub](https://github.com/gluster/glusterfs/compare/v11.0...v11.1)

###### Impact

<details>
<summary>
<b>Checks done</b> (click to expand)
</summary>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 11.1 with grep in /nix/store/0dk3l77fn1dh85blbcn3n4l6va9r2i9i-glusterfs-11.1
- found 11.1 in filename of file in /nix/store/0dk3l77fn1dh85blbcn3n4l6va9r2i9i-glusterfs-11.1

---

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

```
14 total rebuild path(s)

14 package rebuild(s)

First fifty rebuilds by attrpath
glusterfs
libvmi
qemu_full
qemu_xen
qemu_xen_4_15
qubes-core-vchan-xen
xen
xen-slim
xenPackages.xen-slim
xenPackages.xen-vanilla
xenPackages.xen_4_15-slim
xenPackages.xen_4_15-vanilla
xen_4_15
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/0dk3l77fn1dh85blbcn3n4l6va9r2i9i-glusterfs-11.1 \
  --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 glusterfs https://github.com/r-ryantm/nixpkgs/archive/abb7876588ca0bd2619406601ba89ea717df6295.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/abb7876588ca0bd2619406601ba89ea717df6295#glusterfs
```

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

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

---

###### Maintainer pings

cc @7c6f434c 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/266199