Skip to content

feat: add the library used by wireless services - #802

Closed
mrbobbytables wants to merge 8 commits into
projectbluefin:mainfrom
mrbobbytables:hive/502-long-tail-resolution
Closed

mrbobbytables wants to merge 8 commits into
projectbluefin:mainfrom
mrbobbytables:hive/502-long-tail-resolution

Conversation

@mrbobbytables

@mrbobbytables mrbobbytables commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary: This adds a small software component that wireless programs rely on to the project's automated software builder. It helps the built system provide a component that other programs need, rather than confusing it with unrelated software that has a similar name. The remaining packages in this group still need build and installation checks.

What I need from you: Review the recipe and its upstream source lock.


Changes

  • Import Fedora Rawhide's libell source recipe at commit 4eef73d6390c72617d779cceb4d20063cbbe6dcc. The audited binary comes from source package libell, not the unrelated source package ell.
  • Lock upstream release 0.83 at https://www.kernel.org/pub/linux/libs/ell/ell-0.83.tar.xz; its SHA-512 matches both Fedora's source manifest and the downloaded upstream archive.
  • Register the recipe in Packit, refresh the architecture inventory, and move libell from pending to recipe-resolved in the backlog. This does not claim publication or runtime acceptance.
  • Record the HTTP/1.1 retry for Fedora dist-git clone failures in the backlog skill.

Source and build status

  • Fedora recipe tree: 2af8fa9f2bbe353f741dcc803e12d4c6ae9c93d6.
  • Upstream source SHA-512: 4cf7f65fb0595158c2719d0b53b6059877f53e701fb708f4e5315f81af0d70a6083799bf1d11f33fede24edbccb78694ea5b598b286dcc60d9fb695261339879.
  • No hosted package build, publication, permitted-repository dependency transaction, or representative runtime exercise is claimed here.

Remaining batch work

  • libev, libijs, liblqr-1, libmspack, libnet, libpaper, and libpfm remain pending recipe outputs.
  • The other outputs already recorded in the backlog still need dependency-resolution and runtime evidence; libpath_utils also needs its compatibility check.
  • Issue parity(long-tail): resolve factory outputs libdeflate through libpskc #502 stays open until every output has a recorded disposition and the required build, publication, and runtime evidence.

Validation

  • python3 tools/factory_build_backlog.py --check: passed.
  • python3 tools/validate.py: passed; 638 source RPMs validated.
  • just check and just test: passed; 1,396 tests passed and 2 skipped.
  • Pre-commit hooks passed for all changed files. The all-files run still reports two existing failures in unchanged files: a tab in packages/powerstat/packit.yaml:4, and actionlint/ShellCheck SC2129 in .github/workflows/rebuild-rpms.yml:367.
  • git diff --check: passed.

Refs #502 — partial recipe import; remaining outputs and batch runtime acceptance stay open.


🐝 Hive Agent: contributor | SHA: 9e3f7a2

— hive: backend=copilot model=gpt-6-luna

Imports Fedora Rawhide's libell recipe, locks the upstream release with SHA-512, and records recipe-only progress in the long-tail backlog. Build, publication, and runtime evidence remain open on projectbluefin#502.

Hive-Run: projectbluefin#502
Hive-Plan: libell source import
Hive-Spec: issue-502#long-tail.libell
Assisted-by: Auto via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: mrbobbytables <mrbobbytables@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
Link the recipe-resolution record to the reviewable import pull request.

Hive-Run: projectbluefin#502
Hive-Plan: libell source import
Hive-Spec: issue-502#long-tail.libell
Assisted-by: Auto via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
@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 29, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables 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

@mrbobbytables 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

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

Decision needed: @hanthor should decide whether to close #802 in favour of #793 (which already imports the identical libell recipe plus its consumer iwd) and fold #802's backlog move for libell into #793.

This appears to duplicate the libell half of #793, which imports the same recipe.

What I verified by diffing both PRs (not from the bodies):

  • packages/libell/libell.spec, sources, changelog, .gitignore are byte-identical in both PRs.
  • packages/libell/.hummingbird-upstream.json pins the same dist-git commit 4eef73d6… / tree 2af8fa9f… in both; only imported_at differs.
  • Both touch .packit.yaml, config/upstream-sources.json, config/factory-build-backlog.toml, reports/factory-build-backlog.json, docs/architecture.md, docs/skills/factory-build-backlog.md — so they conflict with each other rather than stack. Both are already CONFLICTING against main.

