[mythtv-users] MythTV dependencies and Ron's Ceton patch (Tom Bongiorno)
two.bits.11 at gmail.com
Thu Aug 11 03:53:12 UTC 2011
On Wed, Aug 10, 2011 at 9:24 PM, Ken Truesdale <kat at tiac.net> wrote:
> > Date: Wed, 10 Aug 2011 14:21:17 -0400
> > From: Tom Bongiorno <two.bits.11 at gmail.com>
> > Subject: Re: [mythtv-users] MythTV dependencies and Ron's Ceton patch
> > To: Discussion about MythTV <mythtv-users at mythtv.org>
> > Message-ID:
> > <
> CAObkmsV+tXqLz2iw7Y+jDnLTF6eHm0gidf9gHzHKjGkaTjz9JA at mail.gmail.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> > On Wed, Aug 10, 2011 at 2:10 PM, Tom Bongiorno <two.bits.11 at gmail.com
> >> On Wed, Aug 10, 2011 at 2:02 PM, Tom Bongiorno <two.bits.11 at gmail.com
> >>> On Wed, Aug 10, 2011 at 1:26 PM, Ronald Frazier <ron at ronfrazier.net
> >>>> On Wed, Aug 10, 2011 at 11:41 AM, Tom Bongiorno <
> two.bits.11 at gmail.com>
> >>>> wrote:
> >>>>> On Wed, Aug 10, 2011 at 11:09 AM, Ronald Frazier <ron at ronfrazier.net
> >>>> wrote:
> >>>>> Is it the other way around? I think it is trying to install
> >>>> .24.0+fixes
> >>>>> from 2011.04.16 because that is the latest version of the unpatched
> >>>>> libraries that it knows about, but I applied your patch to the
> >>>> .24.1+fixes
> >>>>> source.
> >>>> Oh, well maybe it is the other way around (it wants to downgrade). I'm
> >>>> not 100% sure how to interpret that dependency output. I thought you
> >>>> had just followed my mythbuntu instructions, which downloads the same
> >>>> 0.24-0 source which I'm pretty was used to build mythbuntu's default
> >>>> copy of myth. If you downloaded 0.24-1 fixes straight from git, then
> >>>> I'm not sure how that would have worked.
> >>>> --
> >>>> Ron Frazier
> >>>> _______________________________________________
> >>>> mythtv-users mailing list
> >>>> mythtv-users at mythtv.org
> >>>> http://www.mythtv.org/mailman/listinfo/mythtv-users
> >>> My head is spinning, but I think I got it. I looked back at what I
> >>> actually did. I did exactly as you said in your instructions. The
> >>> is that I updated to .24.1-fixes, and overwrote some of my .24.1-fixes
> >>> binaries with your patch generated .24.0-fixes binaries. Now I have a
> >>> bag of .24.0-fixes and .24.1-fixes binaries. Scary!
> >>> I made a couple mistakes:
> >>> First, I misunderstood your patch. I thought I already had to be at
> >>> .24.x-fixes to apply the patch. Your patch is not a binary patch, but
> >>> rather a source code patch. It was quite obvious. I don't know why I
> >>> missed that.
> >>> Second, I thought adding the updates repos would bring me to
> >>> and not .24.1-fixes. I should have also known this when it asked me if
> >>> was to keep up-to-date with .24.x or .25.
> >>> I am not sure the best course of action at this point.
> >>> -Tom
> >> I could possibly just dpkg -i all the .24.0-fixes debs that were built
> >> your patch. I wonder if that would fix the problem. I turned off
> >> so I that should not get in the way in the future. The Mythbuntu
> >> updates repos may cause a problem at some point though.
> >> -Tom
> > Sorry to barrage everyone with emails.
> > Ron, how well would your patches work against .24.1-fixes source? I am
> > guessing that it may be just fine. .24.1-fixes is the latest stable
> > of MythTV, and many potential users of your patch may already be there.
> > -Tom
> FWIW, I also found that the package manager was confused. It said I had a
> list of broken packages. Not coincidentally, all of the packages it listed
> as broken were all the packages that I did not install. As per Ron's
> instructions, I initially had only installed the 4 packages he listed. But
> after I realized I had this problem, I went back and did the dpkg -i on all
> remaining packages. Here's the full list of installs I did:
> sudo dpkg -i mythtv_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_all.deb
> sudo dpkg -i mythtv-common_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i libmyth-0.24-0_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i mythtv-backend_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i
> sudo dpkg -i mythbrowser_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i mythweather_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i
> sudo dpkg -i mythvideo_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i mythmusic_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i mythnetvision_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i mytharchive_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i mythgame_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i mythnews_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i mythgallery_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_i386.deb
> sudo dpkg -i mythweb_0.24.0+fixes.20110416.9ba3ece-0ubuntu2_all.deb
> I'd feel a lot better about telling you that you should do this, Tom. But
> I have been unable to use the Ceton from inside Myth yet. I got stuck on
> this over the weekend and haven't had time to get back to it this week.
> I've been reading about what other people have found today and it looks
> like I'm alone with my symptoms so I'm just going to go back to basics and
> try again. I also think I should try the network setup that has been
> described in the other thread.
> Until then, all I can say is that package manager is happy after I did the
> above. Although package manager isn't the thing that I care most about!
> mythtv-users mailing list
> mythtv-users at mythtv.org
Did your problems start before or after you ran "dpkg -i" on the remaining
debs. <knocking on wood>So far, my setup is working very well.</knocking on
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users