--=-ixuYHtg86m+BwXmzQ0oy Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2002-09-06 at 14:02, Robert G. Brown wrote: > On 6 Sep 2002, seth vidal wrote: >=20 > > 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=20 > > > need a little pointing in the right direction. > > >=20 > > > The problem is on a 7.3 machine, with rpm 4.0.4, python 1.5.2-38, and= as far=20 > > > as I can tell, pretty much like any other machine. It is a laptop, i= f that=20 > > > has anthing to do with anything. Here is the traceback > > >=20 > >=20 > > You've got a borked header, Like rob said. You should be able to run yu= m > > clean headers and have it remove the headers - yum needs a better > > "header checking" mechanism to determine if a header is fubarred or not= . >=20 > Or at least a better error recovery mechanism, so it fails with some > message like: =20 >=20 > You may have a borked header -- try running "yum clean headers". >=20 > instead of the indecipherable python messages. Does python let you trap > errors and exit with your own messages? >=20 of course it does. exception handling is easy - but you have to grab the exception first - I hadn't encountered it much/at all - I'd still like to more gracefully handle a broken header. -sv --=-ixuYHtg86m+BwXmzQ0oy Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9eO4O1Aj3x2mIbMcRAqs1AJ41Ra6+myKXDP/xJCwvabnN9Jxj3ACfY25U W6Em9G7k/VnzrH43Ce6FPMM= =bDvg -----END PGP SIGNATURE----- --=-ixuYHtg86m+BwXmzQ0oy--