Where they differ:

  • #793's config/upstream-sources.json entry for libell carries a Fedora lookaside fallback_urls; this PR's entry has none.
  • This PR moves libell from [areas.long-tail] to [resolved] in config/factory-build-backlog.toml; #793 does not (it only moves iwd, leaving libell listed as pending with state already_recipe). I have noted that on #793.
  • This PR adds the HTTP/1.1 import_rawhide.py retry note to docs/skills/factory-build-backlog.md; #793 adds an iwd/libell section instead.

#793 is earlier, brings the only consumer of libell (iwd), and has the more complete source lock, so it looks like the one to keep; the [resolved] move (and optionally the HTTP/1.1 note) is worth carrying over to it. If you agree, this one could be closed in favour of #793. I have not closed anything.

Confidence: 3/5 (needs attention) — 1 medium finding; 1 perspective requires a human decision

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

@hivecommons-hive hivecommons-hive Bot added needs-human stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue and removed stage/074-adopted-by-hive Contributor PR adopted: author unavailable after red CI; the hive is finishing it (takeover path) labels Oct 29, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

Needs a decision, not a merge:

Head: verdict requires_human @9e3f7a2, 21/21 checks green, soak 0s of 30m0s.

What to do: a trusted merger approves this head (9e3f7a2) — a GitHub Approve review, or a /hive approve reply posted after the verdict — and the hive re-evaluates on its next pass; the PR author cannot release their own PR, and the hive does not push to a PR it did not open.

Clear the cause and the hive re-evaluates on its next pass; the stage moves to stage/090-ready-for-human-merge, stage/095-pre-merge-soak or the merge queue on its own. An approval does not bypass CI, hold labels or other merge gates.

@hanthor

hanthor commented Oct 29, 2026

Copy link
Copy Markdown
Member

/hive decision Prefer #793: it already carries the identical libell recipe plus its consumer iwd, so #802 is a strict subset. Do not merge #802 on its own; close it once #793 lands, folding the libell backlog move into #793. Leaving it open until then so the contributor commits stay visible. No approval of #802 is implied.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

/hive decision routes a fix to the hive's own author agent, and the hive did not open this PR, so it will not push to it. The PR-side equivalents are reviews: Approve head 9e3f7a2 to let it merge as-is, or leave a changes requested review and the author is nudged with your text. See https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@mrbobbytables

Copy link
Copy Markdown
Contributor Author

hive-base-moved: merged projectbluefin/utah-packages main at fe68613.


🐝 Hive Agent: contributor | SHA: unknown

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables 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 and removed stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue labels Oct 29, 2026

@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 the recipe and source lock at head 5f040c5 against the tree. Looks correct to me.

  • packages/libell/libell.spec is byte-identical to Fedora Rawhide rpms/libell at 4eef73d (diffed the raw spec; only the %changelog body differs, as expected with %autochangelog).
  • Downloaded https://www.kernel.org/pub/linux/libs/ell/ell-0.83.tar.xz and computed SHA-512: matches packages/libell/sources and config/upstream-sources.json:5811 exactly.
  • python3 tools/validate.py → validated 648 source RPMs (643 rawhide, 5 upstream); tools/factory_build_backlog.py --check → consistent. .packit.yaml:1609-1614 registration is well-formed.
  • Minor body nit, not a code issue: the Validation section says "638 source RPMs validated"; the tree and docs/architecture.md both say 648.

Sequencing note: #811 rewrites the same generated hunks (docs/architecture.md counts 647 vs 648 here; reports/factory-build-backlog.json totals). Whichever merges second needs a rebase and backlog regeneration.

Confidence: 5/5 (safe)

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

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@mrbobbytables

Copy link
Copy Markdown
Contributor Author

hive-base-moved: merged current main at 08684453c5c6e3bc92a5ba0d6925b9eb6cffb83f into this PR.


🐝 Hive Agent: contributor | SHA: unknown

@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/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue labels Oct 29, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

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

Failing checks:

  • Canary

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.

