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.
find-provides.libtool contains following condition:
if grep -iq '^# Generated by ltmain.sh' "$possible" 2> /dev/null ; then
echo "libtool($possible)"
fi
This used to work with older versions of libtool as they are in RHEL6. The new libtool version seems to generate this .la file with following header:
# Generated by libtool (GNU libtool) 2.4.2
This leads to no libtool(something) provides being generated. As an example you can take apr-util-devel package in rhel6 and rhel7.
Obviously find-provides.libtool is incorrect then.
OTOH any package that ends up invoking the old find-provides* scripts could be considered buggy, as those scripts are not really maintained anymore, the old external dependency generator shouldn't really be used anymore.
Then again, the equivalent script invoked by the internal dependency generator in rpm shares this same bug. What a lovely mess...
Comment 4RHEL Program Management
2014-03-22 06:05:57 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Hmm, as the script that should actually be used is in the rpm package I reassign this to rpm and fix it there. Please clone back if you really need to get find-provides.libtool fixed.
Florian,
according to my findings
/usr/lib/rpm/redhat/find-provides.libtool
is in the redhat-rpm-config package, not rpm. This bug seems to be filed against wrong component.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2372.html
find-provides.libtool contains following condition: if grep -iq '^# Generated by ltmain.sh' "$possible" 2> /dev/null ; then echo "libtool($possible)" fi This used to work with older versions of libtool as they are in RHEL6. The new libtool version seems to generate this .la file with following header: # Generated by libtool (GNU libtool) 2.4.2 This leads to no libtool(something) provides being generated. As an example you can take apr-util-devel package in rhel6 and rhel7.