<div dir="ltr"><div class="gmail_quote">On Thu, Aug 21, 2008 at 1:23 PM, Marc Randolph <span dir="ltr"><<a href="mailto:mrand@pobox.com">mrand@pobox.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">On Thu, Aug 21, 2008 at 10:46 AM, Mike Holden <<a href="mailto:mythtv@mikeholden.org">mythtv@mikeholden.org</a>> wrote:<br>> Allen Edwards wrote:<br>>> That was painless. I updated one of the frontends but it didn't fix<br>
>> my problem with KQED. At least I now know it hasn't been fixed in a<br>>> recent myth update, a very important point.<br>>><br>>> I am going to get to the bottom of this yet.<br>><br>> When you say you upgraded _one of the frontentds_, does that mean that you<br>
> have other frontends and a backend that have _not_ been upgraded? You will<br>> need to do all of them.<br><br></div>I don't believe he was upgrading versions - he was obtaining bug fixes<br>for the branch version he already has. In that case, everything<br>
should be fine (said more technically, any svn version on a particular<br>branch should talk to any other svn version on the same branch). This<br>obviously is not the case for the trunk.</blockquote>
<div> </div>
<div>Never make that assumption. It is entirely possible (but maybe not the case) that database changes are introduced as part of a bug fix. You should *always* run the same branch + revision of Myth on every box.</div>
<div> </div>
<div>Kevin</div></div></div>