On Mon, Sep 22, 2008 at 9:09 PM, John Summerfield <[EMAIL PROTECTED]> wrote:
> Donald > I don't see what, in the messages you posted, might have lead you quickly to > the solution to the problem. > > Since Greg _was_ able to diagnose the problem, I surmise you're not the > first. I recommend filing a bug report against yum, suggesting improved > error reporting here (and everywhere). Tracebacks are fine for developers, > but users should not be expected to deal with them in the ordinary course of > events. The problem has wasted your time, and the time of everyone who's > seen the thread. I agree that the yum error handling on that was atrocious. Googling for my error for an hour I saw lots of similar tracebacks and reports that yum is broken, always differently. My conclusion is that error handling in yum is basically not present. That is, yum python code is written with assumptions that files exist, are not zero length, will parse without problems, etc. In the wiki it mentions error reporting would be a todo item for post 3.2: http://wiki.linux.duke.edu/YumTodo --Donald _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
