<div class="gmail_quote">On Thu, Jan 22, 2009 at 2:22 PM, Gareth Glaccum <span dir="ltr"><<a href="mailto:gareth.glaccum@btopenworld.com">gareth.glaccum@btopenworld.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="word-wrap: break-word;" bgcolor="#ffffff">
<blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div style="background: rgb(228, 228, 228) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
<b>From:</b>
<a title="myth@dermanouelian.com" href="mailto:myth@dermanouelian.com" target="_blank">Brad
DerManouelian</a> </div>
<div>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.</div>
<div><br></div>
<div>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.</div>
<div><br></div>
<div>-Brad</div></blockquote>
<div>
<div><font face="Arial" size="2">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. </font></div>
<div></div></div></div></blockquote><div><br>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. <br>
</div></div>