Re: [gentoo-user] Odd portage / eix behavior

[Eric Martin]

Alan McKinnon wrote:
> On Friday 08 August 2008 19:58:46 Eric Martin wrote:
>> On one of my boxes, eix shows every package as (*) which is testing for
>> my current arch but stable on some other.  emerge --info reports x86 as
>> my arch, so I don't know what the problem is.  I don't think it's a huge
>> problem as it's just an annoyance but I might be missing something.  I
>> don't know where to start on google / forums so I figured I'd start here.
>
> I recall something similar happening to me a while ago, on a disconnected box
> that hadn't been updated for 6 months. I was getting weird status symbols just
> like you after a sync. In my case, an upgrade to the latest ~arch portage
> fixed it.
>
> You seem to be running purely x86 right? I assume as a first step you have
> done all the sensible things - remerge latest stable portage, emerge --sync,
> checked /etc/portage/* for silly masks that you forgot about?
>
>

Yes to everything except the 'purely x86'.  I'm running ~x86 on a few things

dev-perl/Video-Frequencies      ~x86
dev-perl/Video-ivtv             ~x86
media-tv/ivtv                   ~x86
app-misc/lirc                   ~x86
x11-drivers/xf86-video-ivtv     ~x86
sys-power/powertop              ~x86
app-admin/puppet                ~x86
dev-ruby/facter                 ~x86
media-tv/mythtv                 ~x86

Portage is 2.1.4.4 which my other computers are running.  This was my 
local rsync mirror that sync'd every two days and my other machines 
sync'd off of it.

This is actually happening on two boxes, although I created the problem 
on the second.  It's my mythbox, and I cloned the box via rsync to make 
a myth-dev box so I can fix it without downtime.  My wife is ready to 
kill me every time I break the mythbox.  Portage didn't have the problem 
on myth-dev, and then I rsync'd over and the problem was created so I 
know it's some setting somewhere...

-- 
Eric Martin
Key fingerprint = D1C4 086E DBB5 C18E 6FDA  B215 6A25 7174 A941 3B9F