From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage world update fails because of masked beryl-plugins
Date: Sun, 18 Feb 2007 13:11:08 +0000 [thread overview]
Message-ID: <200702181311.18624.michaelkintzios@gmail.com> (raw)
In-Reply-To: <45D8592F.8050601@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
On Sunday 18 February 2007 13:48, Jakob Buchgraber wrote:
> Jan Stępień wrote:
> > For more information, see MASKED PACKAGES section in the emerge man page
> > or refer to the Gentoo Handbook.
[snip...]
> There is one interesting part in the output of emerge
>
> >> x11-plugins/beryl-plugins-0.1.99.2 (masked by: missing keyword)
>
> This means that the package hasn't been tested yet.
> So you need to replace the following in package.keywords
> x11-plugins/beryl-plugins
> by
> x11-plugins/beryl-plugins ~x86
>
> If you are using another architecture than x86 (like amd64) you need to
> write ~amd64 instead
Before you do any of the above I suggest that you read MASKED PACKAGES section
and KEYWORDS section within man emerge. It's better that you understand what
you are masking/unmasking in the long run and why.
--
Regards,
Mick
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-02-18 13:17 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 [this message]
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.
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=200702181311.18624.michaelkintzios@gmail.com \
--to=michaelkintzios@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