public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 22:40:43 +0000	[thread overview]
Message-ID: <200702182240.45692.michaelkintzios@gmail.com> (raw)
In-Reply-To: <45D8D10D.8030105@stepien.com.pl>

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

On Sunday 18 February 2007 22:19, Jan Stępień wrote:
> Jakob Buchgraber napisał(a):
> > Jan Stępień wrote:
> >> # 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.
> >
> > 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
>
> 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?

You may want to have a go by adding:

~x11-plugins/beryl-plugins-0.1.99.2

or, 

=x11-plugins/beryl-plugins-0.1.99.2 ~x86  (if you don't want subsequent 
upgrades to unstable packages)

to your /etc/portage/package.keywords file and then run:

# emerge -upDv beryl-plugins 

to see if it is being picked up.  You may discover additional masked 
dependencies at this stage and you will need to unmask them in turn.

HTH
-- 
Regards,
Mick

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

  parent reply	other threads:[~2007-02-18 22:46 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.
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 [this message]
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=200702182240.45692.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