Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.