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.
It seems to me that this bug is present on RHEL-7 too, at least the respective test is failing. Please double check if the fix is needed.
rpm-4.11.3-17.el7
+++ This bug was initially created as a clone of Bug #1268021 +++
rpm-4.8.0-47.el6 fails to find `perl(strict)' in /usr/share/perl5/ExtUtils/ParseXS.pm:
# /usr/lib/rpm/perl.req /usr/share/perl5/ExtUtils/ParseXS.pm
perl >= 0:5.006
perl(Config)
perl(Cwd)
perl(Exporter)
perl(File::Basename)
perl(File::Spec)
perl(Symbol)
perl(re)
perl(vars)
While perl.req from rpm-4.8.0-38.el6_6 works as expected:
# /tmp/perl.req /usr/share/perl5/ExtUtils/ParseXS.pm
perl >= 0:5.006
perl(Config)
perl(Cwd)
perl(Exporter)
perl(File::Basename)
perl(File::Spec)
perl(Symbol)
perl(re)
perl(strict)
perl(vars)
The relevant /usr/share/perl5/ExtUtils/ParseXS.pm text is:
#########################################################
package
ExtUtils::ParseXS::CountLines;
use strict;
use vars qw($SECTION_END_MARKER);
This is regression introduced in rpm-4.8.0-39.
--- Additional comment from Petr Pisar on 2015-10-01 11:08:33 EDT ---
Introduced with this dist-git commit in rhel-6.7 branch:
commit 44a05c812bec74726890a74650f06c6d425ce489
Author: Lubos Kardos <lkardos>
Date: Wed Feb 18 13:51:59 2015 +0100
- Add check if source files aren't too big for payload
- Resolves: #833427
- Fix producing bogus dependencies by perl.req
- Resolves: #1024517, #1026750
- Fix color skipping of multiple files with the same content
- Resolves: #1170124
- Disable curl globbing for remote retrievals
- Resolves: #1076277
- Make rpm-build depend on redhat-rpm-config provide
- Resolves: #1122100
- Handle directory replaced with a symlink to one in verify
- Resolves: #1158377
- Restore default SIGPIPE handling for build scriptlets
- Resolves: #993868
- State --setperms and --setugids are mutually exclusive
- Resolves: #1119572
- Fix byteorder for 64 bit tags on big endian machines
- Resolves: #1040318
- File mode from %%defattr is applied to directories with warning
- Resolves: #997774
- If an error occurs during printing log message then print the error on stderr
- Resolves: #1139444
- Error out on more than one --pipe option
- Resolves: #966093
- Extend PKG_CONFIG_PATH instead of override
- Resolves: #921969
--- Additional comment from Petr Pisar on 2015-10-01 11:11:15 EDT ---
I found it when building perl into rhel-6.7.z to fix bug #1267920. It also removed some other autogenerated run-requires. See <https://errata.devel.redhat.com/rpmdiff/show/132064?result_id=3380073> for full listing.
I have reported this exact issues in bug 1324032#c7 so I guess we could eventually closed this bug as a duplicate. I will let this up on to Florian's preference.
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-2359.html