You were asking for a reproducer, I've provided one.
The issue applies to both db53 & db60, so whichever being used isn't really relevant.
From what I can see, the issue seems to only be triggered when having a large enough rpmdb (which is what I suspect why it is that you cannot reproduce the issue easily with buildbots), hence why I provided a copy of mine and a sample package to test with in order to reproduce the issue.
AFAIK it shouldn't be dependent on mandriva specific rpm package.
Whether there's a bug in rpm or bdb isn't really that relevant to the matter, it's still a blocker bug for using > db52 with rpm that needs to be fixed (wherever) regardless of..
You were asking for a reproducer, I've provided one.
The issue applies to both db53 & db60, so whichever being used isn't really relevant.
From what I can see, the issue seems to only be triggered when having a large enough rpmdb (which is what I suspect why it is that you cannot reproduce the issue easily with buildbots), hence why I provided a copy of mine and a sample package to test with in order to reproduce the issue.
AFAIK it shouldn't be dependent on mandriva specific rpm package.
Whether there's a bug in rpm or bdb isn't really that relevant to the matter, it's still a blocker bug for using > db52 with rpm that needs to be fixed (wherever) regardless of..
The workaround provided by Mark Hatle at http:// rpm5.org/ community/ rpm-devel/ 5393.html seems to be working though.
Dunno what more information or anything that I can provide...