From: lin pro <linforpros@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] resolving portage keywords issue from within catalyst?
Date: Wed, 18 Dec 2013 18:07:57 -0600 [thread overview]
Message-ID: <CACU8XWk7b_=UsEKr2fEyvUpK9UAO5SYUcmWHz5K+DKtHmwK8dA@mail.gmail.com> (raw)
Hi,
Here is the spec file that is causing trouble http://bpaste.net/show/159985/
Catalyst stop with this message:
The following keyword changes are necessary to proceed:
(see "package.accept_keywords" in the portage(5) man page for more details)
# required by dev-ml/ocaml-mad (argument)
=dev-ml/ocaml-mad-0.4.4 ~amd64
...and many more.
Now the /etc/portage/package.keywords has this inside
grep ocaml-mad /etc/portage/package.*
/etc/portage/package.keywords:dev-ml/ocaml-mad ~amd64
Even if I put put the keyword in package.accep_keywords the behaviour
of catalyst is the same.
It seems that catalyst does not read those files for me.
Thank you for hints
Ben
--
best regards
linforpros
next reply other threads:[~2013-12-19 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 0:07 lin pro [this message]
2013-12-19 1:43 ` [gentoo-catalyst] resolving portage keywords issue from within catalyst? Rick "Zero_Chaos" Farina
2013-12-19 1:48 ` Jorge Manuel B. S. Vicetto
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='CACU8XWk7b_=UsEKr2fEyvUpK9UAO5SYUcmWHz5K+DKtHmwK8dA@mail.gmail.com' \
--to=linforpros@gmail.com \
--cc=gentoo-catalyst@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