<br><br><div><span class="gmail_quote">On 4/11/07, <b class="gmail_sendername">Michael T. Dean</b> <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 04/10/2007 10:26 PM, Chris Funk wrote:<br>> I took Steve's advice and upgraded one of my slave backends (actually<br>> made it a master) to SVN. (atrpms bleeding) Had exactly the same<br>> results as with .20.154.
<br><br>If ATrpms bleeding is SVN trunk (as opposed to 0.20-fixes SVN), you do<br>realize that you just upgraded your database to a non-compatible<br>version, right?<br><br>MythTV does /not/ support the use of multiple different versions for
<br>different components in the system. Every frontend/backend/MythWeb must<br>use the exact same version (i.e. same SVN branch and SVN revision).<br><br>So, you can either downgrade the one slave backend and then drop your
<br>database and restore it from the most-current pre-upgrade backup you<br>made, or you need to upgrade /all/ of your components. (Note that the<br>upgrade should be performed even if you used 0.20-fixes SVN.)<br><br>Mike
<br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div><br>Yeah, I took the slave "off" the myth network. Installed the bleeding version fresh as if it was a stand alone backend, local mysql etc. I'll play with it a while longer, then downgrade back to the .20-fixes when I join it back to the existing master.
<br><br>Thanks,<br>Chris<br>