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

Kelly Reed Schuerman krschuerman at gmail.com
Wed Oct 4 01:31:24 UTC 2006


On 10/3/06, Kelly Reed Schuerman <krschuerman at gmail.com> wrote:
> I started out with myth 4 years ago compiling everything but have
> since moved to binary packages, but this upgrade has brought me back
> to compiling which I haven't done for some time so I have some
> questions.
>
> I am having the protocol version mismatch issue with FC5 atrpms binary
> backend (protocol 31) and Ubuntu Dapper source build frontend
> (protocol 30). I built from source on the frontend in hopes that it
> would use protocol 31.
>
> What is the best solution?
>
> Build the FC5 backend from source to back it off to protocol 30? Will
> there be any database version issues with this method? Is it possible
> to load an older binary build for FC5 to back it off to protocol 30,
> if so how do you specify that build with yum? Also, any database
> issues?

Maybe I should have asked a much simpler question...

If I remove the atrpms binary build from my FC5 master backend and
build from source 0.20 release would I then face database shema
version issues between the source build backend and my current DB
schema which is 1160?

Thanks,
Sherm


More information about the mythtv-users mailing list