<br><br><div class="gmail_quote">On Fri, Oct 8, 2010 at 10:44 PM, Robert McNamara <span dir="ltr"><<a href="mailto:robert.mcnamara@gmail.com">robert.mcnamara@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Fri, Oct 8, 2010 at 7:35 PM, Matt Emmott <<a href="mailto:memmott@gmail.com">memmott@gmail.com</a>> wrote:<br>
<br>
> Ok, I'm thoroughly confused.I suppose I could be ok that it's running older<br>
> libraries or something since, as you said, 10.04 was out before 0.23, but<br>
> why the heck would the version show up as 0.23 if it's not a true 0.23? To<br>
> take this a step further, are you saying that when I upgrade my systems to<br>
> 10.10, it will bring Myth to 0.23.1, but when 0.24 comes out I'll remain at<br>
> 0.23.1 but the version number listed in my logs will change to 0.24?<br>
><br>
> I think my brain just exploded.<br>
<br>
</div>It's not as complicated as all of that. For better or for worse, as<br>
soon as Ubuntu starts tracking trunk after a release, they bump their<br>
package version number to what the next version will be-- so trunk<br>
packages on Ubuntu right now are called ".24" even though no such<br>
thing exists yet. The packages that 10.04 went out with were titled<br>
".23" but were basically trunk packages from a ways before .23<br>
actually existed. Unfortunately this means that a) All the bugs that<br>
got fixed after that, and there were many, were blamed on MythTV (even<br>
though we would never have released with those issues) and b) everyone<br>
running Ubuntu/Mythbuntu has to go through a special, somewhat<br>
unintuitive step of finding, downloading, and installing a particular<br>
repository package to get to what is *actually* .23, rather than it<br>
being pushed to htem as an update automatically. It's something to do<br>
with Ubuntu package update policies and something some of us are not<br>
very happy about. As a result, we've talked to the Mythbuntu guys and<br>
asked that this kind of thing not happen again (as it did for both .22<br>
and .23) and instead that they go with .23.1 for their next release as<br>
.24 will still be either pre-release or just-released, and neither<br>
team wants the blame or confusion of having delivered development code<br>
presented as release code.<br>
<font color="#888888"><br>
Robert<br>
</font><div><div></div><div class="h5">_______________________________________________<br></div></div></blockquote><div><br>Wow. I feel like it's the end of Fight Club and everything I thought I knew is wrong. Ok, maybe I'm being melodramatic, but it sounded good.<br>
<br>I tend to run two versions of myth - Prod, which is what my primary backends and frontends all use for day to day recording. Then there's Dev, which I'll have a box or two at home and one or two at work. The dev ones don't last too long, they're generally for testing random stuff I think of at 3 in the morning and since I'm a terrible Linux admin, they never seem to work out.<br>
<br>That being said, all my prod has always been straight downloads via Ubuntu's repos, while dev usually comes from the Auto Builds at <a href="http://www.mythbuntu.org/download-type">http://www.mythbuntu.org/download-type</a> . I always just assumed that Ubuntu (via mythbuntu-control-centre, see my earlier posts) had the latest stable channels and the auto-builds were more bleeding edge. I know that when you set up the auto-build repos it lets you choose from -fixes or -trunk but I still just assumed that these were both less stable, less tested versions of Myth. What you've said totally makes sense but it really threw me for a loop because it changes my whole perspective on how I should be building and deploying my systems.<br>
</div></div>