Bug 456898 - Package Updater never completes the resolution of dependencies.
Package Updater never completes the resolution of dependencies.
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
8
i386 Linux
low Severity high
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-28 10:48 EDT by Greg Denson
Modified: 2014-01-21 18:06 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-09-03 09:54:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Crash Dump file from Package Updater (1.85 KB, text/plain)
2008-07-28 10:48 EDT, Greg Denson
no flags Details

  None (edit)
Description Greg Denson 2008-07-28 10:48:49 EDT
Description of problem:


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


How reproducible:  Package Updater runs automatically to download updates.  Then
click on Apply Updates.  The Updater then starts to work on resolving
dependencies.  It never completes the process.  The status bar moves all the way
to the right, but the window never closes. 


Steps to Reproduce:
1.
2.
3.
  
Actual results:••••••••••The process never completes.  This morning, the system
reported that Package Updater was not responding, and that this was likely a bug
that needed to be reported.  A Crash Dump file is attached.


Expected results:


Additional info:
Comment 1 Greg Denson 2008-07-28 10:48:49 EDT
Created attachment 312780 [details]
Crash Dump file from Package Updater
Comment 2 James Antill 2008-08-18 15:40:12 EDT
  File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 501, in _requiringFromTransaction
    reqpkg = self.rpmdb.searchNevra(name=name, ver=version, rel=release)[0]
IndexError: list index out of range

...that looks somewhat familiar, so it's probably fixed post 3.2.8 (3.2.19 should be in updates-testing for Fedora 8 soon, I think). So that should solve your problem.
Comment 3 seth vidal 2008-09-03 09:54:56 EDT
3.2.19 is in updates-testing. Please reopen if this is not solved.

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