AppImage bootstrap cannot retry a PPA enrollment after its signing-key request fails #2266
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#2266
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Problem
The AppImage's System packages step retries the whole bootstrap, but a partial PPA enrollment can prevent those retries from reaching the operation that repairs it.
In this current-source run,
add-apt-repositorywrote the toolchain PPA source and then received HTTP 504 fetching its signing key. Both later attempts stopped at the initialapt-get updatewithNO_PUBKEY, beforeadd-apt-repositorycould retry the key request. No compilation started.Authored reproduction
I executed the actual workflow shell at main
49f75dc8with stand-ins for apt, PPA enrollment and sleep. The first enrollment creates the source and fails fetching its key; a second enrollment would succeed. Index refresh refuses that unverified source.The resulting calls are:
The script exits 100 with one PPA attempt, even though the endpoint is available afterward. No network or real package command runs in the fixture.
Intended recovery
Bootstrap the base prerequisites separately, then retry PPA enrollment/repair before its signed-index refresh and dependent installations. Keep bounded retries, the failing status and all signature checks. Do not trust the incomplete source or weaken apt authentication.
S0 for blocked AppImage packaging; Linux reach 0.17 upper bound, confidence 1.0 for the observed CI failure and authored stateful reproduction. This is a bootstrap recovery failure, not a claim of a gameplay crash. Open-PR title search found no matching recovery work; coordination will be recorded before implementation.
I'm taking the recovery in #2266. The actual workflow shell reproduces the partial-source/missing-key trap with stateful stand-ins. S0 for blocked packaging, Linux reach 0.17 upper bound, confidence 1.0 for that fixture and the observed CI failure. Bounded retries and signed-index verification stay intact. Claimed in dev-work before production edits.