Repository navigation
Conversation
… factory repo) Investigated run 33361378933. Seven of the eight failures were dependency- closure failures, not compile errors; one (mozjs140) was a real build break. mozjs140 (compile): the recipe declares '%global toolchain clang', so rpm injects the clang hardened-ld config (redhat-hardened-clang-ld.cfg) into the link flags cargo forwards to $CC. The sccache block drove that link through gcc, which rejects the clang-only config. Point the sccache wrapper at clang so the driver matches the hardening the toolchain selected. Verified by a full local rpmbuild (LTO off for host memory): builds to RPM, cargo build scripts link, no gcc rejection. FACTORY_REPO (systemic): the build/builddep steps only add the published [factory] repo when vars.FACTORY_REPO is set, and it is not. Already-published gaps that prepare skips as 'already published' are then in neither [stages] nor [factory], so a to-be-built package cannot resolve them -- e.g. pipewire-libs-extra could not find pkgconfig(libfreeaptx) though libfreeaptx is published. Default FACTORY_REPO to the Pages repo in all six blocks. abseil consumers (closure): utah ships abseil 20260526.0 (soname .2605, the latest upstream Hummingbird targets), but Fedora binaries libphonenumber, re2 and webrtc-audio-processing need .2601 and Fedora abseil is excluded. Per the malcontent precedent in docs/targeting-hummingbird.md, rebuild the consumers against the new soname rather than downgrade the library. Import the three from Rawhide dist-git at stage 1; webrtc's rawhide recipe already patches for current abseil. Unblocks gstreamer1-plugins-bad-free, webkitgtk, gjs, firefox, evolution-data-server. samba (closure): Fedora 44 carries talloc 2.4.4 / tevent 0.17.1; samba 4.25.0 needs >= 2.5.0 / >= 0.17.2. Add libtalloc 2.5.0 and libtevent 0.17.2 as stage 0 gaps. Drop their upstream gpg-verify from %prep: the source pipeline already SHA-512-locks the payload and the detached .tar.asc is not fetched. Verified libtalloc builds to RPM locally. Not addressed here (repo-side, not utah recipes): libicu 77 vs 78 and gpgme multi-version conflicts live in the published Hummingbird repo; Fedora javascriptcoregtk4.1/libcephfs2 still link icu77. Tracked separately.
The first run put co-dependent packages in the same stage, which has no intra-stage ordering, so they resolved against Fedora/Hummingbird instead of each other: - libtevent BuildRequires libtalloc >= 2.5.0; both were stage 0, so libtevent saw only Fedora's talloc 2.4.4 -> 'No match for libtalloc-devel >= 2.5.0'. Move libtevent to stage 1 (libtalloc stays 0). - libphonenumber BuildRequires re2-devel; both were stage 1, so it pulled Fedora/Hummingbird re2, which need abseil .2601 -> unresolved. Move libphonenumber to stage 2 (after abseil 0 and re2 1). - samba needs libtevent -> stage 2. evolution-data-server needs libphonenumber -> stage 3. gstreamer1-plugins-bad-free, webkitgtk and pipewire consume the new stage-1 abseil packages but stay at their current stage; they resolve against the published [factory] repo on the next run once webrtc-audio-processing/re2 publish, per the bootstrap ladder in docs/targeting-hummingbird.md.
publish only fires when all five stages are green, so a wave that built 200 packages and failed on the 201st -- or was cancelled to launch a corrected wave -- published nothing, and the next wave rebuilt the 200. Reuse was keyed on a wave reaching publish, not on a package building. Add an accumulate job that runs after the matrix with if: !cancelled(), so it persists successes even when some package failed. It seeds from ghcr.io/<owner>/utah-packages:building (falling back to :latest, then empty), merges whatever RPMs the matrix produced this run -- a failed job uploads no RPM, so only successes are added -- and pushes back to :building. It does not sign or run the consumer contract: :building is a build cache and may be incoherent, so consumers must never install it. :latest stays the atomic, contract-gated tag publish produces. prepare now seeds its skip list from :building (fall back to :latest, then the Pages repo), so a success persists across waves whether or not its wave ever reached publish. This is what stops the rebuild-everything-again loop after a cancelled wave. :latest and Pages are unchanged: still full-success-gated, still the coherent repository consumers read.
Firefox is by far the longest build in the factory: a full PGO+LTO Gecko compile that dominated wall-clock time and repeatedly hit the runner memory ceiling. It is a leaf application, not a library anything else links, so building it from source buys nothing the Flathub Flatpak does not already give -- and the image already carries the Firefox Flatpak system config hook (99-flatpaks.sh) and lists org.mozilla.firefox in the desktop contract. Drop the firefox RPM from the factory: remove it from upstream-sources.json (no longer built), from bluefin-packages.toml (firefox and firefox-langpacks no longer expected in the image), and delete the recipe. The Flatpak is preinstalled via a new preinstall.d drop-in in the utah image.
The bootstrap ladder could not advance. Same-stage consumers (webkitgtk and gstreamer1-plugins-bad-free need webrtc-audio-processing/re2; those built in the same stage and so were invisible) can only resolve their siblings from a published repo on a later run -- but builds read Pages via FACTORY_REPO, and Pages only updates when a wave reaches publish, which the librsvg2 %check failure prevents. So nothing new ever became visible and the ladder stalled. Seed work/prior from the :building accumulator in every stage. work/prior is already createrepo'd into the [stages] repo the build resolves against, so this makes every success from every prior wave visible to the current build, independent of whether any wave went fully green. webrtc/re2/icu78 published to :building this way let gstreamer1-plugins-bad-free and webkitgtk resolve on the next run, and webkitgtk built against icu78 then unblocks evolution-data-server, whose only remaining conflict is Fedora javascriptcoregtk pulling icu77.
Disable optional OpenCV and ONNX GStreamer plugins that reintroduce Qt6 and the old abseil ABI. Exclude Hummingbird Ruby 3.3 and 3.4 default gems from Ruby-toolchain builddep transactions so WebKitGTK can use Ruby 4 without file conflicts.
Define the global Hummingbird Ruby exclusion before using it and disable optional GStreamer OpenCV and ONNX plugins with the correct bcond semantics.
The reference test binary compares rendered SVGs against pre-rendered PNGs that were generated with the library versions in Fedora's buildroot. Hummingbird ships newer harfbuzz (14.3 vs 12.3), fontconfig (2.18 vs 2.17), and freetype; the font-shaping differences they produce make these 734 pixel-comparison tests fail deterministically. Remove reference.rs and its meson.build entry in %prep so the binary is not built. Every other test suite (api, bugs, errors, filters, geometries, intrinsic_dimensions, loading_crash, loading_disallowed, primitive_geometries, primitives, render_crash, shapes, text) still runs.
gnome-control-center reached libicu through gnome-bluetooth -> bluez-obexd -> libical and hit an unsatisfiable ICU split: Hummingbird still ships libicu-77.1-2.1.hum1 beside libicu 78, and the factory builds icu 78.3 with libical/samba linked against soname .78. Exclude the older Hummingbird libicu-77 NEVR globally so only 78 is selectable. Also extend the workflow quoting guard to the new lane and checkpoint workflows.
Fedora enables vfs_cephfs/vfs_ceph_rgw/ceph_mutex by default on x86_64, which BuildRequires librgw-devel/libcephfs-devel. Those pull libicuuc.so.77 into the buildroot and conflict with the factory libicu 78, and Ceph VFS is not part of the Bluefin desktop contract. Gate the Ceph bconds behind utah_ceph (off by default) so samba links only ICU 78.
A samba built against libicu 77 before the factory moved to 78 lingers in the :building accumulator with the same NEVR as its replacement. In [stages] it is preferred by priority and drags the now-excluded ICU 77 back in, so every buildroot reaching libsmbclient (gvfs, libsoup3, nautilus-python, localsearch) fails to resolve. Drop any prior RPM still requiring the retired ICU 77 soname before building the stages repo; the current run rebuilds a coherent replacement with a matching filename that overwrites it in the accumulator.
Dropping only the ICU-77-linked samba-core-libs left libsmbclient and libsmbclient-devel from the same stale build with unmet private-library deps. Identify stale source packages by ICU 77 soname, then drop every accumulator RPM built from those sources so the replacement set is installed coherently.
gvfs BuildRequires libsmbclient-devel, which only the factory provides once samba (stage 2) is built. At stage 0 gvfs had no coherent libsmbclient in the buildroot -- the stale factory one is purged and Fedora's is excluded by name -- so it could not resolve. Move gvfs to stage 2 so samba is available.
flatpak-selinux pulls python3-policycoreutils, which requires python3-distro, and neither repository had it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015VF8ttMH6WGQHeQ9hdMSY9
flatpak requires flatpak-selinux when selinux-policy-targeted is installed, which pulls policycoreutils-python-utils -> python3-policycoreutils -> python3-setools >= 4.4.0. Hummingbird ships every link of that chain except the last, so its own policycoreutils was uninstallable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015VF8ttMH6WGQHeQ9hdMSY9
Both were solved on fix/repeatable-local-builds (#45) and lost in the port to the Packit shape. Bringing the recipes across rather than rediscovering them. libheif is the one blocking ten packages in the current run. Its ffmpegdec plugin links Fedora libav, and the moment the factory promises its own ffmpeg 9.x the Fedora copy is excluded by name -- so the accumulator libheif becomes uninstallable and takes every buildroot that reaches gdk-pixbuf2, glycin, graphviz or doxygen with it. That is exactly what opus, libthai, libvpx, mpg123, openjpeg, spandsp, libnice, libnma and libtalloc are failing on: package graphviz requires libgdk_pixbuf-2.0.so.0, but none of the providers can be installed ... glycin-loaders requires libheif.so.1 ... The draft answers it with a narrow %bcond ffmpeg 0: the aom and dav1d decoder plugins stay, which is what actually decodes AVIF and HEIC here, and only the ffmpeg HEVC path goes. Narrower than %bcond bootstrap, which would also drop rav1e, SvtEnc and sdl2. tailscale builds from the official static release payload rather than a vendored Go tree, so it no longer depends on the Hummingbird Go version merely to reproduce an upstream artifact. This supersedes the GOEXPERIMENT=nojsonv2 workaround added earlier today, which was treating a symptom: Go 1.27 has moved past the vendored go-json-experiment shim. The spec goes from 1192 lines to 71, the vendor tarball script and the 1.92.5 systray patch go with it, and the source lock points at tailscale_1.98.8_amd64.tgz. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015VF8ttMH6WGQHeQ9hdMSY9
…-processing Reading #45's config/build-lanes.toml rather than rediscovering it. It already records why these three cannot build in the fast lane, and the reasoning holds under the numeric stages this branch uses. libheif now builds with %bcond bootstrap on, permanently. It build-requires sdl2, and sdl2 -> SDL3 -> libdecor -> gtk3 -> gdk-pixbuf2 -> glycin-libs -> glycin-loaders -> libheif closes a cycle. Fedora never trips it because its repository is self-consistent; this accumulator is not. Bootstrap costs exactly one binary, the heif-view example -- the encoders and every library stay. That also retires the %bcond openjph I added earlier today, which dropped the HTJ2K encoder to dodge the same problem. Ordering is the better answer: libheif moves to the wave after openjph, so it links the openjph this factory builds rather than the Fedora 0.25 it then excludes by name. The plugin comes back. ffmpeg and webrtc-audio-processing move with it, for the reason the draft gives: they link libraries the fast lane rebuilds with moved sonames, so building beside them leaves the consumer linked to sonames that never reach the repository. Their own consumers follow one wave later -- pipewire links webrtc-audio-processing, and libepoxy, libglvnd, libayatana-ido, xdg-desktop-portal-gtk and pipewire-libs-extra reach it through pipewire-libs. Stages stay within the five the workflow allows: 296/24/16/6/3. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015VF8ttMH6WGQHeQ9hdMSY9
Seven of the eight stage 0 failures were not package failures at all: Failed to FinalizeArtifact: Received non-retryable error: (403) Forbidden grub2, gtk2, iio-sensor-proxy, liblc3, xkbcomp, xmodmap and xrdb each built their RPMs and then lost them on upload. Every job uploads its debuginfo and debugsource alongside the RPMs, which no BuildRequires ever names and which are more than half the bytes -- #45 already skips them when seeding a local prior for exactly that reason. Exclude them from the artifact so the run stops spending its budget on payload nothing downstream reads. python-evdev is the one real failure. Its %generate_buildrequires runs %pyproject_buildrequires, and that macro has to execute before the dependencies it generates can be resolved -- so with nothing named statically the first pass has nothing to run it with: pyproject-rpm-macros is needed by python-evdev python3-devel is needed by python-evdev python3dist(packaging) is needed by python-evdev and the retry loop then reinstalls what is already installed, three times, and gives up. Name them, the same way python-typing-inspection asks for python3-packaging. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015VF8ttMH6WGQHeQ9hdMSY9
…ed out Sixteen stage 1 packages failed on the openjph knot, and the reason ordering could not untie it was that five waves is not enough to express this dependency graph. openjph, libheif, glycin, gdk-pixbuf2 and then everything reaching gdk-pixbuf2 is already five, before webkitgtk, gjs, evolution-data-server, flatpak or gnome-shell have anywhere to go. fix/repeatable-local-builds solved that with sub-lanes -- stage0_late, stage0_late_b, stage0_late_c, stage1_heavy, stage2_late, stage3_late -- each its own wave with its own boundary. Rather than invent a second answer, take that lane order and flatten it into consecutive numbers here: 1 libheif (stage0_late) 2 webrtc-audio-processing (stage0_late_b) 3 ffmpeg, gstreamer1-plugins-good, xorg-x11-server-Xwayland (stage0_late_c) 5 webkitgtk (stage1_heavy) 7 gjs (stage2_late) 9 evolution-data-server, flatpak, gnome-shell (stage3_late) with the old numeric waves shifted into 4, 6, 8 and 10 around them. The reasoning behind each boundary is recorded in that file and holds unchanged: WebRTC before any consumer whose buildroot resolves PipeWire; libheif before its late consumers; Flatpak after the malcontent-bootstrap provider it needs and before the full malcontent build that needs Flatpak. rebuild-rpms.yml grows rebuild5 through rebuild10 on the same chunked reusable-workflow pattern, and KNOWN_STAGES widens to match so the inventory still refuses a stage no job can resolve. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015VF8ttMH6WGQHeQ9hdMSY9
…after their providers Three of the four failures in run 34337256061 were one bug. The exclude that was meant to keep Hummingbird's older libicu 77 out of the build root never matched: dnf splits a package spec on its dashes before it globs each field, so libicu-77.*hum1 parsed as version "77.*hum1" and matched nothing. localsearch and enchant2 therefore linked libicu 77 on every wave, the ICU purge dropped their RPMs from the accumulator at every consumer, and nautilus fell back to Fedora's localsearch, whose libavformat.so.62 is excluded because the factory builds ffmpeg. nautilus-python failed behind nautilus. Spelling the release as its own field (libicu-77.*-*hum1) is verified locally against Fedora 44 plus Hummingbird: the 77 request answers "matches only excluded packages" and a bare libicu-devel resolves to 78.3. The other two were lane ordering. gnome-shell shared stage3_late with evolution-data-server, which it build-requires, and a lane cannot see its own output, so it resolved Fedora's evolution-data-server against libicu 77 and collided with the factory's libphonenumber. xdg-desktop- portal built in stage 2 against Fedora's flatpak-devel, whose flatpak- libs needs a malcontent-libs that needs libaccountsservice.so.0; the factory's accountsservice ships so.1, so only the flatpak from stage3_late can satisfy it. Both move to stage 4. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D27PMym3vQkeKh2c479fCQ
…iders, build nuspell, and let libvdpau keep TeX Live With libicu 77 finally excluded from the build root, the run showed which stage-0 recipes had been leaning on it through a Fedora dependency: - bluez build-requires libical-devel, and Fedora's libical links libicu 77. The factory builds libical in stage 0, so bluez moves to stage 1. Its own consumers already resolve Fedora's ABI-compatible bluez-libs and are unaffected. - enchant2 build-requires nuspell-devel, and Fedora's nuspell links libicu 77; nothing else provides it, so enchant2-nuspell was an uninstallable subpackage on Hummingbird all along. Import nuspell 5.1.8 from Rawhide into stage 0 and move enchant2 to stage 1, which the WebKitGTK lane still reads. - libvdpau build-requires tex(latex) for the doxygen formulas in vdpau.h, and that resolves to texlive-xetex, which links libicu 77 and which nothing else can provide. libvdpau links no ICU itself. Rather than drop the formulas, a recipe may now declare "buildroot_icu77": true to admit libicu 77 into its build root; the build script then fails the build if any RPM it produced requires libicuuc.so.77 or libicui18n.so.77, so the runtime rule holds whatever the build root held. That output check runs for every package, flag or not. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D27PMym3vQkeKh2c479fCQ
ffmpeg build-requires pkgconfig(smbclient) and gvfs libsmbclient-devel. Fedora's samba-core-libs links libicu 77, which no build root installs any more, so Fedora's libsmbclient-devel can never resolve and the only one that can is the samba this factory builds -- which sat in stage 2, after ffmpeg and beside gvfs. Its chain moves into the stage-0 late lanes: libtalloc and libtdb stay in the fast lane, libtevent joins libheif's lane, samba joins the WebRTC lane, and ffmpeg's lane sees all three. gvfs in stage 2 and gnome-control-center in stage 4 see samba as before, now for real. The lane test records each new provider-consumer pair and checks that a late provider precedes its late consumer by lane, not merely by stage. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D27PMym3vQkeKh2c479fCQ
gstreamer1-plugins-bad-free build-requires pkgconfig(lrdf) for its LADSPA plugin. Fedora's liblrdf needs a raptor2 that links libicu 77, which no build root installs any more -- and the plugin would carry that link into the runtime, where only libicu 78 exists. Import both from Rawhide: raptor2 2.0.15 in the stage-0 fast lane from its upstream release URL, liblrdf 0.5.0 from the Fedora lookaside one lane later so it sees raptor2. gst-bad in stage 1 then sees both. The lane test records the pairing. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D27PMym3vQkeKh2c479fCQ
… sees samba libtevent could not build beside libheif. It needs only libtalloc, but its doxygen resolves graphviz -> gdk-pixbuf -> glycin -> libheif, and in libheif's own lane the only libheif on offer is Fedora's, which asks for the openjph 0.25 the factory replaced. That one failure skipped the WebRTC lane behind it, and with neither WebRTC nor samba built, ffmpeg, gstreamer1-plugins-good, pipewire, gtk4 and everything downstream fell over in run 34422700686. Three late lanes cannot hold this chain: libheif must precede libtevent, libtevent samba, and samba ffmpeg. Add rebuild0_late_d, cloned from the lane before it and threaded through every needs list, prior pattern and the publish gate, and lay the lanes out as libheif and liblrdf; WebRTC and libtevent; samba with the WebRTC consumers; ffmpeg. The lane test now checks four lanes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D27PMym3vQkeKh2c479fCQ
…om the runners download.librdf.org answered from a workstation and timed out three times from a GitHub runner, which failed raptor2 in run 34435888560 and would have skipped every stage-0 late lane behind liblrdf. The Fedora lookaside copy is the same archive by SHA-512; list it as an availability fallback, which the pipeline verifies against the same digest. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D27PMym3vQkeKh2c479fCQ
Run 34436611943 built all 335 packages and failed only the publish gate: the Hummingbird-only transaction could not install ntfs-3g-libs, which requires libhd.so.23. ntfs-3g build-requires hwinfo-devel, and both sat in stage 0, so ntfs-3g resolved Fedora's hwinfo while the factory's hwinfo 25.5 provides a newer soname. Stage 1 sees the factory's copy; nothing build-requires ntfs-3g. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D27PMym3vQkeKh2c479fCQ
The reference suite renders SVGs and compares them pixel by pixel against images rendered on Fedora, failing at max_diff > 2, so it tests the font stack as much as it tests librsvg. Hummingbird ships harfbuzz 14.3 against Fedora 12.3 and fontconfig 2.18 against 2.17, and the shaping differences make it fail deterministically: bug_985_image_rendering_property at 372960 pixels changed with a maximum difference of 6, and text-text-03-b at 12 pixels changed with a maximum difference of 255. The reference images were rendered against different fonts; the library is fine. Every other suite -- api, bugs, errors, filters, geometries, text -- still runs, now serialized (--jobs=1, RUST_TEST_THREADS=1, --num-processes 1) with a doubled timeout, which is also what the parallel-run 180s timeouts asked for. Follows the approach in the draft PR #45. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W6BYLUD6KBzF8rBFXKjP7M
hanthor
left a comment
There was a problem hiding this comment.
Confirming the state of this draft for triage purposes — no action requested, it is doing what its description says.
It does not merge, as expected. mergeable_state: dirty; locally git merge pr/45 produces 14 conflicting files. Base is 9dc62b5, main is now 54cc8d1. Three-dot diff is 1224 files, +103554/−13412, 121 commits.
The portability assessment in the description has largely been acted on. Checking each item against the current open queue:
- "~153 package recipes, 40 of which
mainstill lacks" — carried by #51 (156 package dirs) and #70 (161). Both merge cleanly intomainand both pass every gate (validated 344and341 source RPMsrespectively, against a 193 baseline). - "tailscale built from the official static release payload" — #70 and #86 both address tailscale on
main's shape; #86 withGOEXPERIMENT=nojsonv2and the[unavailable]removal. - "
v4l-utilswithout its Qt viewers;mdadmwithout the ABRT hook" — #51 carries both, moved into the specs since the inventory has norpm_definesfield. - "
no_upstream_sourcesupport forcolor-filesystem" — carried by #51. - "
libheifwith its ownbootstrapbcond" —libheifis in both #51 and #70, and is also one of the 41 packages #81 overlaps with them on.
So the portable half has been ported. The non-portable half (config/build-lanes.toml, tools/seed-build-prior.sh, tools/compose-local-repository.sh, everything hanging off tools/build-package.sh) remains non-portable, as described.
The findings section is the part still carrying unique value, and none of it is captured anywhere else I can find in this repo:
- Hummingbird's
cmakebeing uninstallable (libjsoncpp.so.26required, onlyso.27provided) - No
flatpak,systemd-resolvedorcryptsetupin Hummingbird's bootable base, and no terminal emulator at all while Bluefin's own image test assertsptyxis - The installed ESP lacking
\EFI\BOOT\BOOTX64.EFI, so the disk only boots from the NVRAM entry
Those are cross-repo facts about Hummingbird and about projectbluefin/utah's image test, not about this branch. They would survive this PR being closed only if they are filed as issues. Worth doing before this gets garbage-collected.
One relationship worth recording. #70's tip commit (librsvg2: drop the reference-image suite, serialize the rest) explicitly says "Follows the approach in the draft PR #45" — so this branch is still actively serving as the reference it was opened to be. That argues for leaving it open as a draft rather than closing it, at least until #70 lands.
Note for anyone comparing this to #30: #30 is the same pre-Packit lineage (merge base 66fa022, 1139 files, 45 commits, 14 merge conflicts) but is not marked draft and carries an lgtm label, while its title claims only "unblock 6 build failures". This PR's description is honest about what it is; #30's is not. I have commented there separately.
Generated by Claude Code
|
Closing: this draft was opened to preserve the pre-Packit work, and #70 ( Generated by Claude Code |
Draft — opened to preserve this work, not to merge as-is.
This branch and
mainforked from66fa022on 31 Aug and developedindependently.
mainmigrated the factory to Packit + Mock; this branch keptbuilding on the podman/
build-package.shmodel and used it to get a Utahimage, ISO and encrypted install working end to end. Neither deleted the
other's work —
packages/ffmpeg,tools/build-package.shandconfig/build-lanes.tomlhave zero commits onmain, and this branch's tipis not an ancestor of it.
I am opening this as a draft so the result is visible and recoverable while
the Packit migration settles. The intent is to port the portable half onto
main's shape rather than merge this diff.What it achieved
Utah now builds, installs and boots. Verified locally, not in CI:
output/utah-live.iso, 7.7G, boots to a GNOME sessionembedded container store, and the installed system boots, unlocks and
reaches a desktop a user can log in to
Screenshots of each step are in
docs/verification/on the companionprojectbluefin/utah branch.
What is portable to
mainmainstill lacks and Utah'stransaction demonstrably needs:
flatpak,appstream,libfyaml,setools,xorg-x11-server-Xwaylandand its X11 chain,hunspell+dictionaries,
gcr3,gnome-keyring,openjph,soxr,hidapi,desktop-file-utils,cryptsetup-adjacent leaves and others.from the official static release payload instead of a vendored Go tree that
cannot compile against Hummingbird's toolchain;
v4l-utilswithout its Qtviewers;
mdadmwithout the ABRT hook;libheifwith its ownbootstrapbcond; and an importer fix so a
Version:line carrying a%globalmacrois recorded expanded rather than verbatim.
no_upstream_sourcesupport for a recipe with no archive at all(
color-filesystem, whichcolordrequires).What is not portable
Everything built on machinery
maindoes not have:config/build-lanes.tomlstaging,
tools/seed-build-prior.sh, and thetools/compose-local-repository.shfixes. Those extendtools/build-package.sh, which the Packit migration replaced. They should bere-proposed against Mock or dropped.
Findings worth keeping regardless
cmakeis uninstallable: every build there requireslibjsoncpp.so.26while its onlyjsoncppprovidesso.27.flatpak,systemd-resolvedorcryptsetup, and packages no terminal emulator at all (noptyxis,vte291orgnome-console) — while Bluefin's own image test assertsptyxis.\EFI\BOOT\BOOTX64.EFIfallback, so the disk onlyboots from the NVRAM entry the installer writes.
🤖 Generated with Claude Code
https://claude.ai/code/session_015VF8ttMH6WGQHeQ9hdMSY9