[Rpm-maint] [rpm-software-management/rpm] Implement a separate lock for the keystore (PR #4123)

[Panu Matilainen]

pmatilai left a comment (rpm-software-management/rpm#4123)

The only external thing using this API *that I'm aware of* is libdnf5-plugin-expired-pgp-keys which we can fix easily enough. But then that usage is also "mostly harmless" even if its locking the wrong thing, but since we're still defaulting to the rpmdb as keystore, it's not like it'll run lockless in the default case.

My suggestion, formed while typing the above :smile:, is that we open a ticket to do this gradually: let it just silently be wrong now, add a warning in 6.1, and make the break explicit on the next soname bump. If the soname bump happens in 6.1 already we'll just skip the warning phase.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/4123?email_source=notifications&email_token=ADLPZU4A76STLLVP6CUL64D4TN7YNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGA4TAMBQGY3KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOS2XA4S7MNXW23LFNZ2F633QMVXF6Y3MNFRWW#issuecomment-4160900066
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/4123/c4160900066 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20260331/a656f9ad/attachment-0001.htm>