Bug 190961

Summary: YumEx 1.0.0 crashed
Product: [Fedora] Fedora Reporter: Georg F. Bolz <linux>
Component: yumexAssignee: Tim Lauridsen <tim.lauridsen>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: dzrudy, katzj
Target Milestone: ---   
Target Release: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-10 08:08:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Message from YumEx crash
none
depsolve patch none

Description Georg F. Bolz 2006-05-07 13:35:25 UTC 
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

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
error message asked me to provide a bug report - herewith, I do. 

Expected results:


Additional info: 
see error message file included
Comment 1 Georg F. Bolz 2006-05-07 13:35:26 UTC 
Created attachment 128708 [details]
Message from YumEx crash
Comment 2 Seth Vidal 2006-05-07 13:57:08 UTC 
assiging to yumex
Comment 3 Tim Lauridsen 2006-05-08 06:52:59 UTC 
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.
Comment 4 Dawid Zamirski 2006-05-09 17:39:53 UTC 
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.
Comment 5 Seth Vidal 2006-05-11 18:39:45 UTC 
Dawid, can you point to where in the code you think this should be fixed?
Comment 6 Dawid Zamirski 2006-05-11 20:27:37 UTC 
Created attachment 128914 [details]
depsolve patch

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
:-)
Comment 7 Tim Lauridsen 2006-08-10 08:08:15 UTC 
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
occours.