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.

Bug 1026750

Summary: perl.req produces bogus dependencies
Product: Red Hat Enterprise Linux 6 Reporter: Konstantin Lepikhov <klepikho>
Component: rpmAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED ERRATA QA Contact: Marek Marusic <mmarusic>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: ffesti, jbuchta, jherrman, jzeleny, ksrot, lkardos, mmarusic, mtessun, packaging-team-maint, pmatilai
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: rpm-4.8.0-40.el6 Doc Type: Bug Fix
Doc Text:
Under certain circumstances, the rpm utility incorrectly required the /proc file system to be mounted, and using rpm failed with the following error: warning: Failed to read auxiliary vector, /proc not mounted? With this update, the /proc file system is only required for appropriate RPM operations, and the described failure no longer occurs.
Story Points: ---
Clone Of:
: 1191124 (view as bug list) Environment:
Last Closed: 2015-07-22 07:03:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 994246, 1075802    
Attachments:
Description Flags
example code for testing none

Description Konstantin Lepikhov 2013-11-05 11:09:39 UTC
Description of problem:
Parser that generates rpm "Requires:" can generate fake dependencies in case it finds "use something" string in the script. 

Version-Release number of selected component (if applicable):
rpm-4.8.0-32.el6.x86_64

How reproducible:
Always 

Steps to Reproduce:
$ /usr/lib/rpm/perl.req ./mysql_install_db

Actual results:
perl(Data::Dumper)
perl(Fcntl)
perl(File::Basename)
perl(File::Copy)
perl(Getopt::Long)
perl(Sys::Hostname)
perl(hostnames)
perl(strict)


Expected results:
perl(Data::Dumper)
perl(Fcntl)
perl(File::Basename)
perl(File::Copy)
perl(Getopt::Long)
perl(Sys::Hostname)
perl(strict)

Additional info:
$ yum search perl\(hostnames\)Loaded plugins: langpacks, refresh-packagekit
Warning: No matches found for: perl(hostnames)
No matches found

Comment 1 Konstantin Lepikhov 2013-11-05 11:10:30 UTC
Created attachment 819659 [details]
example code for testing

Comment 6 Florian Festi 2014-12-15 12:26:48 UTC
Patch available upstream

Comment 12 errata-xmlrpc 2015-07-22 07:03:02 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-2015-1452.html