public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: package.keywords
Date: Tue, 23 Jun 2009 20:39:10 +0200	[thread overview]
Message-ID: <200906232039.10798.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <loom.20090623T154419-254@post.gmane.org>

On Tuesday 23 June 2009 17:49:40 James wrote:
> Alan McKinnon <alan.mckinnon <at> gmail.com> writes:

> > * removes masking keywords if the package is stable on your arch
> > ~* removes masking keywords if the package is stable on any arch
> > ** removes masking keywords for the package unconditionally
>
> none of these worked for the
> xz-utils package. Can we find a simple example that does work?
> (not enlightenment).....?

You want "app-arch/xz-utils **" in package.keywords. It is blocked by lzma, 
but that entry does at least get the emerge past the mask stage:

nazgul xz-utils # echo "app-arch/xz-utils ~*" > 
/etc/portage/package.keywords/temp
nazgul xz-utils # emerge -av1 xz-utils

These are the packages that would be merged, in order:

Calculating dependencies... done!

!!! All ebuilds that could satisfy "app-arch/xz-utils" have been masked.
!!! One of the following masked packages is required to complete your request:
- app-arch/xz-utils-9999 (masked by: missing keyword)

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

nazgul xz-utils # echo "app-arch/xz-utils **" > 
/etc/portage/package.keywords/temp
nazgul xz-utils # emerge -av1 xz-utils

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] app-arch/xz-utils-9999  0 kB
[blocks B     ] app-arch/lzma-utils ("app-arch/lzma-utils" is blocking app-
arch/xz-utils-9999)

-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2009-06-23 18:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 13:58 [gentoo-user] package.keywords James
2009-06-22 14:08 ` Albert Hopkins
2009-06-22 14:18 ` [gentoo-user] package.keywords James
2009-06-22 15:14   ` Arttu V.
2009-06-22 15:51     ` James
2009-06-22 20:28       ` Alan McKinnon
2009-06-23 14:40         ` James
2009-06-23 14:54           ` Nikos Chantziaras
2009-06-23 15:28             ` James
2009-06-23 15:40               ` Nikos Chantziaras
2009-06-23 16:09                 ` [gentoo-user] ReSOLVED: package.keywords James
2009-06-23 18:42                   ` Alan McKinnon
2009-06-23 14:55           ` [gentoo-user] package.keywords Neil Bothwick
2009-06-23 15:36             ` James
2009-06-23 15:05           ` Alan McKinnon
2009-06-23 15:49             ` James
2009-06-23 18:39               ` Alan McKinnon [this message]
2009-06-22 22:17       ` Neil Bothwick
2009-06-22 23:17         ` Dale
2009-06-22 23:45           ` Neil Bothwick
2009-06-23  6:42           ` Alan McKinnon
2009-06-23  6:51             ` Dale
2009-06-23  7:33               ` Neil Bothwick
2009-06-23  7:38                 ` Dale
2009-06-23  8:27                   ` Alan McKinnon
2009-06-23  9:16                     ` Weitao Sun
2009-06-23  9:18                     ` Dale
2009-06-23 10:16                     ` Neil Bothwick
2009-06-23 10:51       ` Arttu V.

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=200906232039.10798.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@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