Bug 644304 - package install fails
Summary: package install fails
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-19 11:43 UTC by Roland Frank
Modified: 2014-01-21 06:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-14 19:22:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
urllib2.py:580:proxy_open:TypeError: iterable argument required (2.52 KB, text/plain)
2010-10-19 11:43 UTC, Roland Frank
no flags Details

Description Roland Frank 2010-10-19 11:43:03 UTC
Created attachment 454330 [details]
urllib2.py:580:proxy_open:TypeError: iterable argument required

Description of problem:
yum search (e.g.) filelight

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


How reproducible:


Steps to Reproduce:
1. yum search package-name
2. alternative pirut - search - apply
3.
  
Actual results: 
TypeError: 'iterable argument required'
  if  '@' in host

Expected results:


Additional info:

see attachment for python error trace

Comment 1 James Antill 2013-03-14 19:22:19 UTC
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.


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