Bug 226169

Summary: yum doesn't handle bad xml very gracefully
Product: Red Hat Enterprise Linux 5 Reporter: Máirín Duffy <duffy>
Component: yumAssignee: James Antill <james.antill>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: bkearney, jneedle, jturner
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-13 17:51:43 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:
Bug Depends On:    
Bug Blocks: 289601    
Attachments:
Description Flags
traceback from jkt
none
traceback from jneedle none

Description Máirín Duffy 2007-01-31 19:46:19 UTC 
Version-Release number of selected component (if applicable):
yum-3.0.1-5.el5

An excerpt of yum's behavior upon encountering bad xml:

[root@milkbones ~]# yum check-update
Loading "rhnplugin" plugin
[
Loading "installonlyn" plugin
Setting up repositories
rhel-x86_64-server-5      100% |=========================| 1.2 kB    00:00
Reading repository metadata in from local files
primary.xml.gz            100% |=========================| 867 kB    00:01
##################                                 1039/2811

(process:12033): GLib-WARNING **: GError set over the top of a previous GError
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before
it's set.
The overwriting error message was: Parsing primary.xml error: Entity 'gt' not
defined

(process:12033): GLib-WARNING **: GError set over the top of a previous GError
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before
it's set.
The overwriting error message was: Parsing primary.xml error: Entity 'amp' not
defined

(process:12033): GLib-WARNING **: GError set over the top of a previous GError
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before
it's set.
The overwriting error message was: Parsing primary.xml error: Entity 'amp' not
defined
Comment 1 Máirín Duffy 2007-01-31 19:46:19 UTC 
Created attachment 147045 [details]
traceback from jkt
Comment 2 Máirín Duffy 2007-01-31 19:47:42 UTC 
Created attachment 147046 [details]
traceback from jneedle
Comment 3 Jeremy Katz 2007-01-31 20:26:17 UTC 
I vaguely remember fixing this -- can you try a rebuild of yum-metadata-parser
from rawhide and see if it helps?
Comment 4 Seth Vidal 2007-08-03 20:19:35 UTC 
anyone?
Comment 5 Jeremy Katz 2007-09-13 17:51:43 UTC 
This is definitely fixed in current code.  If we want to push an update for
RHEL5, then a new bug should be opened and pushed along through the process