public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage world update fails because of masked beryl-plugins
Date: Sun, 18 Feb 2007 16:35:21 -0600	[thread overview]
Message-ID: <200702181635.26929.bss03@volumehost.net> (raw)
In-Reply-To: <45D8D10D.8030105@stepien.com.pl>

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

On Sunday 18 February 2007, Jan Stępień <jan@stepien.com.pl> wrote 
about 'Re: [gentoo-user] Portage world update fails because of masked 
beryl-plugins':
> >>> x11-plugins/beryl-plugins-0.1.99.2 (masked by: missing keyword)
>
> I've tried to unmask it with keywords "~x86", "~*", "*" and even "-*"
> but still I've got the same error. I'm afraid that * wildcard isn't
> working and I can't guess the correct keyword. Have you got any further
> suggestions?

I don't have an ebuild for that version on beryl, so I can't tell you what 
keywords can be used.  But, I can tell you how to find out.

e.g.:
$ grep KEYWORD beryl-plugins-0.1.3.ebuild
KEYWORDS="~amd64 ~ppc ~ppc64 ~x86"

So, you can simply find the KEYWORDS variable in the ebuild you are trying 
to use and add one of those keywords to your package.keywords.  Of course, 
if you do anything other than ~${ARCH}, where ${ARCH} is your current 
architecture and it breaks, you get to keep both pieces.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     
New GPG Key!  Old key expires 2007-03-25.  Upgrade NOW!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-02-18 22:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18  7:11 [gentoo-user] Portage world update fails because of masked beryl-plugins Jan Stępień
2007-02-18 13:48 ` Jakob Buchgraber
2007-02-18 13:11   ` Mick
2007-02-18 22:14     ` Jan Stępień
2007-02-18 20:37   ` Boyd Stephen Smith Jr.
2007-02-18 22:19   ` Jan Stępień
2007-02-18 22:35     ` Boyd Stephen Smith Jr. [this message]
2007-02-19 14:09       ` Jan Stępień
2007-02-19 14:57         ` Boyd Stephen Smith Jr.
2007-02-19 16:52         ` Bo Ørsted Andresen
2007-02-19 20:24           ` Jan Stępień
2007-02-18 22:40     ` Mick
2007-02-19 14:13       ` Jan Stępień

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=200702181635.26929.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --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