<div class="gmail_quote">On Sun, Oct 11, 2009 at 6:10 PM, Jean-Yves Avenard <span dir="ltr"><<a href="mailto:jyavenard@gmail.com">jyavenard@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;">
2009/10/12 John Hoyt <<a href="mailto:john.hoyt@gmail.com">john.hoyt@gmail.com</a>>:<br>
<div class="im"><br>
> Uninstall all of the myth-themes as they are from an older package, once<br>
> they are all uninstalled do the upgrade over. The mythbuntu guys stopped<br>
> packaging the themes independently a week or so ago and caused this issue on<br>
> my machine as well. Once you get mythtv-common and the other packages<br>
> updated, your backend "should" work again.<br>
<br>
</div>bad themes would never cause that error. Neither would mythtv-common.<br>
<br>
That particular error is due when mythplugins wasn't compiled with the<br>
current version of the libraries and the version mismatch<br>
<br>
If using trunk you can't just upgrade the backend and nothing else.<br>
*everything* should be running the same version for both the frontend<br>
and the backend as well as all plugins.<br>
<br>
That updating the themes for you fixed your issue is just a<br>
coincidence as you surely upgraded all other components at the same<br>
time.<br>
<div><div></div><div class="h5">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">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>Yes they would. On MYTHBUNTU (not from source), mythtv-common now installs some themes which were previously separate packages their weekly build ppa. This package and the old themes have file conflicts blocking the install of mythtv-common.<br>