feat: keel.sources trusts the testing keyring for trixie-testing #54
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/common!54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/keel-testing-keyring"
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?
Step 6 of decision 0055: the trixie-testing stanza of keel.sources names the testing keyring,
/usr/share/keyrings/keel-testing-keyring.gpgfrom keel-archive-keyring 0.3.0.keys/keel-testing-keyring.asc: the public testing key, the same file as keel-keyskeys/keel-trixie-testing.asc.mk/turnkey.mkcopies it into the bootstrap.conf/bootstrap_aptnames it in the trixie-testing stanza.overlays/turnkey.d/keel-apt: the shipped keel.sources nameskeel-testing-keyring.gpgfor trixie-testing.conf/turnkey.d/keel-apt: stops whenkeel-testing-keyring.gpgis missing, changes the.ascname to the.gpgkeyring, removes the bootstrap copy, and stops an image of the testing track whose stanza names another keyring.The archive signs trixie-testing with the main key and the testing key for now (Keel-Linux/apt#31). So an appliance with the old stanza continues to work, and an image with the new stanza works too. The main key is removed from the suite later, when no reader has the main keyring alone.
Tests: written first, in
tests/apt-sources.bats.8783912b219aaabc60d4