* [gentoo-catalyst] resolving portage keywords issue from within catalyst?
@ 2013-12-19 0:07 lin pro
2013-12-19 1:43 ` Rick "Zero_Chaos" Farina
2013-12-19 1:48 ` Jorge Manuel B. S. Vicetto
0 siblings, 2 replies; 3+ messages in thread
From: lin pro @ 2013-12-19 0:07 UTC (permalink / raw
To: gentoo-catalyst
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-catalyst] resolving portage keywords issue from within catalyst?
2013-12-19 0:07 [gentoo-catalyst] resolving portage keywords issue from within catalyst? lin pro
@ 2013-12-19 1:43 ` Rick "Zero_Chaos" Farina
2013-12-19 1:48 ` Jorge Manuel B. S. Vicetto
1 sibling, 0 replies; 3+ messages in thread
From: Rick "Zero_Chaos" Farina @ 2013-12-19 1:43 UTC (permalink / raw
To: gentoo-catalyst
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/18/2013 07:07 PM, lin pro wrote:
> 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.
>
Perhaps did you forget to set "portage_confdir:"? You point that to
your /etc/portage directory which you wish used for catalyst.
- -Zero
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSsk8/AAoJEKXdFCfdEflK254P/13kQWSdWeJB0OpFPzwIgMzh
2Ohmxf9vtKgDus6H5IG92PkwBhi1P9YjwIMVLXbecLGqUoH2twi9RHY1AavE5YdN
bJnpVU6QqOoe2KZXZzeKC8PLsVtr0GL1rMFb29cdgSIFg9JcnNj+FT7nKywhw5Ii
Y329G0kRjR2O3nS0j8vRxNfSc6Yz4IXEdIQeRdI2UFz2pQ3AzDESFB493z8VbrTQ
ug26DQTDCg7fPjQSKWPl3VsupZsXAJYO3P6llTded1vu/NlU2+CLsWlcvmHtLS8D
SSGICjPg7DWAG+isfAZuhyuBgzdcNDB6UF7anmg2ZL4YJ1HOmLWg0yjccIV7Loqd
t6Z+LVTFJS6tJoApbkuKrxY1QD2/Oap+XO/DtVFQBLBtoxn6Y3pPGol12lDIq5ci
OfaUzCIccRGOrDcgJSROGreNOW0q5pIkt3ZrJWGBThisu+mz516WlaFQVVKiYOau
eyoOmySqv6GouSX5GkR83sXSZ3qBN+LQonwGIAoPWhHgLKZi2uXTm9sXbfbJCL4Y
dbXa2CD9EJwyfkSQblWSnUB5mbFHLPm0CU2FtZ3tRGaLJAYcfjRPNW2VFjQNL+hR
KBD9pEn8B/V465kXxI3D6RnDdOso7sjCqCN2Du54yqbobYZOEmIVY61T+rfrK51R
T6fOMrCD6wldplJx8Hap
=lx50
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-catalyst] resolving portage keywords issue from within catalyst?
2013-12-19 0:07 [gentoo-catalyst] resolving portage keywords issue from within catalyst? lin pro
2013-12-19 1:43 ` Rick "Zero_Chaos" Farina
@ 2013-12-19 1:48 ` Jorge Manuel B. S. Vicetto
1 sibling, 0 replies; 3+ messages in thread
From: Jorge Manuel B. S. Vicetto @ 2013-12-19 1:48 UTC (permalink / raw
To: gentoo-catalyst
On Wed, 18 Dec 2013, lin pro wrote:
> Hi,
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
Catalyst doesn't use any of the /etc/portage files on your host. You need
to use the portage_confdir var in the spec files to tell catalyst to use
it when building the stage.
You can check an example of its use in releng's official repository[1].
You can see how we use it on the installcd specs[2][3] and an example of
the portage config dir for the installcd[4] and the admincd[5].
[1] - http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git
[2] -
http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=blob;f=releases/weekly/specs/amd64/installcd-stage1.spec;h=0bb6777efd2c6151edae44250d1ba708ec929784;hb=refs/heads/master
[3]
-http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=blob;f=releases/weekly/specs/amd64/installcd-stage2-minimal.spec;h=9f2a231c7c9f2eb36ff934a01a900c196c3998f6;hb=refs/heads/master
[4] -
http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=tree;f=releases/weekly/portage/installcd;h=cf9e9fd3c801e505b23f2c57c9689a93c6094313;hb=refs/heads/master
[5] -
http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=tree;f=releases/weekly/portage/admincd;h=3c2b52a416aa991af1b246bc12dec902b08b4139;hb=refs/heads/master
> Ben
Regards,
Jorge
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-12-19 1:48 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-19 0:07 [gentoo-catalyst] resolving portage keywords issue from within catalyst? lin pro
2013-12-19 1:43 ` Rick "Zero_Chaos" Farina
2013-12-19 1:48 ` Jorge Manuel B. S. Vicetto
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox