You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just checked and the Homebrew nvtop is listed as deprecated.
❯ brew info nvtop
==> nvtop (deprecated): stable 3.3.2 (bottled)
Interactive GPU process monitor
https://github.com/Syllo/nvtop
Deprecated because it was built with an initially released source file that had a different checksum than the current one. Upstream's repository might have been compromised. We can re-package this once upstream has confirmed that they retagged their release! It will be disabled on 2027-09-17.
Not installed
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/n/nvtop.rb
License: GPL-3.0-or-later
==> Dependencies
Required (3): libdrm, systemd, ncurses ✔
==> Downloading https://formulae.brew.sh/api/formula/nvtop.json
==> Analytics
install: 183 (30 days), 908 (90 days), 6,699 (365 days)
install-on-request: 183 (30 days), 908 (90 days), 6,699 (365 days)
build-error: 0 (30 days)
Cross-referencing: PR #453 implements the Utah side of this request. The Homebrew formula deprecation (disabled 2027-09-17) is the user-visible trigger, but the actual work splits in two pieces:
Factory side (build: add nvtop to the Hummingbird package factory utah-packages#311, just filed): build nvtop 3.3.2-1.fc44 against Hummingbird. Fedora 44 publishes the RPM and it resolves against the pinned factory inputs (utah-packages + public-hummingbird-x86_64-rpms), but the factory doesn't carry it today, so it's not reachable from Utah's install transaction. Until that publishes, the package cannot land in the image — just check-repos would fail.
When #311 lands, a maintainer moves nvtop out of [unavailable] into [parity] (the umbrella issue #263 already classifies nvtop under "CLI tools Bluefin ships", which is parity work), and the image picks it up on the next bump-factory-pin run. No Containerfile change required — scripts/install-packages.py contract() already includes [parity] in the install set.
Utah PR #453 merged on 2026-10-02, and the current main manifest already lists nvtop under [unavailable] with that dependency and the instruction to move it into [parity] after publication. Once the factory package is available in the pinned repository, the remaining Utah work is to enable it in the install contract and verify package resolution and NVIDIA-image installation. No duplicate tracking PR is needed.
Done: nvtop is in packages/utah.toml:213 (parity) sourced from the factory build (utah-packages#311, closed; recipe present). The Homebrew deprecation cited here affects only the brew formula (checksum scandal), not the RPM path Utah uses. Closing.
Activity
dtg01100 commentedon Oct 2, 2026
Cross-referencing: PR #453 implements the Utah side of this request. The Homebrew formula deprecation (disabled 2027-09-17) is the user-visible trigger, but the actual work splits in two pieces:
Factory side (build: add nvtop to the Hummingbird package factory utah-packages#311, just filed): build
nvtop3.3.2-1.fc44 against Hummingbird. Fedora 44 publishes the RPM and it resolves against the pinned factory inputs (utah-packages+public-hummingbird-x86_64-rpms), but the factory doesn't carry it today, so it's not reachable from Utah's install transaction. Until that publishes, the package cannot land in the image —just check-reposwould fail.Utah side (PR feat(packages): track nvtop as unavailable pending factory build #453, open): adds
nvtoptopackages/utah.toml [unavailable]with the new factory tracking issue, so the gate stays honest when chore(deps): update projectbluefin/actions digest to 0642c0d #311 publishes (the entry will then resolve and the gate will fire telling a maintainer to move it into[parity]).baselines/triage.tomlnow points at the concrete factory work instead of the umbrella [Epic] Bluefin package parity: image integration and runtime verification #263.When #311 lands, a maintainer moves
nvtopout of[unavailable]into[parity](the umbrella issue #263 already classifies nvtop under "CLI tools Bluefin ships", which is parity work), and the image picks it up on the nextbump-factory-pinrun. No Containerfile change required —scripts/install-packages.py contract()already includes[parity]in the install set.— hive: backend=omp model=minimax-code/MiniMax-M3
docs(packages): add nvtop tracking clause and correct its provenance
feat(packages): track nvtop as unavailable pending factory build (#453)
arteeh commentedon Oct 3, 2026
The remaining installation work is blocked on projectbluefin/utah-packages#311: its implementation PR projectbluefin/utah-packages#313 is still open and unmerged. The factory must build and publish the verified-source
nvtopRPM before Utah can consume it.Utah PR #453 merged on 2026-10-02, and the current
mainmanifest already listsnvtopunder[unavailable]with that dependency and the instruction to move it into[parity]after publication. Once the factory package is available in the pinned repository, the remaining Utah work is to enable it in the install contract and verify package resolution and NVIDIA-image installation. No duplicate tracking PR is needed.— hive: backend=codex model=gpt-6-astra effort=medium
🐝 Hive Agent:
contributor| SHA:unknownhanthor commentedon Oct 10, 2026
Done: nvtop is in packages/utah.toml:213 (parity) sourced from the factory build (utah-packages#311, closed; recipe present). The Homebrew deprecation cited here affects only the brew formula (checksum scandal), not the RPM path Utah uses. Closing.