From: "Kurt V. Hindenburg" <khindenburg@cherrynebula.net>
To: Alastair Tse <liquidx@gentoo.org>, Gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] not missing feature for package.unmask
Date: Wed, 11 Jun 2003 09:21:26 -0500 [thread overview]
Message-ID: <200306110921.29928.khindenburg@cherrynebula.net> (raw)
In-Reply-To: <1055336886.20630.94.camel@huggins.eng.cam.ac.uk>
On Wednesday 11 June 2003 8:08 am, Alastair Tse wrote:
| On Wed, 2003-06-11 at 01:02, Kurt V. Hindenburg wrote:
| > Calculating dependencies /
| > !!! all ebuilds that could satisfy "app-crypt/cryptplug" have
| > been masked.
|
| Maybe because you're on a x86 profile and not ~x86?
|
| % fgrep KEYWORDS cryptplug-0.3.15.ebuild
| KEYWORDS="~x86 ~ppc"
|
| AFAIK, that package.unmask only affects things in pacakge.mask, you
| are still restricted by ACCEPT_KEYWORDS.
|
Hmmm, I'm not sure I follow...why does a search on cryptplug says it
is masked?
* app-crypt/cryptplug [ Masked ]
Latest version available: 0.3.15
Latest version installed: 0.3.15
Size of downloaded files: 213 kB
Homepage: http://www.gnupg.org/
Description: GPG and S/MIME encryption plugins. Use by KMail
v1.5 (KDE 3.1) and Mutt
So package.unmask only reverses stuff in package.mask?
--
Kurt
---
There is no good and evil; there is only power.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-11 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 20:56 [gentoo-dev] Missing feature for Christian Aust
2003-06-09 21:28 ` Daniel Armyr
2003-06-09 21:52 ` Christian Aust
2003-06-09 22:05 ` Marius Mauch
2003-06-09 22:08 ` Kumba
2003-06-10 8:21 ` [gentoo-dev] not missing feature for package.unmask Stanislav Brabec
2003-06-11 0:02 ` Kurt V. Hindenburg
2003-06-11 13:08 ` Alastair Tse
2003-06-11 14:21 ` Kurt V. Hindenburg [this message]
[not found] <web-230543@kdmail.aixsequo.de>
2003-06-11 14:11 ` Kurt V. Hindenburg
2003-06-11 14:28 ` Georgi Georgiev
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=200306110921.29928.khindenburg@cherrynebula.net \
--to=khindenburg@cherrynebula.net \
--cc=gentoo-dev@gentoo.org \
--cc=liquidx@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