What does it mean if two debuginfo packages create the same dwz build ID file?

[Richard W.M. Jones]

On Sat, Sep 14, 2013 at 01:48:52PM +0200, Jan Kratochvil wrote:
> On Sat, 14 Sep 2013 11:56:26 +0200, Richard W.M. Jones wrote:
> >   /usr/lib/debug/.build-id/da/39a3ee5e6b4b0d3255bfef95601890afd80709.debug
> > which is a symlink to:
> >   /usr/lib/debug/.dwz/ocaml-pcre-7.0.2-5.fc21.x86_64
> [...]
> >   /usr/lib/debug/.build-id/da/39a3ee5e6b4b0d3255bfef95601890afd80709.debug
> > which is a symlink to:
> >   /usr/lib/debug/.dwz/ocaml-gettext-0.3.4-11.fc21.x86_64
> > 
> > Obviously this prevents me from installing both debuginfo packages at
> > the same time.
> 
> The problem is these two files have exactly the same content so they get the
> same build-id (which is a content hash - to be deterministic across builds).

What I didn't understand is what these /usr/lib/debug/.dwz/* files
are.  Are they related to some files that we're building and how?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v