Your relay session received this as a fix-pr task and launched a parallel fix session; your current work continues.

@mrbobbytables

Copy link
Copy Markdown
Contributor Author

Canary root cause identified: merge b72b40c retained the old Packit digest in .github/workflows/import-rawhide-package.yml and .github/workflows/packit-srpm-chunk.yml, reverting the update already merged in #814. Those unintended workflow changes trigger the fork-only maintainer Canary proof requirement. Restoring both pins to main’s sha256:67042bc007aefa24e30064e49dbcbacb0ecdf62d629ff5d059f2c14b5de5aa86 leaves a recipe-only PR diff; the existing Canary relevance classifier then correctly requires no pipeline proof. No gate changes are needed.

The fix and related lane-validation guidance are committed locally as c3d6fc0 with the original DCO sign-off. just check and just test passed (1396 passed, 2 skipped), and the final merge-base diff was explicitly checked against pipeline_relevant.

Push blocked: GitHub rejected the configured OAuth credential because it lacks workflow scope. The remote PR head remains unchanged. A workflow-authorized credential is required to push these corrections to the existing branch; rerunning the current head does not fix the unintended workflow diff.


🐝 Hive Agent: contributor | SHA: c3d6fc0

@hivecommons-hive

Copy link
Copy Markdown
Contributor
b72b40c

⚠️ Sentinel alert — maintainer review required

Hive flagged this PR (author @mrbobbytables, head b72b40c13694) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

  • sensitive_path — changes 2 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
    • .github/workflows/import-rawhide-package.yml
    • .github/workflows/packit-srpm-chunk.yml

Hive added the sentinel-alert label. While it is present, Hive will not approve this PR, apply LGTM/approval labels, or merge it through any auto-merge lane. Remove the label once reviewed; Hive will not re-apply it unless new commits are pushed. Tune paths and behaviors under sentinel in hive.yaml or the dashboard Security tab.

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

Summary: Re-review of only what changed since the last look: the author merged the main branch into this branch. That merge accidentally undid a separate, already-landed update that moved the build system's container image to a newer pinned version, so this branch now points two automated build jobs back at the older image. The new library recipe itself is unchanged and fine.

What I need from you: Restore the newer image pin in the two workflow files (fix below), then this is ready.


correctness (medium, in-scope)

Merge commit b72b40c1 ("chore: merge main into PR 802") kept the PR side of the packit image digest and reverted #814 (e6a2db80), which bumped quay.io/packit/packit:latest from b72ebfa2… to 67042bc0…. The PR diff against main now shows -67042bc0… / +b72ebfa2… in .github/workflows/import-rawhide-package.yml:80 and .github/workflows/packit-srpm-chunk.yml:69 — neither file is part of this PR's purpose, and merging it would silently roll back the dependency update.

.github/workflows/import-rawhide-package.yml:80

            quay.io/packit/packit:latest@sha256:67042bc007aefa24e30064e49dbcbacb0ecdf62d629ff5d059f2c14b5de5aa86 bash -exc '

.github/workflows/packit-srpm-chunk.yml:69

            quay.io/packit/packit:latest@sha256:67042bc007aefa24e30064e49dbcbacb0ecdf62d629ff5d059f2c14b5de5aa86 bash -exc '

intent-alignment (low, in-scope, advisory)

Previous finding re-checked: packages/libell/libell.spec:1 is still also carried by open #793 (libell.spec and sources blobs are byte-identical: e43cb2f9, d3583ce0; only imported_at in .hummingbird-upstream.json differs). Not blocking — whichever lands second needs a trivial rebase to drop its copy of packages/libell/, the .packit.yaml entry, and the upstream-sources.json entry.

No findings from: security, style, docs-currency.

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

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

@Danathar

Copy link
Copy Markdown
Contributor

Sentinel review (maintainer): the only workflow change in this PR is the quay.io/packit/packit:latest digest in .github/workflows/import-rawhide-package.yml and .github/workflows/packit-srpm-chunk.yml going from 67042bc0… (current main, Renovate e6a2db8 on 2026-10-29) back to b72ebfa2… (the 2026-10-27 digest). That is a downgrade left over from an older merge of main. Please restore both workflow files to main's version (git checkout origin/main -- .github/workflows/); with no workflow diff left, the Sentinel alert can be cleared.

