[ATrpms-users] Mythweb protocol mismatch after yum update

[Graeme Hilton]

Rick wrote:
> Graeme Hilton wrote:
>> Phill Edwards wrote:
>>> Axel Thimm wrote:
>>>> No, you are using partial/selective enablement of ATrpms. Don't.
>>>>       
>>> How am I doing that - I don't really understand what that means? Is it
>>> something in my .repo files or something? All my previous updates have
>>> worked just fine.
>>>     
>>
>> Simply put, you are using yum in a way that it is restricted as to what
>> packages it may or may not update.
>>
>> you should do the following at the command line:
>> yum update
>> (as root, or use sudo)
>>
>> Don't specify a package, or a expression after the update, i.e. don't
>> yum update mythtv-suite or yum update myth* as that it selective
>> updating/partial enablement.
>>
>>   
> That is exactly the way I've been doing it for years.  I still got the
> protocol mismatch on my backend.  I got it on one of my frontend as well
> using smart but that was cured by a removal and reinstall.  That didn't
> work on the backend.  Somewhere, somehow something must have happened to
> a lot of peoples .repo files but mine look fine.  I can't figure it
> out.  Why doesn't someone who successfully updated post their repo files
> so we can do a line by line comparison.

Phill emailed me and let me know that a restart of mythbackend solved
his problems.  Probably the update script doesn't restart the backend.
It might be a useful addition to the script, but if the backend is
mid-recording you won't be winning many friends.


-- 
Graeme Hilton