Re: [gentoo-user] emerge mythtv fails... again

2009-08-19 Thread Gregory Shearman
In linux.gentoo.user, you wrote:
 I wrote:

 Shawn Haggett writes:
  Some recent updates have broken my mythtv (missing libraries) so I'm of
  course trying to recompile it. Whenever I try however, the following
  happens:
 
  sgc ~ # emerge -va mythtv

 [...]

  /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/temp/environment: line
  3924: cd:
  /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0
 -2 1-fixes/mythtv: No such file or directory
  sed: can't read
  /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0
 -2 1-fixes/mythtv/version.pro: No such file or directory

 [...]
 I just had the same problem with a fresh install of mythtv. I tried other
 versions, 0.21_p19961-r2 showed the same problem, but 0.21_p20877 did
 compile. So give that one a try.

 Now python-updater wants to rebuild mythtv, and fails to do so because of 
 the missing version.pro. Same version which built before. The ebuild's date 
 is from july 20th, some days before I emerged it, so there was no silent 
 change.

 Strange. But for the moment I don't care, no time yet to play with mythtv.

 BTW, the expected .../work/mythtv-0.21_p20877/version.pro can be found in 
 .../work/branches/release-0-21-fixes/mythtv/version.pro.

I had the same problem. What I've done is to remove ~x86 from mythtv in
/etc/portage/package.keywords and then rerun the python updater on the
older stable mythtv version (0.21_p18314-r1). The compile completed
successfully.

-- 
Regards,

Gregory.
Gentoo Linux - Penguin Power

-- 
Regards,

Gregory.
Gentoo Linux - Penguin Power



Re: [gentoo-user] emerge mythtv fails... again

2009-08-18 Thread Alex Schuster
I wrote:

 Shawn Haggett writes:
  Some recent updates have broken my mythtv (missing libraries) so I'm of
  course trying to recompile it. Whenever I try however, the following
  happens:
 
  sgc ~ # emerge -va mythtv

 [...]

  /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/temp/environment: line
  3924: cd:
  /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0
 -2 1-fixes/mythtv: No such file or directory
  sed: can't read
  /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0
 -2 1-fixes/mythtv/version.pro: No such file or directory

[...]
 I just had the same problem with a fresh install of mythtv. I tried other
 versions, 0.21_p19961-r2 showed the same problem, but 0.21_p20877 did
 compile. So give that one a try.

Now python-updater wants to rebuild mythtv, and fails to do so because of 
the missing version.pro. Same version which built before. The ebuild's date 
is from july 20th, some days before I emerged it, so there was no silent 
change.

Strange. But for the moment I don't care, no time yet to play with mythtv.

BTW, the expected .../work/mythtv-0.21_p20877/version.pro can be found in 
.../work/branches/release-0-21-fixes/mythtv/version.pro.

Wonko



Re: [gentoo-user] emerge mythtv fails... again

2009-08-18 Thread Mark Knecht
On Tue, Aug 18, 2009 at 12:55 PM, Alex Schusterwo...@wonkology.org wrote:
 I wrote:

 Shawn Haggett writes:
  Some recent updates have broken my mythtv (missing libraries) so I'm of
  course trying to recompile it. Whenever I try however, the following
  happens:
 
  sgc ~ # emerge -va mythtv

 [...]

  /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/temp/environment: line
  3924: cd:
  /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0
 -2 1-fixes/mythtv: No such file or directory
  sed: can't read
  /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0
 -2 1-fixes/mythtv/version.pro: No such file or directory

 [...]
 I just had the same problem with a fresh install of mythtv. I tried other
 versions, 0.21_p19961-r2 showed the same problem, but 0.21_p20877 did
 compile. So give that one a try.

 Now python-updater wants to rebuild mythtv, and fails to do so because of
 the missing version.pro. Same version which built before. The ebuild's date
 is from july 20th, some days before I emerged it, so there was no silent
 change.

 Strange. But for the moment I don't care, no time yet to play with mythtv.

 BTW, the expected .../work/mythtv-0.21_p20877/version.pro can be found in
 .../work/branches/release-0-21-fixes/mythtv/version.pro.

        Wonko



I've been dealing with this failure for a couple of weeks now. Nothing
new released to address it yet even though it seems there might be
some sort of a fix pending, or even possibly released (as per the last
couple of entries) but for me p20877 still doesn't build:

http://bugs.gentoo.org/show_bug.cgi?id=280516

- Mark



Re: [gentoo-user] emerge mythtv fails

2009-08-07 Thread Shawn Haggett
On Tuesday 04 August 2009 09:41:58 Stroller wrote:
 On 4 Aug 2009, at 00:07, 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.

 I don't yet use MythTV myself, but had reason to investigate it again
 this week.

 I saw this mentioned on the MythTV-users list (probably a more useful
 resource for you than this list, TBH). Perhaps you may find it useful:

 http://wiki.github.com/MarcT/mt-mythtv

 Stroller.

