Red Hat Bugzilla – Bug 190961
YumEx 1.0.0 crashed
Last modified: 2014-01-21 17:54:25 EST
Description of problem:
YumEx crashed when processing a RPM file (reported to be missing)
Version-Release number of selected component (if applicable):
Group : Applications/System
Source : yumex-1.0.0-1.0.fc5.src.rpm
Build Time : Wed May 3 13:15:18 2006
Install Time : Sun May 7 02:58:35 2006
License : GPL
Group : System Environment/Base
Source : yum-2.6.1-0.fc5.src.rpm
Build Time : Wed Apr 26 21:29:10 2006
Install Time : Sun May 7 02:32:23 2006
License : GPL
Steps to Reproduce:
error message asked me to provide a bug report - herewith, I do.
see error message file included
Created attachment 128708 [details]
Message from YumEx crash
assiging to yumex
I look like a problem downloading a rpm header, i will take a deeper look.
I dont think you will get this error is you retry, but it should be handled in a
better way by yumex.
This isn't necessarily yumex bug. Yumex received return code 2 from
buildTransaction() which means that everythig went good, but there is a call to
downloadHeader() in resolveDeps (belonging to yum) which throws an exception on
failure without returnig error code. Yum should handle downloadHeader() with
try/except and return relevant error code to calling functions. We could
workaround this in Yumex but I think it would be better to improve error
handling in yum, so we can rely more on error codes in the future.
Dawid, can you point to where in the code you think this should be fixed?
Created attachment 128914 [details]
I have attached patch against depsolve.py in yum 2.6.1 that would pass the
error code up to calling functions. It's a rough patch, not a final solution,
since I didn't test it (I'm at work right now) but it should show what I meant
I have added added a exception handler in the process_one method, so this kind
of errors get catched in the same ways as when doing a normal package processing.
I dont solve the problem but makes yumex behave better when this kind of error