Description of problem
======================

With some packages, upgrading when also -debuginfo / -devel package is installed leads to problem with symlinks, as later reported by --verify.  This does not seem to affect ability to upgrade the main package.

For example, upgrade of libvpd from rhel7.0 to rhel7.1 is affected by this so that: if libvpd and libvpd-devel are both present, upgrading and checking with rpm --verify shows problem:

    # rpm --verify "libvpd-*"
    ....L....    /usr/lib64/libvpd-2.2.so.2
    ....L....    /usr/lib64/libvpd_cxx-2.2.so.2


According to libvpd maintainer, there's nothing wrong with libvpd.spec, so the problem is likely in RPM itself.


Version-Release number of selected component (if applicable)
======================

rpm-4.11.1-16.el7


How reproducible
================

Always with certain packages


Steps to Reproduce
==================

    rpm -i libvpd-2.2.1-3.el7.ppc64.rpm libvpd-devel-2.2.1-3.el7.ppc64.rpm
    rpm -U libvpd-2.2.4-1.el7.ppc64.rpm libvpd-devel-2.2.4-1.el7.ppc64.rpm
    rpm --verify "libvpd-*"


Actual results
==============

    ....L....    /usr/lib64/libvpd-2.2.so.2
    ....L....    /usr/lib64/libvpd_cxx-2.2.so.2


Expected results
================

(nothing)


Additional info
===============

I'm not sure about other packages that might be affected by this.  Scenario described in bz#1126795 is sort of similar, but there --verify complains about files from s390utils-debuginfo and problem is triggered if *other* (from unrelated packages) debuginfos are present.

Note that libvpd is ppc64-only so you will need ppc64 machine for investigation.

Also I was not able to make RPM explain what exactly is the problem with paths, i.e. where the links *should* point.