What's the criteria to unmask a ~x86 ebuild to x86 ????

[seventhguardian]

Hi there!

I just emerged dev-sources 2.6.7 for need (because of a 2.6.5 bug on udf dvds..). So there's no turning back for me!

The thing is, nvidia-kernel 4496 doesn't work with anything above 2.6.5.. not even 2.6.6. Also nvidia-glx had that problem. So I tried nvidia-kernel 5336, and it worked fine. And is still working great.

The annoying thing is that i can't do a simple "emerge --update world" because it tries to downgrade nvidia-kernel and nvidia-glx. Is there a way of masking these ebuilds in order to avoid their downgrade?

Also, nvidia-kernel 5336 is working fine for me, and I haven't noticed anything wrong with it. Since now most of the people building new systems will use 2.6.7, those that have nvidia cards are FORCED to use ~x86 ebuilds. So that cancels out all the "choices", right?

So when will the "~x86" nvidia-kernel and nvidia-glx be unmasked to the "x86" group?? They've been there for so long, that I wonder if someone hasn't forgotten them...

[RobMcM]

Well, you can do it two ways (probably more...):

1) NOT the way to do it:

Code: Select all

#ACCEPT_KEYWORDS='~x86' emerge nvidia-blahblah
. . .
#emerge -U world

The -U is --upgrade-only, rather than just -u (--update). It does not downgrade, but this can cause problems: e.g. an ebuild might be removed for security reasons, but you wouldn't downgrade...

2) The way to do it:

In /etc/portage/package.keywords:

Either

a) To unmask all unstable packages:

Code: Select all

media-video/nvidea-glx ~x86
media-video/nvidea-kernel ~x86

or

b) to unmask a specific version

Code: Select all

~ media-video/nvidea-glx-1.0.5336 ~x86
~ media-video/nvidea-kernel-1.0.5336 ~x86

Note the use of ~. This means all ebuilds in the 1.0.5336 series, such as 1.0.5336-r1, 1.0.5336-r2 etc. If you had used >= it would unmask all above or equal to 1.0.5336, not just revisions of it. = would only unmask that specific version.

Now when you do an emerge -u world (emerge --update world) it will use the unmasked versions...

HTH

[seventhguardian]

hi!

thanks a lot! It worked! no more manual world update to me

By the way, anyone knows who is responsable for the masking and unmasking of the portage ebuilds? I guess noobs like me should be able to install gentoo without any "dangerous" options like "~x86".. We should only need to face this kind of danger after a bit of experience on breaking things..

[kallamej]

You know, there are quite a few threads about the nvidia drivers and 2.6.* kernels. They fall into two categories:

• Why is 5336 still masked?
• 5336 doesn't work

Add to that that Gentoo officially doesn't support 2.6 kernels (they're still considered development-sources ). That should explain this particular case. An answer to your general question can be found here.

[seventhguardian]

Thanks a lot!

That is *exactly* what i was looking for too

I'll keep my eyes on that. My first experience with linux was on september last year, so I'm obviously a noob... But I'm reading a lot of stuff about "how the linux guts look like", so I can realy start helping!

By the way, I think there should be THREE groups of ebuilds: those that are stable, those that are almost stable but need more testing, and those that have serious bugs or are realy new and still unknown..

Also it would help if there was more info about bugs and stuff, and how to realy help and specially how to "not bloat" the bug tracking systems with "can you help me" bugs.. It should be the first chapter of the "install guide"!!

Still a noob, but dying to learn Thanks!!

[RobMcM]

There are already three: arch, ~arch and -arch (e.g. x86, ~x86, -x86). -arch either don't work, or have serious bugs, ~arch usually seem to work (for me at least...)

[seventhguardian]

oops noob strikes again..... sorry!