<div class="gmail_quote">On Wed, Aug 10, 2011 at 11:09 AM, Ronald Frazier <span dir="ltr"><<a href="mailto:ron@ronfrazier.net">ron@ronfrazier.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It looks to me like maybe mythbuntu has an updated version of myth in<br>
it's repository. When I created the patch, it looks like the version<br>
was dated 20110416, but in those files I see it dated 20110802. So<br>
what I think happened (and it's just a guess here, as I'm not an<br>
expert at the fine details of package management):<br>
<br>
In my mythbuntu instruction, I mentioned that the build process<br>
created a bunch of packages, and I said you could try installing them<br>
all if you want, but that I only installed 4 and everything seemed to<br>
work. If you only installed those 4, then everything else (the<br>
packages for mythmusic, mythgallery, etc) remained at their default<br>
version. Now that apt sees newer versions of everything, it probably<br>
wants to update all of those other components, but doesn't want to<br>
update the ones that you replaced, probably because it doesn't<br>
recognize those versions, and thus doesn't know how to update them.<br>
<br>
So I'm not sure what the correct course of action here would be. You<br>
could probably run "apt-get -f install" as it suggests, to force the<br>
updates. You might then have mismatched versions of the myth<br>
libraries. I'm betting there's actually a new version of the myth code<br>
available (looks like they switched from 0.24-0 to 0.24-1), and if you<br>
forced those updates and then rebuilt the newer version of myth and<br>
installed the updated packages you'd be back on solid ground. I'm not<br>
absolutely positive though.<br>
<br>
If anyone else here knows a bit more about package management, perhaps<br>
they could chime in.<br>
<br>
Otherwise, if you are shy about experimenting, I could take a look<br>
into it tonight. I've got my mythbuntu test system running in a VM, so<br>
I can take a snapshot, mess with it, and then revert if it doesn't<br>
work right.<br>
<font color="#888888"><br>
--<br>
Ron Frazier<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">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>
</font></blockquote></div><br>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. This is because Mythbuntu 11.04 comes with .24.0 and not .24.1. I added the MythTV and Mythbuntu updates (<a href="http://mythbuntu.org/repos">http://mythbuntu.org/repos</a>) for .24.x. I thought this would bring me to to .24.1+fixes, but I guess it did not. I only got .24.0+fixes. From a MythTV point of view, this is not a problem, but it seems to have confused the package manager.<br>
<br>-Tom<br>