<div class="gmail_quote">On Sun, Oct 11, 2009 at 5:02 PM, John Hoyt <span dir="ltr"><<a href="mailto:john.hoyt@gmail.com">john.hoyt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div><div></div><div class="h5">On Sun, Oct 11, 2009 at 1:32 PM, Matt Emmott <span dir="ltr"><<a href="mailto:memmott@gmail.com" target="_blank">memmott@gmail.com</a>></span> wrote:<br></div>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">
Mythbuntu 9.04 box, using the testing repos to run 0.22.<br><br>Every weekend I run an upgrade via apt-get on my master BE to keep it up to date. This week, however, I seem to have run into issues. I updated, rebooted and tried a manual mythfilldatabase but received the following:<br>
<br>2009-10-11 13:27:37.091 Using configuration directory = /home/matt/.mythtv<br>2009-10-11 13:27:37.091 Application binary version (0.22.20090928-1) does not match libraries (0.22.20091008-1)<br>2009-10-11 13:27:37.091 This application is not compatible with the installed MythTV libraries. Please recompile after a make distclean<br>
2009-10-11 13:27:37.092 Failed to init MythContext, exiting.<br><br>Upon further review, my backend process was not running and trying to start it manually gave me the same error. I then tried another apt-get update / apt-get upgrade to see if something just didn't update that I overlooked, and received the following:<br>
<br>matt@magicbe:/etc/init.d$ sudo apt-get upgrade<br>Reading package lists... Done<br>Building dependency tree <br>Reading state information... Done<br>The following packages have been kept back:<br> mythtv-backend mythtv-backend-master mythtv-common mythtv-database mythtv-transcode-utils<br>
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.<br><br>I'll be the first to say that I am somewhat terrible with the joys of apt-get, so I was hoping somebody would know why these packages were held back, and what could be done about it.<br>
<br>Here are my mythbuntu repos:<br>:/etc/apt/sources.list.d/mythbuntu-repos.list:<br>deb <a href="http://weeklybuilds.mythbuntu.org/mythbuntu/trunk-0.22/ubuntu" target="_blank">http://weeklybuilds.mythbuntu.org/mythbuntu/trunk-0.22/ubuntu</a> jaunty main<br>
deb <a href="http://ppa.launchpad.net/mythbuntu/testing/ubuntu" target="_blank">http://ppa.launchpad.net/mythbuntu/testing/ubuntu</a> jaunty main<br><br><br>
<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://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
<br></blockquote></div><br>Uninstall all of the myth-themes as they are from an older package, once they are all uninstalled do the upgrade over. The mythbuntu guys stopped packaging the themes independently a week or so ago and caused this issue on my machine as well. Once you get mythtv-common and the other packages updated, your backend "should" work again.<br>
</blockquote></div><br><br>Also, on a side note, make sure to be up to date (i.e. read the mailing list and ALL revisions) with what release of trunk the mythbuntu guys have in the repo. A week ago their automated tools picked a release that had different version of the communication protocol for myth backend, frontend, and plugins and hose my system up for a day.<br>