Bug 430605 - yum traceback after update "out of range integer value"
Summary: yum traceback after update "out of range integer value"
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-28 23:42 UTC by Mike LaPlante
Modified: 2014-01-21 23:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-15 21:24:15 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
pirut traceback (2.88 KB, text/plain)
2008-01-28 23:42 UTC, Mike LaPlante 		no flags Details
Fix yum installonly_limit to use strings and not int's (736 bytes, patch)
2008-01-29 00:08 UTC, James Antill 		no flags Details | Diff
View All

Description Mike LaPlante 2008-01-28 23:42:52 UTC 
Description of problem:
Yum crashes no matter how you run it. "yum clean all" "yum update" "yum -h"

[root@mike ~]# yum -h
Options Error: Error parsing '0': out of range integer value

Version-Release number of selected component (if applicable):yum-3.2.10-3.fc9


How reproducible:
 updated to 3.2.10-3, ran yum.

  
Actual results:
crash!

Expected results: 
update!


Additional info:
Attached traceback output from Pirut
Comment 1 Mike LaPlante 2008-01-28 23:42:52 UTC 
Created attachment 293222 [details]
pirut traceback
Comment 2 James Antill 2008-01-29 00:08:44 UTC 
Created attachment 293224 [details]
Fix yum installonly_limit to use strings and not int's

 You have installonly_limit manually set to 0?
 Can you try applying the following patch to
/usr/lib/python2.5/site-packages/yum

 ...or just change your config to:

installonly_limit=<off>
Comment 3 Mike LaPlante 2008-01-29 13:54:47 UTC 
Setting installonly_limit=<off> fixed it. Thanks!
Comment 4 Andrew Farris 2008-02-15 21:08:46 UTC 
This would be a good thing to have commented in the yum.conf if =0 cannot be used.
Comment 5 James Antill 2008-02-15 21:24:15 UTC 
 This is fixed in 3.2.11
Note You need to log in before you can comment on or make changes to this bug.