From: Matt Turner <mattst88@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] How to accept licences
Date: Mon, 27 Jun 2011 12:17:24 -0400 [thread overview]
Message-ID: <BANLkTi=ROhQdAoKYGr6M37FUVXaBtag0NQ@mail.gmail.com> (raw)
In-Reply-To: <assp.01598f2d4f.4E08A512.3050609@kyos.ch>
On Mon, Jun 27, 2011 at 11:43 AM, Martino Dell'Ambrogio
<martino.dellambrogio@kyos.ch> wrote:
> Hello,
>
> I'm trying to build a livecd with catalyst 2.0.6.916.
>
> While building the livecd-stage1 target I've got this obvious error:
>
> !!! All ebuilds that could satisfy "dev-java/sun-jdk" have been masked.
> !!! One of the following masked packages is required to complete your
> request:
> - dev-java/sun-jdk-1.6.0.26 (masked by: dlj-1.1 license(s))
>
> I set portage_confdir to a path with a package.license file containing the
> line "dev-java/sun-jdk dlj-1.1", but I got the same result.
>
> I tried with a package.license directory, with a "*" flag, even with an
> export ACCEPT_LICENSE="*" within catalystrc, but portage seems to ignore all
> of them.
> The portage version is 2.1.9.42 for both host and build. Also both systems
> are amd64.
>
> I can't seem to find my error anywhere, and I guess catalyst is aware of
> everything LICENSE-related or it wouldn't be possible to build the official
> distributions, right? Thank you for your help.
Actually, the only references I see to 'license' when I grep the
catalyst source appear in license headers.
It looks to me like catalyst doesn't export any way to modify
ACCEPT_LICENSES, though I would have thought that putting 'export
ACCEPT_LICENSES=...' in catalystrc would work.
Matt
next prev parent reply other threads:[~2011-06-27 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 15:43 [gentoo-catalyst] How to accept licences Martino Dell'Ambrogio
2011-06-27 16:17 ` Matt Turner [this message]
2011-06-27 16:54 ` Sebastian Pipping
2011-06-27 20:20 ` Martino Dell'Ambrogio
2011-06-27 20:23 ` Matt Turner
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='BANLkTi=ROhQdAoKYGr6M37FUVXaBtag0NQ@mail.gmail.com' \
--to=mattst88@gentoo.org \
--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