bant: 0.2.1 -> 0.2.2

[r-ryantm]

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

meta.description for bant is: Bazel/Build Analysis and Navigation Tool

meta.homepage for bant is: http://bant.build/

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

• Release on GitHub

• Compare changes on GitHub

Impact

Checks done

---

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

---

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

bant

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/g0fr5jnjmx6z2s9g9gf1a7plmq3hsfzb-bant-0.2.2 \
  --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 bant https://github.com/r-ryantm/nixpkgs/archive/bd93e9a8a5d03cb861781ed94a4879a61c802321.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/bd93e9a8a5d03cb861781ed94a4879a61c802321#bant

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

ls -la /nix/store/g0fr5jnjmx6z2s9g9gf1a7plmq3hsfzb-bant-0.2.2
ls -la /nix/store/g0fr5jnjmx6z2s9g9gf1a7plmq3hsfzb-bant-0.2.2/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

---

x86_64-linux

✅ 1 package built:

• bant

---

Maintainer pings

cc @hzeller @lromor 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.

---

Add a 👍 reaction to pull requests you find important.

[phanirithvij]

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.

just a reminder.

from the post above, last paragraph.

[phanirithvij]

nixpkgs-review result

Generated using nixpkgs-review-gha

Command: nixpkgs-review pr 438057

Logs: https://github.com/phanirithvij/nixpkgs-review-gha/actions/runs/17312291798

---

x86_64-linux

✅ 1 package built:

• bant

---

aarch64-linux

✅ 1 package built:

• bant

---

aarch64-darwin (sandbox = true)

❌ 1 package failed to build:

• bant

[pyrox0]

is the aarch64-darwin build failure new?

[phanirithvij]

logs say

       > ERROR: Could not build Bazel
       For full logs, run:
         nix log /nix/store/d5y3f2b8801y4kpm9vk4pdnjnskj5yib-bazel-7.6.0.drv

bazel doesn't seem to build on aarch64-darwin

edit: maybe #435110?

[hzeller]

Looks like the bazel 7 situation is taken care of by @emilazy in #435110
So this PR is good to go.