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.
Bug 1492742 - perl-Getopt-Long RPM does not Provide perl(newgetopt.pl)
Summary: perl-Getopt-Long RPM does not Provide perl(newgetopt.pl)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: perl-Getopt-Long
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: perl-maint-list
QA Contact: Mirek Długosz
URL:
Whiteboard:
Depends On:
Blocks: 1481811
TreeView+ depends on / blocked
 
Reported: 2017-09-18 14:43 UTC by Sebastian Ahndorf
Modified: 2018-05-25 11:08 UTC (History)
10 users (show)

Fixed In Version: perl-Getopt-Long-2.40-3.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-04-10 12:06:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
perl-Getopt-Long.spec.patch (381 bytes, patch)
2017-09-18 14:43 UTC, Sebastian Ahndorf
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1366724 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHBA-2018:0752 0 None None None 2018-04-10 12:06:20 UTC

Internal Links: 1366724

Description Sebastian Ahndorf 2017-09-18 14:43:00 UTC
Created attachment 1327499 [details]
perl-Getopt-Long.spec.patch

Description of problem:
newgetopt.pl has been removed from perl-Perl4-CoreLibs-0.003-7.el7 because it is already included in perl-Getopt-Long, but perl-Getopt-Long-2.40-2.el7 does not have a related "Provides:" lines in it's spec file.
Therefore package installation of rancid (epel) will fail due to missing dependencies.

Version-Release number of selected component (if applicable):
2.40-2.el7

Rebuilding the perl-Getopt-Long RPM with attached patch to spec file should fix this problem.

Comment 2 Petr Pisar 2017-09-19 08:21:12 UTC
You are right. The provide should be added into perl-Getopt-Long.

Comment 6 Helge Wiethoff 2017-11-15 10:59:31 UTC
Any progress in this?

Comment 7 Branislav Náter 2017-11-15 16:11:43 UTC
(In reply to Helge Wiethoff from comment #6)
> Any progress in this?

Hi, this bug is scheduled for rhel-7.5 that is currently at the beginning of testing phase and preliminary release date is 2018-03-27.

Comment 11 errata-xmlrpc 2018-04-10 12:06:07 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://access.redhat.com/errata/RHBA-2018:0752


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