<div class="gmail_quote">On Wed, Aug 11, 2010 at 4:15 PM, Thomas Mashos <span dir="ltr"><<a href="mailto:tgm4883@gmail.com">tgm4883@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><div class="gmail_quote">On Wed, Aug 11, 2010 at 1:43 PM, Nick Rout <span dir="ltr"><<a href="mailto:nick.rout@gmail.com" target="_blank">nick.rout@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, Aug 12, 2010 at 5:20 AM, Thomas Mashos <<a href="mailto:tgm4883@gmail.com" target="_blank">tgm4883@gmail.com</a>> wrote:<br>
><br>
><br>
> On Wed, Aug 11, 2010 at 9:37 AM, Brian J. Murrell <<a href="mailto:brian@interlinx.bc.ca" target="_blank">brian@interlinx.bc.ca</a>><br>
> wrote:<br>
>><br>
>> On Tue, 2010-08-10 at 09:32 -0700, Thomas Mashos wrote:<br>
>> ><br>
>> > There is now a PPA for 0.23.1. The 0.23.0 PPA will not get any more<br>
>> > updates.<br>
>><br>
>> Hrm. I was not operating out of the PPA but from the mythbuntu<br>
>> repository directly at <a href="http://us.autobuilds.mythbuntu.org/mythbuntu/" target="_blank">http://us.autobuilds.mythbuntu.org/mythbuntu/</a><br>
>><br>
>> > <a href="https://edge.launchpad.net/~mythbuntu/+archive/0.23.1" target="_blank">https://edge.launchpad.net/~mythbuntu/+archive/0.23.1</a><br>
>><br>
>> So where is the canonical Mythbuntu repository? Is it a PPA or is it at<br>
>> <a href="http://mythbuntu.org" target="_blank">mythbuntu.org</a>?<br>
>><br>
><br>
> As Mythbuntu is not a canonical project, there is no canonical Mythbuntu<br>
> repository. <a href="http://us.autobuilds.mythbuntu.org" target="_blank">us.autobuilds.mythbuntu.org</a> is mirrored from the PPA, so you<br>
> should be able to manually switch to 0.23.1<br>
><br>
>><br>
>> How were users to find out about this 0.23 -> 0.23.1 changeover if I had<br>
>> not posted here? Shouldn't there be some more automated mechanism to<br>
>> notify and/or upgrade people following a "fixes" stream?<br>
>><br>
><br>
> There isn't an automated way to find out about the change. You may be able<br>
> to subscribe to MythTV.org and see the upgrade there, but you won't<br>
> automatically get upgraded to the next version (ie. 0.23.1 from 0.23.0).<br>
> This is by design and will not change, although I'd be open to input on how<br>
> to notify people of the upgrade.<br>
><br>
>><br>
>> Perhaps the mythbuntu-repos package update that you refer to would have<br>
>> done all of this automatically?<br>
>><br>
><br>
> Nope, you wouldn't have been automatically notified about this.<br>
<br>
There have been two recent updates to mythbuntu-repos on my system. I<br>
have installed them both.<br>
<br>
upon dpkg-reconfoigure mythbuntu-repos I still only have the choice<br>
between 0.23 and 0.24, no 0.23.1<br>
<br>
Surely an update to mythbuntu-repos should offer 0.23.1?<br>
<div><div></div><div>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br></div></div><div>That is how it is supposed to happen, however mythbuntu-repos is built automatically by our build server. It's suppose to only build when there is a new version of Mythtv (ie. 0.23.1), but we have been having issues with the mythtv builds lately. In trying to fix the builds, mythbuntu-repos gets built too. </div>
</blockquote></div><br><div>Sorry for the second reply. This issue was compounded by a few factors. Basically it isn't easy to have -repos go from 0.23 to 0.23.1 (it's setup to easily to go 0.24), and feature freeze is right around the corner giving the project i'm working on higher priority (as it needs to be done by FF). Once I fix mythbuntu-repos so that I can easily go to 0.23.1, this issue shouldn't crop up again.</div>