Thanks, although I'm already on that list too. I haven't seen this problem 
mentioned on the mythtv-users list (and a quick search doesn't turn anything 
up).

I chose this list to post to, since the problem appears to be a Gentoo/portage 
issue, rather then a mythtv issue. I suspect a bug needs to be filled for 
Gentoo, although I didn't want to needlessly file bugs and annoy the hard 
working bug wrangles/devs.

Shawn



[gentoo-user] emerge mythtv fails

2009-08-03 Thread Shawn Haggett
Some recent updates have broken my mythtv (missing libraries) so I'm of course 
trying to recompile it. Whenever I try however, the following happens:

sgc ~ # emerge -va mythtv

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N] media-tv/mythtv-0.21_p18314-r1  USE=aac alsa dvd ieee1394 mmx 
opengl perl python xvmc 
(-altivec) -autostart -debug -directv -dvb -fftw -jack -lcd -lirc 
VIDEO_CARDS=nvidia 0 kB

Total: 1 package (1 new), Size of downloads: 0 kB

Would you like to merge these packages? [Yes/No] y

 Verifying ebuild manifests

 Emerging (1 of 1) media-tv/mythtv-0.21_p18314-r1
 * mythtv-0.21_p18314.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...[ 
ok ]
 * checking ebuild checksums ;-) ... [ 
ok ]
 * checking auxfile checksums ;-) ...[ 
ok ]
 * checking miscfile checksums ;-) ...   [ 
ok ]
 * This ebuild now uses a heavily stripped down version of your CFLAGS
 *
 * For NVIDIA based cards, the XvMC renderer only works on
 * the NVIDIA 4, 5, 6  7 series cards.
 Unpacking source...
 Unpacking mythtv-0.21_p18314.tar.bz2 
to /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work
/var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/temp/environment: line 3924: 
cd: 
/var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0-21-fixes/mythtv:
 
No such file or directory
sed: can't 
read 
/var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0-21-fixes/mythtv/version.pro:
 
No such file or directory
 *
 * ERROR: media-tv/mythtv-0.21_p18314-r1 failed.
 * Call stack:
 *   ebuild.sh, line   49:  Called src_unpack
 * environment, line 3925:  Called die
 * The specific snippet of code:
 *   sed -e s:\`(svnversion \$\${SVNTREEDIR} 2\/dev\/null) || echo 
Unknown\`:${MYTHTV_REV}: -i ${S}/version.pro || die svnversion sed 
failed;
 *  The die message:
 *   svnversion sed failed
 *
 * If you need support, post the topmost build error, and the call stack if 
relevant.
 * A complete build log is located 
at '/var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/temp/build.log'.
 * The ebuild environment file is located 
at '/var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/temp/environment'.
 *

 Failed to emerge media-tv/mythtv-0.21_p18314-r1, Log file:

  '/var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/temp/build.log'
sgc ~ # 


The error seems to be in the line: 
/var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/temp/environment: line 3924: 
cd: 
/var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0-21-fixes/mythtv:
 
No such file or directory

There's a folder missing somewhere, and when I look, sure enough:

sgc ~ # ls /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/
mythtv-0.21_p18314
sgc ~ #  

It seems the work folder has a 'mythtv-0.21_p18314' folder, which has the 
branches folder inside that.

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?

Thanks
Shawn



Re: [gentoo-user] emerge mythtv fails

2009-08-03 Thread Alex Schuster
Shawn Haggett writes:

 Some recent updates have broken my mythtv (missing libraries) so I'm of
 course trying to recompile it. Whenever I try however, the following
 happens:

 sgc ~ # emerge -va mythtv
[...]
 /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/temp/environment: line
 3924: cd:
 /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0-2
1-fixes/mythtv: No such file or directory
 sed: can't
 read
 /var/tmp/portage/media-tv/mythtv-0.21_p18314-r1/work/branches/release-0-2
1-fixes/mythtv/version.pro: No such file or directory

[...]
 It seems the work folder has a 'mythtv-0.21_p18314' folder, which has the
 branches folder inside that.

 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 just had the same problem with a fresh install of mythtv. I tried other 
versions, 0.21_p19961-r2 showed the same problem, but 0.21_p20877 did 
compile. So give that one a try.

No idea where the exact problem lies, I did not even use mythtv yet. Other 
things to do first.

Wonko



Re: [gentoo-user] emerge mythtv fails

2009-08-03 Thread Stroller


On 4 Aug 2009, at 00:07, 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.


I don't yet use MythTV myself, but had reason to investigate it again  
this week.


I saw this mentioned on the MythTV-users list (probably a more useful  
resource for you than this list, TBH). Perhaps you may find it useful:


http://wiki.github.com/MarcT/mt-mythtv

Stroller.





Re: [gentoo-user] emerge mythtv fails

2009-08-03 Thread Brandon Vargo
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