Skip to content

feat: prepare the iwd Wi-Fi service for Utah - #793

Closed
Danathar wants to merge 6 commits into
mainfrom
feat/import-iwd-libell
Closed

Danathar wants to merge 6 commits into
mainfrom
feat/import-iwd-libell

Conversation

@Danathar

@Danathar Danathar commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary: This adds build recipes for iwd, a Wi-Fi connection service that Bluefin ships and Utah (the Bluefin-like image this repository builds packages for) does not have yet. It also adds the small system library iwd needs to run, which the base system Utah builds on does not provide. This only prepares the recipes. Whether the package builds, gets published and works on a real Wi-Fi card still has to be checked, so the tracking issue stays open.


Refs #486 — partial: this resolves only iwd. Remaining in the batch: fedora-release-common, fedora-release-identity-silverblue, fedora-release-ostree-desktop, fedora-release-silverblue, generic-logos (branding, which needs a linked maintainer decision), fuse-encfs (retired in Fedora Rawhide) and hfsplus-tools (upstream source host returns 404). Consumer tracking: projectbluefin/utah#392 (Utah triage lists iwd as planned under projectbluefin/utah#262).

What changed

Recipe Fedora dist-git commit Upstream source (SHA-512 locked) Audited binary
libell 0.83 a4b3fa900dfacba2961ef7e65f816789c31e816e https://www.kernel.org/pub/linux/libs/ell/ell-0.83.tar.xz — (runtime dependency of iwd)
iwd 3.12 4eef73d6390c72617d779cceb4d20063cbbe6dcc https://www.kernel.org/pub/linux/network/wireless/iwd-3.12.tar.xz iwd
  • Recipes imported unmodified with tools/import_rawhide.py. Fedora's iwd/.gitignore ignores iwd.spec and sources, so those two were staged with git add -f (same tracked-but-ignored pattern as hplip and ibus).
  • config/upstream-sources.json: kernel.org primary url, Fedora lookaside only in fallback_urls. I downloaded both upstream tarballs and checked that their SHA-512 matches the pins in packages/*/sources. Both fallback URLs return HTTP 200.
  • .packit.yaml and docs/architecture.md were regenerated with tools/render_packit_config.py --write and tools/render_architecture_counts.py --write.
  • config/factory-build-backlog.toml: iwd moved from [areas.dev-tools] to [resolved], and reports/factory-build-backlog.json was regenerated (227 backlog entries, 212 pending).
  • docs/skills/factory-build-backlog.md: new section covering iwd and libell, the unrelated Fedora ell package, the .gitignore issue, and why fuse-encfs and hfsplus-tools can't be imported straight from Rawhide.

Dependencies

  • Fedora builds iwd with --enable-external-ell, so it needs libell.so at runtime. The current Hummingbird primary.xml has no libell/ell, so it builds here. libell-devel lists %{_libdir}/pkgconfig/ell.pc in its %files, so tools/build_graph.py orders it before iwd's pkgconfig(ell) >= 0.43 without any stage.
  • Fedora's ell dist-git is an unrelated header-only C++ library. I did not import it.
  • Other runtime requirements (dbus, systemd, readline) are in Hummingbird: dbus-1:1.16.2, systemd-261, readline-8.3 (hum1). wireless-regdb is only Recommends.
  • asciidoc and python3-docutils are build-time only and come from the build root, as they do for bluez and git.

Evidence still missing (not claimed)

  • Hosted digest-pinned Packit/mock build run URLs and resulting NEVRAs for libell and iwd
  • Factory OCI digest and repodata identity for the published binaries
  • Runtime resolution against Hummingbird plus the factory, and a real test of the program (e.g. iwctl --version, starting iwd.service on Wi-Fi hardware)

Validation

  • python3 tools/factory_build_backlog.py --check: consistent (227 entries, 212 pending)
  • just check: passed, including pytest (1390 passed, 2 skipped)
  • pre-commit run --all-files: not run because pre-commit isn't installed on this host. CI runs it.

🤖 Generated with Claude Code

— hive: backend=claude model=claude-opus-5-5


🐝 Hive Agent: contributor | SHA: 4292aea4

Danathar and others added 2 commits October 28, 2026 15:22
Import the iwd and libell source recipes from Fedora Rawhide and lock
their kernel.org release tarballs by SHA-512, with Fedora's lookaside as
fallback. iwd links libell at runtime and Hummingbird does not ship it,
so both build here; libell's ell.pc orders it first in the build graph.

Move iwd to the backlog's resolved records. Hosted build, publication
and runtime evidence remain outstanding in #486.

Hive-Run: #486
Hive-Plan: dev-tools source-family import
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>
Hive-Run: #486
Hive-Plan: dev-tools source-family import
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>
@hivecommons-hive hivecommons-hive Bot added author/clanker A contributor's own hive authored this PR under their login dco All commits are DCO signed-off role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 28, 2026
@hivecommons-hive hivecommons-hive Bot added stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 28, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the branch conflicts with the base and needs a rebase

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (4 waiting): fixes are handed out before new work as soon as you have capacity.

1 similar comment
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the branch conflicts with the base and needs a rebase

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (4 waiting): fixes are handed out before new work as soon as you have capacity.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Read the full diff against main and the backlog tooling in tools/factory_build_backlog.py. Two things worth fixing on the rebase the hive already asked for:

  1. libell is imported but left pending in the backlog. config/factory-build-backlog.toml:261 (main) still lists "libell" under [areas.long-tail] while this PR adds packages/libell/. The regenerated reports/factory-build-backlog.json shows the effect: libell flips from pending to already_recipe (states already_recipe 13 → 14) instead of leaving the backlog. --check passes because the snapshot was regenerated, so nothing flags it. Move libell to [resolved] with pr = 793, the same way iwd is moved at config/factory-build-backlog.toml:127. #802 does exactly this move for the identical libell recipe — see my note there.

  2. The dist-git commits in the PR body table are swapped. packages/libell/.hummingbird-upstream.json pins 4eef73d6… and packages/iwd/.hummingbird-upstream.json pins a4b3fa90…; the body lists them the other way round. I checked src.fedoraproject.org/rpms/{libell,iwd}/c/<sha>: each sha resolves only for the package the lock file names. The code is right; the body is not.

Overlap: #802 (libell only) is byte-identical in packages/libell/* to this PR except imported_at, and conflicts with it on the shared config/docs files. One of the two should land; this one carries the consumer and the lookaside fallback URLs.

Otherwise the recipe import and upstream-sources.json entries look correct to me: kernel.org primary with Fedora lookaside fallback, SHA-512 matching packages/*/sources.

