Ah yes forgot to mention I was running LTS 8.04 so upgraded from 8.04 to 10.04<br><br><div class="gmail_quote">On Tue, Mar 27, 2012 at 10:19 AM, Igor Cicimov <span dir="ltr"><<a href="mailto:icicimov@gmail.com">icicimov@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I upgraded to MythTV 0.23 about 2 weeks ago from 0.20 I've been running for years. No problems at all. I also upgraded the ATI proprietary driver to the latest version. The Ubuntu itself had 0.23-fixes in it's repositories and I also added some ppa I found online for higher fixes version. All running good. I decided to stick with the official Mythbuntu releases though so not trying 0.24 or 0.25 since 0.23 does all I need. Except BD playback ...<div class="HOEnZb">
<div class="h5"><br>
<br><div class="gmail_quote">On Tue, Mar 27, 2012 at 7:17 AM, 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">
<div><div>On Tue, Mar 27, 2012 at 6:52 AM, <<a href="mailto:f-myth-users@media.mit.edu" target="_blank">f-myth-users@media.mit.edu</a>> wrote:<br>
> > Date: Mon, 26 Mar 2012 09:09:09 -0500<br>
> > From: Kevin Kuphal <<a href="mailto:kkuphal@gmail.com" target="_blank">kkuphal@gmail.com</a>><br>
><br>
> > On Sun, Mar 25, 2012 at 8:50 PM, <<a href="mailto:f-myth-users@media.mit.edu" target="_blank">f-myth-users@media.mit.edu</a>> wrote:<br>
><br>
> > > I've been pondering this for a couple weeks, ever since I saw Mike's<br>
> > > commit of 2012-03-09T15:20:56-08:00 and his message re "Upgrad failing<br>
> > > from schema 1214 to 1265)" [sic]. This is a new thread 'cause I'm not<br>
> > > sure if very late replies to old threads typically get seen. Sorry if<br>
> > > this is a bit long, but thanks for whatever you can clarify.<br>
> > ><br>
> > > I understand the problem with supporting old Myth versions if their<br>
> > > surroundings also change, but can you be a little clearer on a few<br>
> > > issues here? And I'm hoping to perhaps change your mind, or at least<br>
> > > get workable ways forward---maybe support old versions until 0.25 is<br>
> > > released and -then- drop them, with more warning than the zero that<br>
> > > such users got before your commit?<br>
><br>
> > Cutting the below, can't you just upgrade to 0.23, 0.24, then 0.25 in order<br>
> > using the tarballs? I've seen that before in plenty of commercial products<br>
> > and should work just fine here was well.<br>
><br>
> My impressions of why this wouldn't be easy:<br>
> (a) The tarballs are often not the latest release in any given major<br>
> version. Is it now the case that there are up-to-date tarballs<br>
> for the latest of -fixes in "all" (for some definition of "all")<br>
> Myth versions? If not, what's the right source? git? svn?<br>
> Does it vary based on the age of the release?<br>
> (b) Building requires grabbing a lot of dependencies. That's -way-<br>
> easier if you're starting with a package instead of a tarball,<br>
> so you can do "apt-get build-dep mythtv" or whatever and be sure<br>
> you actually have a consistent and compatible-with-itself set of<br>
> supporting packages.<br>
> (c) Building old versions often winds up in dependency hell, so<br>
> you often need to install an OS of the right vintage as well.<br>
> Remember we're talking Qt versions, MySQL versions, maybe default<br>
> charset issues, I dunno. And that's ignoring capture devices,<br>
> which I'm assuming one would -not- build except to get the backend<br>
> to start, but that then requires a working dummy tuner or something<br>
> else that most users never do, depending on how picky the backend<br>
> is about starting enough to even upgrade itself.<br>
> (d) Many older distros either stop offering -everything-, or stop<br>
> updating packages. This means that someone trying to actually<br>
> go the package route may wind up in trouble as well.<br>
><br>
> I can easily see just one of these causing a lot of hairpulling,<br>
> especially if done long after any given release/package/etc was<br>
> current---in some distros, it might not even be -possible- to go<br>
> back far enough.<br>
><br>
> Are these concerns invalid?<br>
><br>
> Here's another question:<br>
><br>
> Let's just take Ubuntu, since that's what I'm running. For either<br>
> the Canonical-supplied packages or those from Mythbuntu, are those<br>
> routinely rebuilt for (for example, just 'cause it's an LTS) 10.04<br>
> against the -latest- -fixes?<br>
<br>
</div></div>For the canonical packages, they stay at the (ubuntu) release-date<br>
version, as this search shows:<br>
<br>
<a href="http://packages.ubuntu.com/search?keywords=mythtv-frontend&searchon=names&suite=all&section=all" target="_blank">http://packages.ubuntu.com/search?keywords=mythtv-frontend&searchon=names&suite=all&section=all</a><br>
<br>
For the mythbuntu repos you get updates. For example on 10.04, you can<br>
get the latest 0.24-fixes as well as master (which they describe as<br>
0.25, although it is not as 0.25 is not yet released)<br>
<br>
from the repos FAQ:<br>
<br>
How long will you keep doing builds for my version of Ubuntu?<br>
<br>
If your version of Ubuntu is an LTS release, you can expect to<br>
have any MythTV version released up until the next Ubuntu LTS<br>
available to you.<br>
If your version of Ubuntu is a standard release, you will have the<br>
version of MythTV that was available in that release as well as one<br>
more afterward. So if the release launched with 0.23, you will have<br>
0.23 and 0.24 available to you.<br>
<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://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>