On 4/4/07, Michael <[EMAIL PROTECTED]> wrote:
Ben Lancaster wrote: > Hi all, > > I'm considering the jump to mythtv from bleeding in the hope that it'll > fix some bugs that drive me nuts. Are there any showstoppers or caveats > I should watch out for? > > I have been running trunk for a few months. The only major issue for myself is this one: http://svn.mythtv.org/trac/ticket/3031 If you record a lot of HD then it may be a problem for you. Michael
Just to throw in my two cents. Back in early February I was somewhat forced to upgrade to the SVN branch of Myth to get some fixes for HDHomeRun tuning QAM channels. The fixes eventually made their way into the "fixes" branch thanks to Jarod Wilson, but it was a little too late for me. Anyway, I've been running the 0.21-153 packages from ATRpms bleeding since then, but my attempts to upgrade to both the 0.21-154 and 0.21-155 packages that have since been released into the bleeding repo have failed. With both sets of packages I ran into "undefined symbol" errors when trying to start the mythbackend process. Actually with the 154 packages the process would start but then die almost immediately, and with the 155 packages the back-end process wouldn't even start; two different errors. This is apparently related to some programming changes in Myth described here: http://svn.mythtv.org/trac/ticket/2421. Honestly, I would love to help troubleshoot this problem but I'm not a programmer, don't really have the time, and just want a stable Myth system. If it hadn't been for the issues I was having with the HDHR I would have happily stayed with the stable packages. Having said that though I haven't had any problems to speak of with the 0.21-153 packages.
_______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
