public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gregory Shearman <zekeyg@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge mythtv fails... again
Date: Wed, 19 Aug 2009 18:08:15 +1000	[thread overview]
Message-ID: <20090819080815.GA17419@pacific.net.au> (raw)
In-Reply-To: <daD0P-7xh-9@gated-at.bofh.it>

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



       reply	other threads:[~2009-08-19  8:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d5ePt-IX-13@gated-at.bofh.it>
     [not found] ` <d5fV9-2rx-7@gated-at.bofh.it>
     [not found]   ` <daD0P-7xh-9@gated-at.bofh.it>
2009-08-19  8:08     ` Gregory Shearman [this message]
2009-08-03 23:07 [gentoo-user] emerge mythtv fails Shawn Haggett
2009-08-04  0:10 ` Alex Schuster
2009-08-18 19:55   ` [gentoo-user] emerge mythtv fails... again Alex Schuster
2009-08-18 20:39     ` Mark Knecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090819080815.GA17419@pacific.net.au \
    --to=zekeyg@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox