Hi<br><br><div class="gmail_quote">On 16 November 2010 00:40, Greg Oliver <span dir="ltr"><<a href="mailto:oliver.greg@gmail.com">oliver.greg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><br></div>
Like I said, the regular ubuntu mirrors (for non-mythtv stuff) I have<br>
never had issues with (maybe just lucky), but these mythbuntu mirrors<br>
that are included in the .deb package from the mythbuntu website gave<br>
me grief for 2 weeks on some test systems before I finally gave up.<br>
Selecting on mirror would have 0.24 libmyth, but no 0.24 frontend<br>
package, so changing to another would have no 0.24 packages.. It just<br>
got frustrating that partial dependencies are allowed to be<br>
propagated.<br>
<div><div></div><br></div></blockquote><div> </div><div>This can't happen anymore.<br><br>All packages are now built at once. Previously the mythtv packages were built independantly of the mythplugins one etc..<br><br>
It's now one build package building mythtv, the plugins and the themes.<br><br>The only problem I could think of is related to architecture independant packages and you update at a precise moment: but the odds are rather low.<br>
<br>When I was building my own package, the build script were checking on those so it couldn't happen, if mythtv libmyth changed, it would force a rebuild of mythplugins etc..<br><br>I now use <a href="http://fr.autobuilds.mythbuntu.org">fr.autobuilds.mythbuntu.org</a> . This is hosted on my server, same machine running <a href="http://www.avenard.org">www.avenard.org</a> ; it has a gigabit internet connection in a good data centre.<br>
<br>I will continue to make nvidia and mplayer packages. But for mythtv, you are better off using mythbuntu mirrors.<br><br>The mythbuntu decided yesterday to support new mythtv packages on the LTS release until a new LTS version comes + 6 months. This was the key factor making me decide to not bother building my own packages for the time being. I may build some in the "testing" repo in the future if I decide to backport some trunk features in the fixes branch but unofficially.<br>
<br>Jean-Yves<br></div></div>