[Yum] traceback encountered
Robert G. Brown
rgb at phy.duke.edu
Fri Sep 6 18:02:20 UTC 2002
On 6 Sep 2002, seth vidal wrote:
> On Fri, 2002-09-06 at 11:28, Troy Dawson wrote:
> > Howdy,
> > This traceback might be a problem on the machine's end, and not yum. I just
> > need a little pointing in the right direction.
> >
> > The problem is on a 7.3 machine, with rpm 4.0.4, python 1.5.2-38, and as far
> > as I can tell, pretty much like any other machine. It is a laptop, if that
> > has anthing to do with anything. Here is the traceback
> >
>
> You've got a borked header, Like rob said. You should be able to run yum
> clean headers and have it remove the headers - yum needs a better
> "header checking" mechanism to determine if a header is fubarred or not.
Or at least a better error recovery mechanism, so it fails with some
message like:
You may have a borked header -- try running "yum clean headers".
instead of the indecipherable python messages. Does python let you trap
errors and exit with your own messages?
rgb
>
> -sv
>
>
Robert G. Brown http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb at phy.duke.edu
More information about the Yum
mailing list