[mythtv-users] Just upgraded one front end from .23-fixes to .23.1 now broken

Raymond Wagner raymond at wagnerrp.com
Fri Sep 3 19:24:49 UTC 2010


  On 9/3/2010 15:18, Brent Bolin wrote:
> On Fri, Sep 3, 2010 at 2:00 PM, Raymond Wagner<raymond at wagnerrp.com>  wrote:
>> On 9/3/2010 14:48, Gavin Hurlbut wrote:
>>
>> On Fri, Sep 3, 2010 at 11:43 AM, Thomas Mashos<tgm4883 at gmail.com>  wrote:
>>> On Fri, Sep 3, 2010 at 9:58 AM, Brent Bolin<brent.bolin at gmail.com>  wrote:
>>>> Now it can't connect to back end.  Apparently data base versions have
>>>> changed.  Can't upgrade backend at this time.
>>>>
>>>> Is there any way to back out of this?
>>>>
>>>> Tried changing myth control center back with no success.
>>> Database versions are different? Or Protocol versions are different?
>>> There shouldn't be different database schemas in 0.23.x releases
>> 0.23.1 was only a protocol bump.  There has been no change in the database.
>> That means you can flip back and forth at will.  However you still must
>> retain the same protocol revision on all connected machines.
> Think I can understand schema changes, but what are protocol changes?

The protocol changes refer to the communication protocol used to access 
the backend.  It is used by frontends, mythweb, both the perl and python 
bindings, and a few third party programs.


More information about the mythtv-users mailing list