glusterfs 10.1 -> 11.0 https://repology.org/metapackage/glusterfs/versions
attrpath: glusterfs
Checking auto update branch...
An auto update branch exists with message `glusterfs: 10.1 -> 10.2`. New version is 11.0.
The auto update branch does not match or exceed the new version.
[version] 
[version] updated version and sha256
[rustCrateVersion] 
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash
[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 a1d09df7e60..ccb771308e3 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 = "10.1";
+  version = "11.0";
 
   src = fetchFromGitHub {
     owner = "gluster";
     repo = pname;
     rev = "v${version}";
-    sha256 = "sha256-vVFC2kQNneaOwrezPehOX32dpJb88ZhGHBApEXc9MOg=";
+    sha256 = "sha256-K2w8YqpoLzkzUuoOuI7itfC81sJPUf6elOL8LCrxKAI=";
   };
   inherit buildInputs propagatedBuildInputs;
 
@@ -87,9 +87,9 @@ in stdenv.mkDerivation rec {
   '';
 
   # Note that the VERSION file is something that is present in release tarballs
-  # but not in git tags (at least not as of writing in v3.10.1).
+  # but not in git tags (at least not as of writing in v3.11.0).
   # That's why we have to create it.
-  # Without this, gluster (at least 3.10.1) will fail very late and cryptically,
+  # Without this, gluster (at least 3.11.0) will fail very late and cryptically,
   # for example when setting up geo-replication, with a message like
   #   Staging of operation 'Volume Geo-replication Create' failed on localhost : Unable to fetch master volume details. Please check the master cluster and master volume.
   # What happens here is that the gverify.sh script tries to compare the versions,
@@ -146,7 +146,7 @@ in stdenv.mkDerivation rec {
 
     # Note that we only wrap the symlinks in $out/bin, not the actual executable scripts in $out/libexec/glusterfs.
     # This is because those scripts use `__file__` in their program logic
-    # (see https://github.com/gluster/glusterfs/blob/v3.10.1/extras/cliutils/cliutils.py#L116)
+    # (see https://github.com/gluster/glusterfs/blob/v3.11.0/extras/cliutils/cliutils.py#L116)
     # which would break if we changed the file name (which is what `wrapProgram` does).
     # Luckily, `libexec` scripts are never supposed to be invoked straight from PATH,
     # instead they are invoked directly from `gluster` or `glusterd`, which is why it is

Received ExitFailure 1 when running
Raw command: /nix/store/3nqhcyc7vid1npgcd0m7arg5sn325nhz-nix-2.12.0/bin/nix-build --option sandbox true --arg config "{ allowBroken = true; allowUnfree = true; allowAliases = false; }" --arg overlays "[ ]" -A glusterfs
nix build failed.
got build log for 'glusterfs' from 'daemon'
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/yl1gpzvyh9d2sh19rrqp01p96vxva2nq-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
applying patch /nix/store/qnd2y2x2l43mny8bnsl61ffgsynrrrbk-ssl_cert_path.patch
patching file configure.ac
Hunk #1 FAILED at 766.
1 out of 1 hunk FAILED -- saving rejects to file configure.ac.rej