Confidence: 3/5 (needs attention) — 1 medium finding; 2 perspectives requested changes

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

Conflicts resolved by keeping both sides (source locks, skill docs);
docs/architecture.md and reports/factory-build-backlog.json take main's
numbers moved by this PR's own delta. Recipe, .packit.yaml and
architecture counts checked equal.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnzFs53Qcer1xDySyxv1Vj
Signed-off-by: Danathar <berths-purger-0g@icloud.com>
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act and removed stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 29, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the branch conflicts with the base and needs a rebase

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (5 waiting): fixes are handed out before new work as soon as you have capacity.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnzFs53Qcer1xDySyxv1Vj
Signed-off-by: Danathar <berths-purger-0g@icloud.com>
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act and removed stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 29, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the branch conflicts with the base and needs a rebase

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (5 waiting): fixes are handed out before new work as soon as you have capacity.

1 similar comment
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the branch conflicts with the base and needs a rebase

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (5 waiting): fixes are handed out before new work as soon as you have capacity.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Read both recipes against the tree; this looks correct to me.

What I verified at 271ad7d:

  • packages/iwd/iwd.spec and packages/libell/libell.spec are byte-identical to Fedora dist-git rpms/iwd@a4b3fa9 and rpms/libell@4eef73d (fetched and diffed), matching the commits recorded in each .hummingbird-upstream.json.
  • SHA-512 in both sources files and config/upstream-sources.json match the dist-git sources entries and fresh downloads of kernel.org/pub/linux/libs/ell/ell-0.83.tar.xz and kernel.org/pub/linux/network/wireless/iwd-3.12.tar.xz.
  • iwd.spec:14 BuildRequires: pkgconfig(ell) >= 0.43 is satisfied by libell.spec:55 (%{_libdir}/pkgconfig/ell.pc in libell-devel, version 0.83), so the graph can order libell before iwd as the skill note says. asciidoc, python3-docutils, readline-devel, libtool have no recipe here, which is expected: the build root is Fedora 44 + Hummingbird (docs/skills/repeated-mistakes.md:709-712) and 23 existing specs already BR asciidoc.
  • Recommends: wireless-regdb (iwd.spec:21) has a recipe under packages/wireless-regdb.

