public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jakob Buchgraber <jakob.buchgraber@googlemail.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 14:48:31 +0100	[thread overview]
Message-ID: <45D8592F.8050601@gmail.com> (raw)
In-Reply-To: <45D7FC18.1090105@stepien.com.pl>

Jan Stępień wrote:
> Hi everyone,
>
>
>
> # emerge -avDu world
>
> These are the packages that would be merged, in order:
>
> Calculating world dependencies |
> !!! All ebuilds that could satisfy "~x11-plugins/beryl-plugins-0.1.99.2"
> have been masked.
> !!! One of the following masked packages is required to complete your
> request:
> - x11-plugins/beryl-plugins-0.1.99.2 (masked by: missing keyword)
>
> For more information, see MASKED PACKAGES section in the emerge man page or
> refer to the Gentoo Handbook.
> (dependency required by "x11-wm/beryl-core-0.1.99.2" [ebuild])
>
> !!! Problem resolving dependencies for x11-wm/emerald
> !!! Depgraph creation failed.
>
>
>
> Maybe snippets from my /etc/portage/package.* files will be helpful:
>
> keywords
>
> x11-wm/beryl
> x11-wm/beryl-core
> x11-plugins/beryl-plugins
> x11-plugins/beryl-dbus
> x11-misc/beryl-manager
> x11-misc/beryl-settings
>
> unmask
>
> x11-wm/beryl
> x11-wm/beryl-core
> x11-plugins/beryl-plugins
> x11-plugins/beryl-dbus
> x11-plugins/beryl-vidcap
> x11-misc/beryl-manager
> x11-misc/beryl-settings
>
>
>
> I'm not very familiar with unmasking system, so most probably an answer
> to the question I'm asking is more than just obvious - if so, accept my
> apologies. Nevertheless, I would be grateful for your support.
>
> Best regards,
> Jan Stępień
>
>   
Hey!

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

Cheers,
Jay

-- 
My system configuration (Gentoo Linux): http://www.linux-stats.org/index.php?c=userpage&sys=810
Registered Linux User #373457

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-02-18 12:52 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 [this message]
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.
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=45D8592F.8050601@gmail.com \
    --to=jakob.buchgraber@googlemail.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