Bug 507878

Summary: yum.Errors.MiscError: Could not open local rpm file: gcc-4.1.2-44.el5.src.rpm
Product: Red Hat Enterprise Linux 5 Reporter: Michal Nowak <mnowak>
Component: yum-utilsAssignee: James Antill <james.antill>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: ohudlick
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-12 20:54:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Nowak 2009-06-24 15:49:02 UTC
Description of problem:
.qa.[root@ia64-5s-m2 ~]# yum clean all
Loaded plugins: aliases, changelog, downloadonly, fastestmirror, filter-data,
              : keys, kmod, list-data, protect-packages, protectbase, rhnplugin,
              : security, tmprepo, verify, versionlock
Cleaning up Everything
Cleaning up list of fastest mirrors

.qa.[root@ia64-5s-m2 ~]# yum-builddep gcc-4.1.2-44.el5.src.rpm 
Loaded plugins: fastestmirror, kmod, protectbase, rhnplugin, versionlock
Determining fastest mirrors
[...]
Reading version lock configuration
0 packages excluded due to repository protections
Traceback (most recent call last):
  File "/usr/bin/yum-builddep", line 142, in ?
    util = YumBuildDep()
  File "/usr/bin/yum-builddep", line 41, in __init__
    self.main()
  File "/usr/bin/yum-builddep", line 66, in main
    self.get_build_deps()
  File "/usr/bin/yum-builddep", line 109, in get_build_deps
    srpms.append(yum.packages.YumLocalPackage(self.ts, arg))
  File "/usr/lib/python2.4/site-packages/yum/packages.py", line 1460, in __init__
    raise Errors.MiscError, \
yum.Errors.MiscError: Could not open local rpm file: gcc-4.1.2-44.el5.src.rpm


The file gcc-4.1.2-44.el5.src.rpm is not existing in $(PWD), but issuing another random "filename" works as expected:

.qa.[root@ia64-5s-m2 ~]# yum-builddep dfkdfkjfd.rpm
Loaded plugins: fastestmirror, kmod, protectbase, rhnplugin, versionlock
Loading mirror speeds from cached hostfile
Reading version lock configuration
0 packages excluded due to repository protections
No such package(s): dfkdfkjfd.rpm.src


(Well, not exactly as expected: "dfkdfkjfd.rpm.src" v. "dfkdfkjfd.rpm")

Version-Release number of selected component (if applicable):

yum-utils-1.1.16-13.el5.noarch
yum-3.2.19-18.el5.noarch

How reproducible:

always.redhat.com

Expected results:

No bt + sane filename in "No such package(s):" field.

Comment 1 Michal Nowak 2011-05-13 08:58:21 UTC
(i386)

I still can see it:

# yum-builddep --nogpg bridge-utils-1.1-2.src.rpm 
Loaded plugins: product-id
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 897da07a
Traceback (most recent call last):
  File "/usr/bin/yum-builddep", line 142, in ?
    util = YumBuildDep()
  File "/usr/bin/yum-builddep", line 41, in __init__
    self.main()
  File "/usr/bin/yum-builddep", line 66, in main
    self.get_build_deps()
  File "/usr/bin/yum-builddep", line 109, in get_build_deps
    srpms.append(yum.packages.YumLocalPackage(self.ts, arg))
  File "/usr/lib/python2.4/site-packages/yum/packages.py", line 1570, in __init__
    raise Errors.MiscError, \
yum.Errors.MiscError: Could not open local rpm file: bridge-utils-1.1-2.src.rpm

However, cpufreq-utils-005-3.el5.src.rpm is fine.

Can't use `yum-builddep bridge-utils' alone since I don't have SRPM repos here.

Comment 3 James Antill 2013-03-12 20:54:12 UTC
I believe this is fixed in RHEL-6.


This request was evaluated by Red Hat Engineering for inclusion in a Red 
Hat Enterprise Linux maintenance release.

Red Hat does not currently plan to provide this change in a Red Hat 
Enterprise Linux update release for currently deployed products.

With the goal of minimizing risk of change for deployed systems, and in 
response to customer and partner requirements, Red Hat takes a 
conservative approach when evaluating enhancements for inclusion in 
maintenance updates for currently deployed products. The primary 
objectives of update releases are to enable new hardware platform 
support and to resolve critical defects.