Comment 3 for bug 923631

I don't believe Christophe Fergeau really fixed: I've watched/explained
this problem for years (and I believe I remember the bug report where
the claim of "fix" was made).

The near term fix is to get debugedit.c out of rpm somehow. The code
ended up in RPM because RPM was one of the first applications to
use elfutils, the code was actually embedded in RPM sources before
being packaged (which I also was responsible for).

So debugedit.c chased elfutils and the code sits and rots: producing
-debuginfo is "rpm therapy" intensive, several e-mail exchanges this month
and that is typical.

The longer term answer uses a distributed store for debugging symbols
indexed by buildid and path and ripping Berkeley DB out of gdb and
other tools that are linking rpm libraries for no sane reasons, creating
application contention (like with abrt) for an rpmdb for no sound
engineering reason. The world is full of "Berkeley DB haters" and
the engineering choices are creating locking contention and
deadlock watchdog's to keep applications running when colliding
on accessing an rpmdb. Ditto SElinux and systemtap.

Diffing @rpm.org code against @rpm5.org hurts little. Note that
the main difference is whether NSS or BeeCrypt is used for digests:
which creepy-toe library is used is only a part of a much larger puzzle.