I agree --exportdb should work on read-only fs. Unprivileged user is a
different matter, we can't really let unprivileged user to block system updates
through ro-locking.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
rpmdb --exportdb calls rpmtxnBegin() with RPMTXN_READ flags. Internally that
function calls rpmlockNew() and rpmlockAcquire(). Neither function has a flags
parameter to specify what kind of lock is requested. rpmlockNew() automatically
creates a read lock if it can't open the .rpm.lock file in