Also note: #793 adds libell too (with iwd). Whichever of the two merges second will need its libell recipe and source lock dropped to avoid a duplicate.

@mrbobbytables

Copy link
Copy Markdown
Contributor Author

Restored both Packit image digests in local commit c0f249a. GitHub rejected the push because the available OAuth credential lacks workflow scope for .github/workflows; the remote head remains b72b40c, and no workflow changes were pushed.


🐝 Hive Agent: contributor | SHA: unknown

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables the hive has adopted this PR (stage/074-adopted-by-hive): CI stayed red and the review asks stayed open (the review swarm requested changes) for 2h after the nudge and the relay nudge went unanswered. The hive will rebase this branch on main and fix CI here; your commits and sign-off stay. Push a new head yourself at any time and the hive yields it back to you. The merge stays manual: the PR edits CI workflow / action files, which the lane never merges unattended; once CI is green a maintainer reviews and merges it (stage 085).

@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
@hivecommons-hive

Copy link
Copy Markdown
Contributor

⚠️ Hold-gate mergeability: Hive could not update this branch

This PR is hold-gated and has fallen behind its base branch. Hive keeps held PRs up to date while they wait on review, but it could not update this one. The branch is in a fork the Hive app cannot push to ("Allow edits by maintainers" is off, or GitHub refused the push).

Hive will not try again until this branch or its base branch changes. To bring it up to date now, ask the author to merge the base branch in, or use Update branch on this PR if GitHub offers it.

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

Blocking: .github/workflows/import-rawhide-package.yml:80 and packit-srpm-chunk.yml:69 change the pinned quay.io/packit/packit image hash (67042bc0… → b72ebfa2…). That has nothing to do with libell, the PR body doesn't mention it, and it changes trusted workflows from a fork. Please split it into its own PR or drop it. The branch also needs a rebase.

@hivecommons-hive hivecommons-hive Bot added the stage/stalled In its current stage longer than expected label Oct 30, 2026
@hanthor

hanthor commented Oct 30, 2026

Copy link
Copy Markdown
Member

libell is now on main through #827 (the rebased #793), with an identical recipe, lock and backlog entry. This PR's remaining change is the unexplained quay.io/packit/packit digest bump in import-rawhide-package.yml and packit-srpm-chunk.yml. If that bump is wanted, please open it as its own PR saying where the new digest comes from; otherwise this PR can be closed.

A stale merge of main left this branch pinning quay.io/packit/packit at the 2026-10-27 digest (b72ebfa2), so merging would downgrade main's 67042bc0. This PR does not intend to change either workflow.

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

@mrbobbytables 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 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 labels Oct 30, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

🔒 Hold-gate integrity: branch changed while hold-gated — fresh review required

This PR's branch moved while it sat hold-gated: the head recorded when the hold was applied was b72b40c13694, but the branch now sits at 2cdbfd00a851. The diff a reviewer saw under the hold is no longer the diff that would merge, so auto-merge is blocked and the hold label has been re-applied.

Commits not present in the hold-time snapshot (1):

  • 2cdbfd00a851 by Danathar — ci: restore main's packit image digest in the import and srpm workflows

Authors not in the hold-time author set: Danathar

A human should review the FULL diff at the current head — a rebase or force-push renames every commit, so everything above needs eyes even if it looks familiar. Removing the hold label after that review is the fresh approval: the guard has re-pinned its snapshot to the current head, so a clean lift re-opens the merge lanes.

@hivecommons-hive hivecommons-hive Bot added the hold Work is intentionally paused. label Oct 30, 2026

@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

Assisted-by: Auto mode via GitHub Copilot

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@mrbobbytables

Copy link
Copy Markdown
Contributor Author

hive-base-moved: merged current main at cf586df.


🐝 Hive Agent: contributor | SHA: unknown

@mrbobbytables

Copy link
Copy Markdown
Contributor Author

Closing as superseded per the maintainer's decision: #793 landed via #827, which already carries the libell recipe and backlog accounting. The refreshed branch confirms the Packit digest matches main; no separate change remains for this PR.

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 hold Work is intentionally paused. needs-human no-dco A commit is missing Signed-off-by — run `git rebase --signoff` 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants