Bug 1320214 - perl.req does not find `perl(strict)' in /usr/share/perl5/ExtUtils/ParseXS.pm
Summary: perl.req does not find `perl(strict)' in /usr/share/perl5/ExtUtils/ParseXS.pm
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rpm
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Florian Festi
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 15:01 UTC by Karel Srot
Modified: 2016-11-04 04:39 UTC (History)
1 user (show)

Fixed In Version: rpm-4.11.3-18.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1268021
Environment:
Last Closed: 2016-11-04 04:39:01 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2359 0 normal SHIPPED_LIVE rpm bug fix and enhancement update 2016-11-03 13:49:15 UTC

Description Karel Srot 2016-03-22 15:01:24 UTC
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.

Comment 1 Karel Srot 2016-04-21 06:08:38 UTC
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.

Comment 5 errata-xmlrpc 2016-11-04 04:39:01 UTC
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


Note You need to log in before you can comment on or make changes to this bug.