[mythtv-users] protocol version mismatch, what's the best solution?

Nick knowledgejunkie at gmail.com
Fri Oct 6 11:32:04 UTC 2006


On 06/10/06, Osma Ahvenlampi <oa at iki.fi> wrote:
> On ke, 2006-10-04 at 02:01 +0200, Axel Thimm wrote:
> > On Tue, Oct 03, 2006 at 07:43:00PM -0300, Rick wrote:
> > > None of this explains why a yum update and smart update upgrade on the
> > > appropriate machines running the same os, Fedora,  one after the other
> > > gives the protocol mismatch on the backend (for me at least).  Surely
> > > this is the exact way one is to update a system via the packages.
> >
> > Indeed, that's the proper way. Assuming that you don't have any funny
> > options with exclude/include/flagging/pinning/repo weiging or any
> > mechanism that can be summarized as selective/partial then the only
> > thing that you may be missing is a restart of the frontend and/or
> > backend.
>
> I think the problem many users were bitten by was one of "yum update
> myth*", which did not include libmyth. Why would people do this? Because
> many of them would rather avoid updating most parts of their (possibly
> dedicated) HTPC system in search for a more stable base (for example,
> updating the kernel necessitates updating or reinstalling other
> components like NVidia or ATI drivers, lirc, etc).

Why not use "yum update mythtv-suite"? Axel created the meta-package
for a reason.

Nick

MythTV Official wiki:
http://mythtv.org/wiki/
MythTV users list archive:
http://www.gossamer-threads.com/lists/mythtv/users


More information about the mythtv-users mailing list