Same merge note as on #786: #786, #789, #793 and #808 all regenerate the same lines in docs/architecture.md, config/factory-build-backlog.toml, reports/factory-build-backlog.json and .packit.yaml; whichever lands later needs the count/report tools re-run on rebase. The recipes themselves do not overlap.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar the hive has adopted this PR (stage/074-adopted-by-hive): your hive has been offline since the nudge. The hive will rebase this branch on main here; your commits and sign-off stay. Push a new head yourself at any time and the hive yields it back to you.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar this PR has a new head without confirmed hive push evidence, so the hive has handed this PR back to you (stage/074-adopted-by-hive → stage/072-returned-to-contributor). It will nudge again if CI stays red.

@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act and removed stage/074-adopted-by-hive Contributor PR adopted: author unavailable after red CI; the hive is finishing it (takeover path) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 29, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the branch conflicts with the base and needs a rebase

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (2 waiting): fixes are handed out before new work as soon as you have capacity.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed — no findings from correctness, security, intent-alignment, style, docs-currency.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar the hive has adopted this PR (stage/074-adopted-by-hive): your hive has been offline since the nudge. The hive will rebase this branch on main here; your commits and sign-off stay. Push a new head yourself at any time and the hive yields it back to you.

@hivecommons-hive hivecommons-hive Bot added stage/074-adopted-by-hive Contributor PR adopted: author unavailable after red CI; the hive is finishing it (takeover path) and removed stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act labels Oct 29, 2026

@hanthor hanthor left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The libell recipe here is identical to #802's. I suggest #802 goes first, then this PR is rebased to carry iwd only. The PR body has the libell and iwd commit hashes swapped.

@hivecommons-hive hivecommons-hive Bot added the stage/stalled In its current stage longer than expected label Oct 30, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnzFs53Qcer1xDySyxv1Vj
Signed-off-by: Danathar <berths-purger-0g@icloud.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar this PR has a new head without confirmed hive push evidence, so the hive has handed this PR back to you (stage/074-adopted-by-hive → stage/072-returned-to-contributor). It will nudge again if CI stays red.

@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act and removed stage/074-adopted-by-hive Contributor PR adopted: author unavailable after red CI; the hive is finishing it (takeover path) stage/stalled In its current stage longer than expected stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted labels Oct 30, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the branch conflicts with the base and needs a rebase

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (2 waiting): fixes are handed out before new work as soon as you have capacity.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

stage 095-pre-merge-soak → 072-returned-to-contributor: conflicting

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar the hive has adopted this PR (stage/074-adopted-by-hive): your hive has been offline since the nudge. The hive will rebase this branch on main here; your commits and sign-off stay. Push a new head yourself at any time and the hive yields it back to you.

@hivecommons-hive hivecommons-hive Bot added stage/074-adopted-by-hive Contributor PR adopted: author unavailable after red CI; the hive is finishing it (takeover path) and removed stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act labels Oct 30, 2026
@hanthor

hanthor commented Oct 30, 2026

Copy link
Copy Markdown
Member

Rebased onto main and continued in 827 (this PR's head stopped syncing with its branch).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author/clanker A contributor's own hive authored this PR under their login dco All commits are DCO signed-off role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/074-adopted-by-hive Contributor PR adopted: author unavailable after red CI; the hive is finishing it (takeover path)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants