[mythtv-users] Upgrade and moving of backend

[jarpublic at gmail.com]

On Thu, Jan 22, 2009 at 2:22 PM, Gareth Glaccum <
gareth.glaccum at btopenworld.com> wrote:

>  *From:* Brad DerManouelian <myth at dermanouelian.com>
> It sounds to me like instead of going to trunk you want to check out the
> -fixes branch and build from that so you're still at 0.21 and have a stable
> system. Then when you get that free time, you can easily upgrade to the
> trunk branch.
>
> The bottom line is that you can never mix versions of MythTV. If you want
> to use 0.21-fixes, use it on all machines. If you want to try you hand with
> trunk, it must be on all machines. You should just get a protocol mismatch
> error if you try to run trunk fronend against 0.21-fixes backend. If it's
> actually performing an upgrade then that is wrong behavior.
>
> -Brad
>
>  That sounds perfect! Thanks! I was in fact thinking of using encap for
> 'package management' so being able to move from the -fixes to trunk when the
> time comes and back (if it all goes horrible) would be easy, if I can keep
> the database safe.
>

Others can speak more clearly on the matter, but I don't think you can
downgrade the database once you have upgraded it to .22. I recall seeing on
this list that they are making a few significant changes to the database
structure that would make it incompatable with .21. I am not sure if that is
what you meant by going "back" but I just thought the clarification may
help. Obviously, you could go back to a backed up copy of your .21 database
though.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20090122/a843de06/attachment.htm>