Re: pld rpm 5.4.17

> > I’m sure your analysis is correct … > > … meanwhile what was the core issue? What problem are you trying to solve? > > Issues relating to whether a cursor COULD (or SHOULD) read uncommitted data > are quite complex, including whether the flags are inherited from the > database open > and

Re: pld rpm 5.4.17

> On Feb 24, 2017, at 5:03 PM, Jakub Bogusz wrote: > >>> >> >> Update: still the same with uid>0 (no write permission to /var/lib/rpm). >> It seems that DB_READ_COMMITTED and DB_READ_UNCOMMITTED require +w, >> so they should be filtered out in unprivileged mode. > >

Re: pld rpm 5.4.17

On Wed, Feb 22, 2017 at 10:02:17PM +0100, Jakub Bogusz wrote: > On Tue, Feb 21, 2017 at 09:51:13PM +0100, Jakub Bogusz wrote: > > On Tue, Jan 10, 2017 at 09:36:24PM +0200, Elan Ruusamäe wrote: > > > not cool. > > > > > > $ rpm -q rpm > > > BDB0056 DB->cursor: DB_READ_COMMITTED,