On Thu, Oct 4, 2012 at 2:10 PM, Thomas Mashos <span dir="ltr"><<a href="mailto:thomas@mashos.com" target="_blank">thomas@mashos.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Thu, Oct 4, 2012 at 11:58 AM, Jim Oltman <<a href="mailto:jim.oltman@gmail.com">jim.oltman@gmail.com</a>> wrote:<br>
> On Thu, Oct 4, 2012 at 1:43 PM, Mario Limonciello <<a href="mailto:mario.mailing@gmail.com">mario.mailing@gmail.com</a>><br>
> wrote:<br>
>><br>
>> This should be fixed with the 10/4 builds.<br>
>><br>
>> There was two snafu's here:<br>
>><br>
>> 1) The packaging branch didn't have fixes/0.26 branched when everything<br>
>> else was branched for release.<br>
>> 2) The Ubuntu packaging scripts were checking for the latest fixes version<br>
>> and had a fallback to master when that didn't exist.<br>
>><br>
>> I've added some commits around the autobuilder to query directly for the<br>
>> current fixes version (from github) to make sure that this can't happen in<br>
>> the future (when 0.27 gets released or so). Fortunately there weren't any<br>
>> database changes yet in 0.27, so moving from the 10/3 "0.27pre" builds to<br>
>> 10/4 builds shouldn't be any trouble.<br>
><br>
><br>
> Should there be an announcement on the MythBuntu.org site AND here on the<br>
> list stating that MythBuntu Control Center has been tested to work with the<br>
> new version and that upgrading should work correctly? For every new major<br>
> Myth release?<br>
><br>
</div></div><div class="im">> _______________________________________________<br>
> mythtv-users mailing list<br>
> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
> <a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
><br>
<br>
</div>I'm not sure I understand why you think that the Mythbuntu control<br>
centre wouldn't work.<br>
<br>
Thanks,<br>
<br>
Thomas Mashos</blockquote><div><br></div><div>it didn't work for the guy above. His system got upgraded to 0.27. Granted he can fall back to 0.26 without any DB issues. However, if there is an eventual change to 0.27's DB or 0.28 and this happens again, it could be a bad time recovering data. It was just a thought to have a nice public announcement.</div>
</div>