Description of problem:
While connected via ssh -Y to remote server I got attached backtrace. The
problem is not happening anymore, I guess RHN was the problem but I guess pup
should not crash when got improper data. More details might be seen in attached
log -- if there's nothing just close...
(Just my assumption.)
Version-Release number of selected component (if applicable):
always (that time)
Steps to Reproduce:
do not crash when received wrong data
Created attachment 301615 [details]
backtrace from crashed pup
Created attachment 302578 [details]
And now, after some time, again
Ok, yeh ... all the XML processing in yum and related tools is strict and
always has been, you need to fix whatever is generating this (I assume RHN?) ...
we really need xmllint to be run on the output before it goes live.
I'd expect pup not to completely blow up with bt but issue error msg "Hey, the
the data I'm receiving from satellite/hosted are messed up. Bug your admin."
Yum did not asplode in this situation.
yum doesn't blow up because it doesn't load the updateinfo.xml file by default,
if you use the --security it will blow up in the same way.
Yes, in theory, we could catch all the exceptions that libxml raises and print
a message like "your FOO xml file is broken", but we don't ... and it's not
supposed to be a "common" error.
Feel free to open an RFE against yum Fedora and we'll look at it.