Comment 17 for bug 934420

You are running a heavily patched custom build of RPM5 on
an operating system that I cannot type "make install" from CVS.

I also do not have any access to a a machine or VM on which
to attempt a reproducer, largely because lack of "make install"
prevents meaningful rpm development.

You also have not stated what you expect (or what is wrong), nor
attempted/reported any of the detailed debugging steps that I have
already given you.

And this is db60 not db53. We both know that using db52 works reliably,
which would seem to indicate a change in Berkeley DB, not rpm, is the root
cause of the problem.