| View previous topic :: View next topic |
| Author |
Message |
ganzhi
n00b
Joined: 09 Jun 2003
Posts: 7
|
 Posted: Wed Jun 11, 2003 5:12 am Post subject: Can't emerge masked package? |
 |
|
Hi, all!
I use gentoo 1.4 rc 4 in my box. I have set my USE variable like this:
[code]
USE="x86 encode gnome gtk cjk zlib X xmms python truetype jpeg png gif avi emacs -qt -kde"
[code]
Whenever I tried to emerge a masked package, error occurs:
[code]
root@scorpio ganzhi # emerge scim
Calculating dependencies
!!! all ebuilds that could satisfy "scim" have been masked.
!!! Error calculating dependencies. Please correct.
[/code]
Then I want to comment appropriate item in package.mask, but I found
there is no such item. I really need a help!
Thx in advance!  |
|
| Back to top |
|
 |
StuBear
Apprentice
Joined: 26 Feb 2003
Posts: 157
Location: Melbourne,AUSTRALIA
|
| Posted: Wed Jun 11, 2003 5:39 am Post subject: |
|
|
There are 2 types of masking in gentoo, package.mask for the broken/"may melt your monitor" type ebuilds and ~arch masked packages that work, but may need more tweaking before becoming arch ebuild.
It looks as if scim is an ~x86 masked ebuild, to emerge it you have 3 options.
1. add ~x86 to ACCEPT_KEYWORDS in /etc/make.conf
2. emerge using the following
ACCEPT_KEYWORD="~x86" emerge scim
3. emerge using the complete path to the ebuild
emerge /usr/portage/some-cat/scim/scim-0.0.ebuild
The 2nd and 3rd option are probably what you want.
Hope this helps
_________________
Since it is the optimal DVD-RAM correspondence for backup of personal computer data, and lighting soft needlessness, it is data preservation by floppy disk feeling. |
|
| Back to top |
|
|
ganzhi
n00b
Joined: 09 Jun 2003
Posts: 7
|
| Posted: Thu Jun 12, 2003 1:07 am Post subject: It works! |
|
|
That's what I need.
Thank you very much. It's so kind of you to be patient. |
|
| Back to top |
|
|
riceboy50
n00b
Joined: 12 Nov 2002
Posts: 48
Location: Southern CA
|
| Posted: Thu Jun 12, 2003 6:27 am Post subject: differentiating the different type of masks? |
|
|
I had the same problem when trying to emerge bootsplash (I wanted to see what all the hype was about from a different thread on this forum) but I got the masked error. How can you tell the difference between the totally broken ebuilds that will, as you put so eloquently, "melt your monitor" and the ones that work but just aren't in the official portage tree yet? This is pretty useful information. Thanks for posting it.
_________________
I am logged on therefore I am... |
|
| Back to top |
|
|
StuBear
Apprentice
Joined: 26 Feb 2003
Posts: 157
Location: Melbourne,AUSTRALIA
|
| Posted: Thu Jun 12, 2003 9:37 am Post subject: |
|
|
The easiest way I know is to have a look in the ebuild file and see what the value is for KEYWORDS (should be near the top). If you see a ~x86 (or ~ppc id that is your flavour) then the package is masked due to testing.
THe other way is to type | Code: | | ACCEPT_KEYWORDS="~x86" emerge package -p |
if it shows up then it is ~arch, if it's still masked then it in pakage.mask.
_________________
Since it is the optimal DVD-RAM correspondence for backup of personal computer data, and lighting soft needlessness, it is data preservation by floppy disk feeling. |
|
| Back to top |
|
|
|
Portage & Programming
