yaookctl: 0-unstable-2026-01-13 -> 0-unstable-2026-02-05

[r-ryantm]

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

meta.description for yaookctl is: Toolbox for interacting with Yaook clusters

meta.homepage for yaookctl is: https://gitlab.com/yaook/yaookctl

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 0-unstable-2026-02-05 in filename of file in /nix/store/06qz3sh13v35lks17gcyv5kp3sjbqgq4-yaookctl-0-unstable-2026-02-05

---

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

yaookctl

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/06qz3sh13v35lks17gcyv5kp3sjbqgq4-yaookctl-0-unstable-2026-02-05 \
  --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 yaookctl https://github.com/r-ryantm/nixpkgs/archive/10eea93870ba579ec18b4ff6461c55806a23820e.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/10eea93870ba579ec18b4ff6461c55806a23820e#yaookctl

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

ls -la /nix/store/06qz3sh13v35lks17gcyv5kp3sjbqgq4-yaookctl-0-unstable-2026-02-05
ls -la /nix/store/06qz3sh13v35lks17gcyv5kp3sjbqgq4-yaookctl-0-unstable-2026-02-05/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: 10eea93870ba579ec18b4ff6461c55806a23820e

---

x86_64-linux

✅ 2 packages built:

• yaookctl
• yaookctl.dist

---

Maintainer pings

cc @Lykos153 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.

[Lykos153]

@NixOS/nixpkgs-merge-bot merge

[nixpkgs-ci]

@Lykos153 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.
• ✅ Lykos153 is a member of @NixOS/nixpkgs-maintainers.
• ✅ Lykos153 is a maintainer of all touched packages.

✔️ Queued for merge (#306934)