On Sat, Feb 24, 2007 at 06:20:46PM -0500, John Welch wrote: > OK first, I was able to scroll back in my terminal window to find the error > I was getting on the yum update. It was "Metadata file does not match > checksum" (error 256). Not that I really think that matters at this point.
It does, it means that there is a caching proxy between your system and ATrpms.net. This may give you ancient metadata and explain why yum didn't suggest updates (since it wasn't seeing the new metadata). > I just did the yum update again. It picked up the myth packages and > installed them without any problems. However, I'm still getting the same > back-end error -- "/usr/bin/mythbackend: symbol lookup error: > /usr/bin/mythbackend: undefined symbol: _ZN8EITCache17ClearChannelLocksEv" > > I guess I'll go back to the prior version for now. Should I file a bug > report? No, I'm quite sure you didn't issue a yum update but rather a selective install/update. Do a full yum update (in a dry run if you wish) and see what yum suggests as an update, you'll find you must have been missing libmyth and perhaps more. Currently the only thing in bleeding that yum update would touch is indeed mythtv 0.21, so you can safely do a full yum update. But this is just for the current state of the bleeding repo, not a general recommendation. -- Axel.Thimm at ATrpms.net
pgpKVAVddHtM4.pgp
Description: PGP signature
_______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
