Version 0.15 of MythTV was released today. A version bump on the ebuild is needed. Also what is holding the 0.14 ebuilds from moving from ~x86 to stable? Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge -p mythtv 3. view results that don't include 0.15 Actual Results: Results did not contain version 0.15 Expected Results: Seeing version 0.15
0.15 is very important for North American users as it supports the new DataDirect service from zap2it labs since they disable XMLTV support and everyone's guide data runs out by Friday (I'm writing this Thursday). So basically 0.15 needs to even go straight to stable since no user setting up 0.14 and earlier will be able to get it to function if their in North America.
On a lark, I decided to try copying the mythtv 0.14 ebuild into the appropriate location under /usr/local/portage and rename it mythtv-0.15.ebuild. The build process starts, but it eventually chokes on libs/libmythtv/videoout_directfb.cpp: videoout_directfb.cpp: In member function `virtual bool VideoOutputDirectfb::Init(int, int, float, long unsigned int, int, int, int, int, long unsigned int)': videoout_directfb.cpp:340: error: `DSCAPS_DOUBLE' undeclared (first use this function) I have DirectFB 0.9.20 installed, which is the latest available. The error occurs in VideoOutputDirectfb::Init, which appears to have changed substantially from v0.14. I'm thinking that changing DSCAPS_DOUBLE to DSCAPS_FLIPPING might do the trick...it's building now. I should know in a few minutes.
Re: Comment #1 (DataDirect and .14) .15 isn't exactly essential. Users can continue running .14 (or earlier, I suppose) since XMLTV has support for DataDirect with the new grabber (tv_grab_na_dd). Install the latest version of XMLTV if you want to use it. Then see http://www.gossamer-threads.com/lists/mythtv/users/67721?#67721 for instructions on changing a few things and then there is a new Cron script located later on in that thread.
In a followup to my previous comment, changing DSCAPS_DOUBLE to DSCAPS_FLIPPING enables the compile to complete. I've made a patch available at http://alfter.us/files/mythtv-0.15-directfb.patch and integrated that into the ebuild. I've successfully emerged MythTV 0.15 (and MythWeb 0.15, again using a private ebuild), but I'll need to wait until this evening to see if it'll actually work as it should. (I'm at work right now and can't properly test it out.) For that reason (and also because I haven't vetted the dependencies to make sure the minimum versions are correct for MythTV 0.15), I'm reluctant to post my ebuilds at this time.
Created attachment 32185 [details] updated ebuild for MythTV 0.15 I have tested this ebuild on my MythTV system (using the PVR350 framebuffer for the X11 display). The referenced patch is needed for DirectFB support (which the PVR350 uses), and a wget dependency is added.
I don't have a PVR-350 so I don't need the directfb patch, but I noticed this when building it: >>> emerge (1 of 1) media-tv/mythtv-0.15 to / >>> md5 src_uri ;-) mythtv-0.15.tar.bz2 >>> md5 src_uri ;-) mythtv-0.15-directfb.patch >>> Unpacking source... >>> Unpacking mythtv-0.15.tar.bz2 to /var/tmp/portage/mythtv-0.15/work >>> Unpacking mythtv-0.15-directfb.patch to /var/tmp/portage/mythtv-0.15/work unpack mythtv-0.15-directfb.patch: file format not recognized. Ignoring. RUNNING FROM extra_functions.sh * Applying mythtv-0.15-directfb.patch... [ ok ] >>> Source unpacked. .... Is that "file format not recognized" error expected?
In your ebuild (most recent comment with ebuild above), is >=net-misc/wget-1.9.1 necessary? etcat -v wget shows: $ etcat -v wget [ Results for search key : wget ] [ Candidate applications found : 3 ] Only printing found installed programs. * net-misc/wget : [ ] 1.8.2-r3 (0) [ I] 1.9-r2 (0) [M~ ] 1.9.1-r2 (0) $ I'm going to try with 1.9-r2. It seems to work. Second problem with your ebuild is that that directfb patch seems to already be applied; this could just be Isaac's very faulty managing style (e.g., perhaps he changed the release without making a new version #), or somehow you did the patch wrong (it wasn't necessary, or you did it backwards). Also, next time you create a patch file, use diff -up (if doing trees, do diff -Nrup); that makes it unified, and includes the function names the patches are about so it's a more informative and redundant patch (redundancy is good in patches). WRT XMLTV: I confirm that hacking XMLTV interactions with MythTV 0.14 works WRT its database, but I only use its database with local scripts (not with any Myth stuff). They said MythTV preserves more data using its native Zap2It grabber than via XMLTV->mythfilldatabase. However, finding and implementing the correct hacks was, while not very hard, quite annoying, and now that there is a release of MythTV that simply supports the correct method to retrieve Zap2It data, a lot of people who are MythTV users will prefer to upgrade to 0.15, depending on other things (its stability, bugs, features, etc.). Also, XMLTV's new Zap2It grabber has the same problems of needing to create a survey login that you're claiming MythTV now has, and Zap2It has been getting mad about users still using the old XMLTV method (someone said it's going to stop working soon; I was forced to deal with it since all my distributions dropped XMLTV's support for the old system by default more than a few weeks ago, and I didn't have any data left!). I'm not sure why XMLTV people haven't tried TitanTV interfacing yet, and implementation of using broadcast schedule data has been too slow AFAIK (some people have done a little work with it so far; is it working in Myth yet?). The ebuild now completed. Running mythsetup now. It updated schemes from 1027 to 1044. Converted XMLTV to Direct; it seems to work now. Mythbackend is running now. I'm not sure if it will work, but at least it made a schedule and is sitting there. So, the ebuild is close to right.
>unpack mythtv-0.15-directfb.patch: file format not recognized. Ignoring. >... >>>> Source unpacked. >... > >Is that "file format not recognized" error expected? I think emerge is trying to uncompress a patch that's already uncompressed. It's harmless. >In your ebuild (most recent comment with ebuild above), is >>=net-misc/wget-1.9.1 necessary? From http://www.mythtv.org/docs/mythtv-HOWTO-5.html: "If you are in North America you will use the DataDirect grabber which is built-in to MythTV. You do not need to install XMLTV, but you need wget version 1.9.1 or higher." >Second problem with your ebuild is that that directfb patch >seems to already be applied; this could just be Isaac's very >faulty managing style (e.g., perhaps he changed the release >without making a new version #), or somehow you did the >patch wrong (it wasn't necessary, or you did it backwards). The patch is correct. I checked the MD5 sums between the MythTV 0.15 tarball I downloaded Thursday evening and the tarball I downloaded a few minutes ago; it hasn't changed. If you attempt to compile MythTV 0.15 with DirectFB support ("directfb" is among your USE flags) without the patch, the compile will fail because DSCAPS_DOUBLE is undefined in the DirectFB header files. It needs to be changed to DSCAPS_FLIPPING; the patch does that. (I read on the MythTV list that DSCAPS_DOUBLE is defined in DirectFB CVS, but most people won't be running that version.)
Simple fix to the error with the patch... Just change these lines... src_unpack() { unpack ${A} && cd ${S} epatch ${DISTDIR}/${P}-directfb.patch to src_unpack() { unpack ${P}.tar.bz2 cd ${S} epatch ${DISTDIR}/${P}-directfb.patch
As just realized my database ran out. I upgraded to 0.15.1 by hand, I worry about it later. I would recommend that it go to stable soon as I am sure many users are confused or issue a .14 upgrade with the tv_grab_na_dd updates and whatever else. Also the wget-1.9.1-r2 in portage now did not work for me with the DataDirect upgrade. I needed to install from the tarball to get it to work, but it all works now. The ebuild should also mention the DataDirect changes with a link to http://www.mythtv.org/docs/mythtv-HOWTO-21.html#ss21.19
In CVS, thanks!
I was a bit to quick to close this bug. The directfb patch and wget dependency has been added. Thanks!