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

Michal Domonkos notifications at github.com
Mon Apr 20 13:37:39 UTC 2026


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

> How about:
> 
>     4. detect the wrong lock type use and take a keystore lock if so
> 
> 
> This would happen in the `rpmtxn*()` operations, so they would effectively use the correct lock internally. The old API users would just redundantly lock the transaction also.

But I guess that still leaves us with the question of "how do we manage the transition itself". For that, I agree with the gradual approach that you described.

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

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


More information about the Rpm-maint mailing list