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 1235623

Summary: /bin/python dependency makes python update fail
Product: Red Hat Enterprise Linux 7 Reporter: adam winberg <adam.winberg>
Component: yumAssignee: Valentina Mukhamedzhanova <vmukhame>
Status: CLOSED ERRATA QA Contact: Stefan Dordevic <sdordevi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: admiller, emrakova, extras-qa, giuseppe.ragusa, james.antill, jorton, jzeleny, novyjindrich, olivier.lahaye1, rvokal, sdordevi
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: yum-3.4.3-135.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1117878
: 1344697 (view as bug list) Environment:
Last Closed: 2016-11-04 05:29:01 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: 1295396    

Description adam winberg 2015-06-25 10:54:42 UTC
+++ This bug was initially created as a clone of Bug #1117878 +++

Description of problem:

Package built with dependency for "/bin/python" makes update of python package fail:

Error: Package: pygrib-2.0.0-1.x86_64 (@/pygrib-2.0.0-1.x86_64)
           Requires: /bin/python
           Removing: python-2.7.5-16.el7.x86_64 (@anaconda/7.0)
               Not found
           Updated By: python-2.7.5-18.el7_1.1.x86_64 (rhel7-updates)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Comment 2 adam winberg 2015-06-25 11:08:49 UTC
I can add that the 'pygrib' package contains python files with shebang:
#!/usr/bin/env python

which I guess makes rpm autorequire /bin/python

Comment 5 Giuseppe Ragusa 2015-12-18 16:16:13 UTC
Verified as still present while trying to upgrade from CentOS 7.1 to CentOS 7.2

I can confirm that (as per comment 8 of Bug #1117878) recompiling the local python-dependent package (Mayavi, in my case) with 'PATH="/usr/bin:$PATH"' added into spec in front of 'python setup.py' lines is an effective workaround for the problem (the dependency changes from /bin/python to /usr/bin/python).

Comment 10 errata-xmlrpc 2016-11-04 05:29: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-2397.html