From ee97ce82c0f2249640ff477ab83085b82ec58ac6 Mon Sep 17 00:00:00 2001 From: hive Date: Sat, 3 Oct 2026 23:13:20 +0000 Subject: [PATCH 1/2] fix(packages): record nss-mdns .local resolution parity gap as unavailable Bluefin ships nss-mdns (baselines/bluefin/rpms.tsv, 0.15.1-28.fc44) so `ping foo.local` resolves over mDNS; Utah does not, and Hummingbird's repository does not carry it either -- it appears in that repodata only as a Recommends of cups (a virtual provide), never as an installable . Enabling avahi-daemon restores mDNS service browsing but not .local name resolution, which is what this module provides (the two are separate; reviewed against #411). Records nss-mdns as an image-level parity gap in packages/utah.toml [unavailable] and baselines/triage.toml ([package.nss-mdns], status unavailable, area network-fs, issue #499), mirroring the nvtop precedent. Bumps the genuinely-unavailable count 7 -> 8 and updates the README parity table, site/data/packages.json (regenerated), and docs/skills/package-contract.md in lockstep so just check stays green. Hive-Run: projectbluefin/utah#499 Hive-Plan: record nss-mdns as an unavailable image-level parity gap in utah.toml and triage.toml, bump the unavailable count 7 to 8 and sync README, packages.json, package-contract.md Hive-Spec: package-contract.md#[unavailable] Signed-off-by: hive --- README.md | 2 +- baselines/triage.toml | 11 +++++++++++ docs/skills/package-contract.md | 5 +++-- packages/utah.toml | 16 ++++++++++++++++ site/data/packages.json | 8 +++++++- 5 files changed, 38 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index cbc530001..2cc54115b 100644 --- a/README.md +++ b/README.md @@ -102,7 +102,7 @@ than being noticed later. | --- | --- | | Bluefin contract installed | **61** | | Utah additions (GNOME 51, base-image parity, device firmware, desktop services) | 105 | -| Genuinely unavailable | **7** | +| Genuinely unavailable | **8** | The install writes its resolved list to `/usr/share/utah/contract.txt` and the verify step asserts *that file*, so the two cannot disagree. The unavailable diff --git a/baselines/triage.toml b/baselines/triage.toml index 3e498906b..b55da187f 100644 --- a/baselines/triage.toml +++ b/baselines/triage.toml @@ -1025,6 +1025,17 @@ status = "untriaged" [package.avahi-tools] status = "untriaged" +[package.nss-mdns] +status = "unavailable" +area = "network-fs" +reason = "packages/utah.toml [unavailable]" +issue = "#499" +# .local name resolution over mDNS (Name Service Switch module). Image-level +# parity gap: Bluefin ships it, Hummingbird's repository and the utah-packages +# factory do not, so no repository Utah enables supplies it. Distinct from +# avahi, which this triages as untriaged; enabling avahi-daemon does not bring +# .local resolution. See packages/utah.toml [unavailable]. + [package.b43-fwcutter] status = "untriaged" diff --git a/docs/skills/package-contract.md b/docs/skills/package-contract.md index f25c8cbbc..fd5d6f50e 100644 --- a/docs/skills/package-contract.md +++ b/docs/skills/package-contract.md @@ -75,7 +75,8 @@ hardware establishes that its radio works. It covers both kinds of parity gap: names in the copied `base.toml` contract, and names Bluefin's published image ships from a build file outside that contract (recorded in `baselines/bluefin/rpms.tsv` and triaged in -`baselines/triage.toml` — `nvtop` is the current example). Each entry +`baselines/triage.toml` — `nvtop` and `nss-mdns` are the current example). +Each entry **MUST carry a tracking issue**: the list is the documented parity debt, not a dumping ground for packages that are merely inconvenient (header comment, `packages/utah.toml`). @@ -250,7 +251,7 @@ Update it whenever synchronizing `packages/bluefin.toml` with upstream. Current counts, per the README "Package parity" section: 61 Bluefin contract packages installed, 105 Utah additions (GNOME 51, base-image parity, device -firmware, desktop services), 7 genuinely unavailable. `scripts/check-doc-counts.py` (part of +firmware, desktop services), 8 genuinely unavailable. `scripts/check-doc-counts.py` (part of `just check`) recomputes these from the manifests and fails if either document drifts from `site/data/packages.json`. diff --git a/packages/utah.toml b/packages/utah.toml index 5242153f9..c75015c31 100644 --- a/packages/utah.toml +++ b/packages/utah.toml @@ -479,6 +479,21 @@ packages = [ # requirement on utah-packages#311). Add `nvtop` to `[parity]` once # utah-packages#311 publishes an Hummingbird-targeted build, which must only # happen after that verification. Tracked by #451 and utah-packages#311. +# +# nss-mdns +# nss-mdns is the Name Service Switch module that resolves .local hostnames +# over mDNS, so `ping foo.local` resolves. Bluefin ships it +# (baselines/bluefin/rpms.tsv, nss-mdns 0.15.1-28.fc44); Utah does not, and +# Hummingbird's repository does not carry it either -- verified in +# repodata/primary.xml, where nss-mdns appears only as a Recommends of cups +# (a virtual provide) and never as an installable . It is an +# image-level parity gap, not inherited from the copied base.toml contract +# (nss-mdns is not in packages/bluefin.toml) and not built by the +# utah-packages factory, so no repository Utah enables at runtime supplies it. +# Enabling avahi-daemon restores mDNS service browsing but not .local name +# resolution, which is what this module provides; the two are separate +# (found while reviewing #411). Returns once the factory builds nss-mdns for +# Hummingbird and utah-packages publishes the build; tracked by #499. packages = [ "grub2-efi-x64-cdboot", "anaconda-live", @@ -486,6 +501,7 @@ packages = [ "firefox", "fish", "nvtop", + "nss-mdns", "slitherer", ] diff --git a/site/data/packages.json b/site/data/packages.json index 66944b393..47257659f 100644 --- a/site/data/packages.json +++ b/site/data/packages.json @@ -224,7 +224,7 @@ ], "totals": { "installed": 166, - "unavailable": 7 + "unavailable": 8 }, "unavailable": [ { @@ -255,6 +255,12 @@ ], "name": "grub2-efi-x64-cdboot" }, + { + "issues": [ + 499 + ], + "name": "nss-mdns" + }, { "issues": [ 451 From 638e2f6b23b815931b773c648ce0616c97402aba Mon Sep 17 00:00:00 2001 From: scanner Date: Sat, 3 Oct 2026 19:54:04 -0400 Subject: [PATCH 2/2] fix(packages): drop nss-mdns triage entry the gap checker never reports nss-mdns ships no path in baselines/bluefin/surface.tsv, so image-baseline.py check never derives it as a gap and flagged the entry as one to drop. The parity debt stays recorded in packages/utah.toml [unavailable] and site/data/packages.json. Restore nvtop as the sole triage.toml example in package-contract.md. Hive-Fix-Attempt: 1/6 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: scanner --- baselines/triage.toml | 11 ----------- docs/skills/package-contract.md | 3 +-- 2 files changed, 1 insertion(+), 13 deletions(-) diff --git a/baselines/triage.toml b/baselines/triage.toml index b55da187f..3e498906b 100644 --- a/baselines/triage.toml +++ b/baselines/triage.toml @@ -1025,17 +1025,6 @@ status = "untriaged" [package.avahi-tools] status = "untriaged" -[package.nss-mdns] -status = "unavailable" -area = "network-fs" -reason = "packages/utah.toml [unavailable]" -issue = "#499" -# .local name resolution over mDNS (Name Service Switch module). Image-level -# parity gap: Bluefin ships it, Hummingbird's repository and the utah-packages -# factory do not, so no repository Utah enables supplies it. Distinct from -# avahi, which this triages as untriaged; enabling avahi-daemon does not bring -# .local resolution. See packages/utah.toml [unavailable]. - [package.b43-fwcutter] status = "untriaged" diff --git a/docs/skills/package-contract.md b/docs/skills/package-contract.md index fd5d6f50e..5a8c1cc10 100644 --- a/docs/skills/package-contract.md +++ b/docs/skills/package-contract.md @@ -75,8 +75,7 @@ hardware establishes that its radio works. It covers both kinds of parity gap: names in the copied `base.toml` contract, and names Bluefin's published image ships from a build file outside that contract (recorded in `baselines/bluefin/rpms.tsv` and triaged in -`baselines/triage.toml` — `nvtop` and `nss-mdns` are the current example). -Each entry +`baselines/triage.toml` — `nvtop` is the current example). Each entry **MUST carry a tracking issue**: the list is the documented parity debt, not a dumping ground for packages that are merely inconvenient (header comment, `packages/utah.toml`).