This has been fixed upstream for 2 months, but we don't have the fix in our package. Cardoe, are you planning on putting out a more recent version of the 0.19-fixes branch?
Maybe, Jeremy.... Maybe...
I checked out the mythtv-0.19-fixes (svn co http://svn.mythtv.org/svn/branches/release-0-19-fixes/mythtv). Tarballed it like the mythtv-0.19 tarball (renamed mythtv to mythtv-0.19). Copied to /usr/portage/distfiles. Commented out the rev patch in the ebuild. Emerged it. Working great, sofar. Did a mythfilldatabase and still see the upcoming recordings using MySql 5.1 (always failed with the rev-9163). I, for one, vote for a more recent snapshot of the mythtv-0.19-fixes.
Marvin, is it still working well for you?
(In reply to comment #3) > Marvin, is it still working well for you? > Haven't needed to restart mythbackend since the update. No problems noticed (I just use the TV/PVR portion of mythtv).
What do the devs need for a bump for unstable to a more recent snapshot for 0.19-fixes, for both plugins and core mythtv code? We've got a user reporting long-term testing success, do you need more reports? 10254 is the current revision #, but it would appear that Marvin's revision would have been 9960. sp that might be a safer bet. Thanks.
This was fixed by newer snaps of the 0.19 release... Can they make a release without requiring a ton of bug fixes?