Repository navigation
feat: add the library used by wireless services - #802
mrbobbytables wants to merge 8 commits into
Conversation
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>
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>
|
@mrbobbytables this PR is back in your court ( Review asks:
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. |
|
@mrbobbytables the hive has adopted this PR ( |
There was a problem hiding this comment.
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,.gitignoreare byte-identical in both PRs.packages/libell/.hummingbird-upstream.jsonpins the same dist-git commit4eef73d6…/ tree2af8fa9f…in both; onlyimported_atdiffers.- 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 alreadyCONFLICTINGagainstmain.
Where they differ:
- #793's
config/upstream-sources.jsonentry forlibellcarries a Fedora lookasidefallback_urls; this PR's entry has none. - This PR moves
libellfrom[areas.long-tail]to[resolved]inconfig/factory-build-backlog.toml; #793 does not (it only movesiwd, leavinglibelllisted as pending with statealready_recipe). I have noted that on #793. - This PR adds the HTTP/1.1
import_rawhide.pyretry note todocs/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
|
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 ( Clear the cause and the hive re-evaluates on its next pass; the stage moves to |
|
/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. |
|
|
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
hive-base-moved: merged projectbluefin/utah-packages main at fe68613. 🐝 Hive Agent: |
|
@mrbobbytables this PR has a new head without confirmed hive push evidence, so the hive has handed this PR back to you ( |
There was a problem hiding this comment.
Reviewed the recipe and source lock at head 5f040c5 against the tree. Looks correct to me.
packages/libell/libell.specis byte-identical to Fedora Rawhiderpms/libellat4eef73d(diffed the raw spec; only the%changelogbody differs, as expected with%autochangelog).- Downloaded
https://www.kernel.org/pub/linux/libs/ell/ell-0.83.tar.xzand computed SHA-512: matchespackages/libell/sourcesandconfig/upstream-sources.json:5811exactly. python3 tools/validate.py→validated 648 source RPMs (643 rawhide, 5 upstream);tools/factory_build_backlog.py --check→ consistent..packit.yaml:1609-1614registration is well-formed.- Minor body nit, not a code issue: the Validation section says "638 source RPMs validated"; the tree and
docs/architecture.mdboth 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>
|
hive-base-moved: merged current main at 08684453c5c6e3bc92a5ba0d6925b9eb6cffb83f into this PR. 🐝 Hive Agent: |
|
@mrbobbytables this PR is back in your court ( Failing checks:
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 |
|
Canary root cause identified: merge b72b40c retained the old Packit digest in The fix and related lane-validation guidance are committed locally as Push blocked: GitHub rejected the configured OAuth credential because it lacks 🐝 Hive Agent: |
b72b40c
|
There was a problem hiding this comment.
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
|
Sentinel review (maintainer): the only workflow change in this PR is the Also note: #793 adds |
|
@mrbobbytables the hive has adopted this PR ( |
|
hanthor
left a comment
There was a problem hiding this comment.
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.
|
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 |
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>
|
@mrbobbytables this PR has a new head without confirmed hive push evidence, so the hive has handed this PR back to you ( |
🔒 Hold-gate integrity: branch changed while hold-gated — fresh review requiredThis PR's branch moved while it sat hold-gated: the head recorded when the hold was applied was Commits not present in the hold-time snapshot (1):
Authors not in the hold-time author set: 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. |
Assisted-by: Auto mode via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
hive-base-moved: merged current main at cf586df. 🐝 Hive Agent: |
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
libellsource recipe at commit4eef73d6390c72617d779cceb4d20063cbbe6dcc. The audited binary comes from source packagelibell, not the unrelated source packageell.0.83athttps://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.libellfrom pending to recipe-resolved in the backlog. This does not claim publication or runtime acceptance.Source and build status
2af8fa9f2bbe353f741dcc803e12d4c6ae9c93d6.4cf7f65fb0595158c2719d0b53b6059877f53e701fb708f4e5315f81af0d70a6083799bf1d11f33fede24edbccb78694ea5b598b286dcc60d9fb695261339879.Remaining batch work
libev,libijs,liblqr-1,libmspack,libnet,libpaper, andlibpfmremain pending recipe outputs.libpath_utilsalso needs its compatibility check.Validation
python3 tools/factory_build_backlog.py --check: passed.python3 tools/validate.py: passed; 638 source RPMs validated.just checkandjust test: passed; 1,396 tests passed and 2 skipped.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