On Tue, 2009-08-04 at 08:37 +0930, Shawn Haggett wrote: > This has been broken for over a week now (normally I just wait, resync > and these things go away if they're an ebuild problem) but I'm > starting to think it's a problem on my end. Anyone have any > suggestions on how to track down where the error is coming from. It > the environment file, but I'm not sure if that's a distributed file, > or generated by portage (I suspect the later). So where does that file > get its contents from?
I ran into this same problem approximately two weeks ago on my amd64 box with the same version. I also needed to rebuild mythtv due to a library upgrade. I originally thought that the problem arose when the ebuild switched from using a SVN checkout to a tarball download. However, the changelog shows that this happened on March 2nd, but I successfully emerged mythtv-0.21_p18314-r1 on April 24th. I upgraded mythtv to 0.21_p20877. It builds correctly on my system and also corrects an issue I was having with the backend process occasionally segfaulting when the frontend exited. Sorry I do not know how to fix this particular issue, but so far 0.21_p20877 has been working great for me on amd64 after a few days of light usage. Regards, Brandon Vargo
