Bug 671166 - Ran "yum install *d*R*d*r*" to install Adobe Reader, got traceback
Summary: Ran "yum install *d*R*d*r*" to install Adobe Reader, got traceback
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.0
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: BaseOS QE Security Team
URL:
Whiteboard: abrt_hash:fea3ebb1
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-20 16:44 UTC by Red Hat Case Diagnostics
Modified: 2018-11-14 15:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-09 14:54:05 UTC
Target Upstream Version:


Attachments (Terms of Use)
File: backtrace (1.13 KB, text/plain)
2011-01-20 16:45 UTC, Red Hat Case Diagnostics
no flags Details

Description Red Hat Case Diagnostics 2011-01-20 16:44:52 UTC
This description generated by Andreas from an ABRT report
architecture: x86_64
cmdline: /usr/bin/python /usr/bin/yum install AdbeRdr9.4-1_i486linux_enu.rpm AdobeReader
component: yum
executable: /usr/bin/yum
kernel: 2.6.32-71.14.1.el6.x86_64
package: yum-3.2.27-14.el6_0.1
reason: miscutils.py:61:checkSig:OSError: [Errno 2] No such file or directory: 'AdbeRdr9.4-1_i486linux_enu.rpm'
release: Red Hat Enterprise Linux Workstation release 6.0 (Santiago)
reproduce: 1. Ran "yum install *d*R*d*r*" to install Adobe Reader.  Could not find the program in the Add/Remove Software program
2. 
3.

time: 1295537277
uid: 0
backtrace: miscutils.py:61:checkSig:OSError: [Errno 2] No such file or directory: 'AdbeRdr9.4-1_i486linux_enu.rpm'

Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 254, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 192, in main
    return_code = base.doTransaction()
  File "/usr/share/yum-cli/cli.py", line 421, in doTransaction
    if self.gpgsigcheck(downloadpkgs) != 0:
  File "/usr/share/yum-cli/cli.py", line 517, in gpgsigcheck
    result, errmsg = self.sigCheckPkg(po)
  File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 1731, in sigCheckPkg
    sigresult = rpmUtils.miscutils.checkSig(ts, po.localPkg())
  File "/usr/lib/python2.6/site-packages/rpmUtils/miscutils.py", line 61, in checkSig
    fdno = os.open(package, os.O_RDONLY)
OSError: [Errno 2] No such file or directory: 'AdbeRdr9.4-1_i486linux_enu.rpm'

Local variables in innermost frame:
currentflags: 986880
ts: <rpmUtils.transaction.TransactionWrapper instance at 0x2b67170>
value: 0
package: 'AdbeRdr9.4-1_i486linux_enu.rpm'

Comment 1 Red Hat Case Diagnostics 2011-01-20 16:45:03 UTC
Created attachment 474491 [details]
File: backtrace

Comment 4 James Antill 2011-01-20 17:51:36 UTC
Did anything weird happen with the file/directory while yum was running?

Can you try the 6.1 yum (I don't remember anything being completely broken for localinstall, but maybe it was).

Can you give "ls -dl *d*R*d*r*"?

Comment 5 Gavin Romig-Koch 2011-01-25 01:48:12 UTC
restoring the needinfo from comment 4.

Comment 8 James Antill 2011-02-25 21:36:58 UTC
Restoring the needinfo from comment#4

Comment 10 Phil Knirsch 2011-06-09 14:54:05 UTC
This request was evaluated by Red Hat Engineering for inclusion in a Red
Hat Enterprise Linux maintenance release.                               

As this bug has been in NEEDINFO for an extended period of time we are going
to close this bug due to inactivity. If you would like to pursue this
matter feel free to reopen this bug and attach the needed information.

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.

However, Red Hat will further review this request for potential inclusion
in future major releases of Red Hat Enterprise Linux.


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