garnet: 1.1.6 -> 1.1.9

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for garnet is: Remote cache-store from Microsoft Research

meta.homepage for garnet is: https://microsoft.github.io/garnet/

meta.changelog for garnet is: https://github.com/microsoft/garnet/releases/tag/v1.1.9

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 1.1.9 with grep in /nix/store/phdg2j1k4k86wlmnff2c2j4wzlgklrma-garnet-1.1.9
• found 1.1.9 in filename of file in /nix/store/phdg2j1k4k86wlmnff2c2j4wzlgklrma-garnet-1.1.9

---

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

garnet

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/phdg2j1k4k86wlmnff2c2j4wzlgklrma-garnet-1.1.9 \
  --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 garnet https://github.com/r-ryantm/nixpkgs/archive/0deb8382a832362ed85b2123eb6908f8a86fc508.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/0deb8382a832362ed85b2123eb6908f8a86fc508#garnet

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/phdg2j1k4k86wlmnff2c2j4wzlgklrma-garnet-1.1.9
ls -la /nix/store/phdg2j1k4k86wlmnff2c2j4wzlgklrma-garnet-1.1.9/bin

---

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.

Command: nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'
Commit: 0deb8382a832362ed85b2123eb6908f8a86fc508

---

x86_64-linux

✅ 1 package built:

• garnet

---

Maintainer pings

cc @getchoo @Hythera for testing.

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.

[Hythera]

diff: microsoft/garnet@v1.1.6...v1.1.9

Seems like nixpkgs-review-gha got stuck. Changes are very minimal.

@NixOS/nixpkgs-merge-bot merge

[nixpkgs-ci]

@Hythera wants to merge this PR.

Requirements to merge this PR with @NixOS/nixpkgs-merge-bot merge:

• ✅ PR targets a development branch.
• ✅ PR touches only files of packages in pkgs/by-name/.
• ✅ PR is at least one of:
  • ⬜ Approved by a committer.
  • ⬜ Backported via label.
  • ⬜ Opened by a committer.
  • ✅ Opened by @r-ryantm.
• ✅ PR is not a draft
• ✅ Hythera is a member of @NixOS/nixpkgs-maintainers.
• ✅ Hythera is a maintainer of all touched packages on the master branch.

✔️ Queued for merge (#306934)

[nixpkgs-ci]

Successfully created backport PR for release-26.05:

• [Backport release-26.05] garnet: 1.1.6 -> 1.1.9 #523976