Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix rpmsign --key-id regression #3423

Merged
merged 1 commit into from
Nov 6, 2024

Conversation

pmatilai
Copy link
Member

@pmatilai pmatilai commented Nov 4, 2024

Commit d99186f failed to update the popt alias to the new macro. So --key-id worked only if you hadn't set %_openpgp_sign_id in your rpm macro config - the prime case for wanting to use --key-id to override that choice. Doh. Just goes to show what you don't test, really is broken by definition...

@pmatilai pmatilai requested a review from a team as a code owner November 4, 2024 10:33
@pmatilai pmatilai requested review from ffesti and removed request for a team November 4, 2024 10:33
@pmatilai
Copy link
Member Author

pmatilai commented Nov 4, 2024

(gah, sure is Monday when you need so many fixups to messages etc for a patch this small)

@pmatilai pmatilai changed the title Fix rpmsign --key-id with Sequoia Fix rpmsign --key-id regression Nov 5, 2024
@pmatilai
Copy link
Member Author

pmatilai commented Nov 5, 2024

All those edits and it was still wrong: just now realized the breakage wasn't limited to Sequoia, it occurred with Gpg too, so commit summary+message updated.

Commit d99186f failed to update
the popt alias to the new macro. So --key-id worked only if you
hadn't set %_openpgp_sign_id in your rpm macro config - the prime
case for wanting to use --key-id to override that choice. Doh.
Just goes to show what you don't test, really is broken by definition...
@ffesti ffesti merged commit 3c06b9e into rpm-software-management:master Nov 6, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants