refactor: keel-archive-keyring is built from keel-keys #7
No reviewers
Labels
No labels
accessibility
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/keel-transition!7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refactor/keyring-moves-to-keel-keys"
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?
Handbook decision 0055 moves the
keel-archive-keyringpackage to Keel-Linux/keel-keys (Keel-Linux/keel-keys#1). This pull request removes the copy here.What changes
debian/control: thekeel-archive-keyringstanza and thegnupgbuild dependency are removed. keel-transition depends onkeel-archive-keyring (>= 0.2.0). Before, it depended on>= ${source:Version}, and no keyring of version 0.2.1 exists.debian/rules: the keyring build and its fingerprint check are removed. keel-keys does that check now, for each role.debian/keel-archive-keyring.install,keys/and the copyright stanza ofkeys/are removed.tests/helpers.bash:install_keyringwrites a throwaway key and its fingerprint. 3 tests compare with$KEYRING_FPR, not with the project fingerprint.What does not change
keel-transition reads
/usr/share/keyrings/keel-archive-keyring.gpgand/usr/share/keel-archive-keyring/fingerprint. keel-keys keeps both paths. The fingerprint file keeps the main fingerprint only.lib/has no change.