"Build it yourself" copies binaries from the builder's home directory #59
No reviewers
Labels
No labels
P0
P1
P2
P3
audio
bakery
boot
breadbug
bug
build
ci
dependencies
design
disk
docs
encryption
final
firewall
graphics
hardware
idle
installer
keybinds
nvidia
packages
phase-1
polish
recovery
reliability
reproducibility
secure-boot
security
shell
signing
snapshots
supply-chain
swap
tech-debt
theming
ux
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/bos!59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/bos-37-pinned-bakery-binaries"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Local ISO builds now run
scripts/ci-stage-bakery.pyinto a temporaryLAPTOP_HOMEby default, so binaries come from the signed index and lockfile pins. The temporary home is removed on exit.BAKE_FROM_HOME=1preserves the builder's installed versions for development, and CI continues using its separately staged home.The build writes a temporary
GPGDirinto its staged pacman config and removes it on exit. Repository key trust and local signatures stay out of the host pacman keyring. Updated stale comments inbuild-local.shand the lockfile header to describe the pinned staging default. README and the Unreleased changelog describe the default and override.Updated stale bakery, bread-theme, and breadpaper lockfile pins to their current signed stable-index versions, following the lockfile's pin refresh policy.
Verified shell syntax, Python compilation, and
git diff --check. A clean Arch container completed aFAST_BUILD=1ISO build without bread tools installed. The signed index verified, all 19 required/usr/local/binbinaries in the ISO matched signed-index SHA-256 values and lockfile versions, the host keyring did not acquire the[breadway]key, and the temporary GPGDir was removed. mkinitcpio emitted its existing missingnbd-clienthook warning, but the ISO build completed successfully.The public BOS landing page copy is in Breadway/bos-site PR #4, stacked on source import PR #1. Merge the site PRs and publish the static page before marking BOS-37 DONE.
Closes #37
Independent site-source review found PR #1 changes
data/projects.tomlin the obsolete Zola catalog, which has no CI or deployment path. It does not update the live BOS site, served from the separateBOS Website [bos.breadway.dev]checkout. The BOS issue's site-copy acceptance therefore remains unmet. Keep this issue open until the live source has a reviewable change and the published page is verified.Independent re-review of PR #59 at
0af7f8af4f53da3f9a5f1c9e5758981ca59b36c0Acceptance mapping: the default local build stages signed, lockfile-pinned bakery binaries through
build-local.sh:143-154;BAKE_FROM_HOME=1and CI's existing staged-home path are covered atbuild-local.sh:143-148. Temporary GPGDir setup and cleanup keep trust changes out of the host keyring atbuild-local.sh:28-41,74-81. The README, lockfile comments, package pins and Unreleased changelog are in the diff. The clean Arch ISO evidence on BOS-37 reports all 19 required binaries match signed-index hashes and lockfile versions, with no new host keyring trust.The BOS-site copy is separately reviewed in PR #4 at
index.html:1447,1451, but is stacked on site PR #1 and is not yet published. Forgejo reports no CI statuses for PR #59; it is mergeable. BOS is release-sensitive, so this is a recommendation for the maintainer and I have not merged. BOS-37 remains open until the site stack is landed and published.Independent re-review
The current PR #59 head remains
0af7f8af4f53da3f9a5f1c9e5758981ca59b36c0. Acceptance mapping:build-local.sh:143-153. The recorded clean Arch acceptance checks all 19 ISO binaries against the signed index and pins.BAKE_FROM_HOME=1uses the builder's installed bakery versions, while CI retains its separately staged home:build-local.sh:143-148,README.md:134-153.build-local.sh:30-41,74-80. The recorded acceptance confirms the host keyring remained unchanged.No CI statuses are configured for this BOS PR. Forgejo reports it mergeable. Code review is complete, but BOS is release-sensitive so the merge remains with the maintainer. BOS-37 stays in TODO because PR #1 needs the deployment target privacy rework noted on that PR; do not mark the parent issue done before the site PRs are safely merged and the page is verified live.