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