public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: madscientistatlarge <madscientistatlarge@protonmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] How to fix license error during install?
Date: Sat, 21 Mar 2020 02:39:09 +0000	[thread overview]
Message-ID: <sqtTnejr3T0JMBkDDwmCtSYqIw24BHd-9kKLlfCVxe41MR3zGgfEj30OHI5MR_QZgVqU7EdL1mk7Mb5IdNAwFgUodqZCI73WBqdpPCCHFGo=@protonmail.com> (raw)
In-Reply-To: <CAH8yC8n2S6qfADfg8LNiWZJo-wG_VgWPPS8GDjYY7CX=jTJQng@mail.gmail.com>

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, March 20, 2020 8:18 PM, Jeffrey Walton <noloader@gmail.com> wrote:

> On Fri, Mar 20, 2020 at 10:16 PM John Covici covici@ccs.covici.com wrote:
>
> > On Fri, 20 Mar 2020 21:16:10 -0400,
> > Jeffrey Walton wrote:
> >
> > > Hi Everyone,
> > > I'm having trouble installing Gentoo in a Virtual Box VM for testing.
> > > It is a x86_64 guest. I selected a hardened profile to test PaX, which
> > > means I selected 18 in 'eselect profile'.
> > > I'm at "Configuring the Linux kernel" in the Handbook
> > > (https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Alternative:_Using_genkernel).
> > > The part "emerge --ask sys-kernel/gentoo-sources" seems OK and does
> > > not report errors. The genkernel part fails.
> > > The specific error is:
> > > $ LICENSE_ACCEPT="*" emerge --ask --autounmask-write
> > > sys-kernel/genkernel 2>&1 | tee kernel.txt
> > > $ cat kernel.txt
> > >
> > > -   IMPORTANT: 6 config files in '/etc/portage' need updating.
> > >     Calculating dependencies * See the CONFIGURATION FILES and
> > >     CONFIGURATION FILES UPDATE TOOLS
> > >
> > > -   sections of the emerge man page to learn how to update config files.
> > >     ... done!
> > >     [ebuild N ] app-arch/cpio-2.12-r1 USE="nls"
> > >     [ebuild N ] sys-kernel/linux-firmware-20200316
> > >     USE="redistributable -initramfs -savedconfig (-unknown-license)"
> > >     [ebuild N ] sys-kernel/genkernel-4.0.4 USE="firmware (-ibm)"
> > >
> > >
> > > The following license changes are necessary to proceed:
> > > (see "package.license" in the portage(5) man page for more details)
> > >
> > > required by sys-kernel/genkernel-4.0.4::gentoo[firmware]
> > >
> > > =========================================================
> > >
> > > required by genkernel (argument)
> > >
> > > =================================
> > >
> > > =sys-kernel/linux-firmware-20200316 linux-fw-redistributable no-source-code
> > > Autounmask changes successfully written.
> > >
> > > -   IMPORTANT: 7 config files in '/etc/portage' need updating.
> > > -   See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
> > > -   sections of the emerge man page to learn how to update config
> > >     files.Here is the
> > >
> > >
> > > Here is the portage(5) man page:
> > > https://dev.gentoo.org/~zmedico/portage/doc/man/portage.5.html. Here
> > > is the part about package.license:
> > >
> > >     This will allow ACCEPT_LICENSE (see make.conf(5)) to be augmented
> > >
> > >
> > > for a single package.
> > >
> > >     Format:
> > >
> > >         - comment lines begin with # (no inline comments)
> > >         - one DEPEND atom per line followed by additional licenses or groups
> > >
> > >
> > > Removing LICENSE_ACCEPT="*" and --autounmask-write does not help.
> > > The information provided in portage(5) and package.license leaves a
> > > lot to be desired.
> > > What is the problem and how do I fix it?
> >
> > Well, you need to change your config files as portage asked you to do
> > before proceeding. There are several utilities to do that, I use
> > etc-update, but there are several others.
>
> Thanks John.
>
> The Handbook does not say to make any configuration changes. That
> seems safe to me since I have no idea what changes to make.
>
> Jeff

The manual is a starting point, not a step by step guide that tells you enough by itself.  You have to pay attention to what your' system is telling you and look up the things you don't understand.  A lack of configuration of many files will doom later steps.  For example, if you lack substantial shell experience, and even if you don't you will have to learn new things, on your' own or with some help from the list.  If you just do the basic things in the manual, you won't get anywhere.  It's more of an outline with some steps well documented, some over documented, and some not documented properly unless you are smart enough too look up error messages and do what is required.  Most if not all the info is on the gentoo site, but it's your' job to find it.  It's a learning experience,  not a complete and detailed set of instructions.  Part of this is because you have options, you have to chose how some things will be done and investigate.  I strongly recommend using a "tee" etc. to dump everything into text files you can skim.  Often compiling will produce specific suggestions that won't be on the last page of text that scrowls by, you have to read ALL of the output from each step, and learn enough to have some understanding of why and how which will require research on the gentoo site, and often other sites.  You have to modify the "USE" files for each application, as your' machine will tell you, that's actually the easy part.  The hard part involves dealing with issues you don't understand yet.  You have to learn, you have to try and want to learn, and you have to pay attention to what your' computer etc. is trying to tell you.  It's not as trivial as the manual may imply at first.  The people who wrote the various support materials are usually very experienced, that make it hard to anticipate everything someone less experienced may need to be told.  Think about rebuilding an engine, for a highly experienced mechanic it's easy and obvious, to  someone less experienced it requires real thought and learning many things you don't already have burned into your' brain from years of experience.  Fully supporting the less experienced (like myself frankly) is always challenging, because when you learn you won't remember everything to tell someone else in advance, it will be interactive by it's very nature.  Understanding some concepts may be easy for one person, but difficult for another, and it will vary from person to person, brains are not identical.



  reply	other threads:[~2020-03-21  2:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21  1:16 [gentoo-user] How to fix license error during install? Jeffrey Walton
2020-03-21  2:15 ` John Covici
2020-03-21  2:18   ` Jeffrey Walton
2020-03-21  2:39     ` madscientistatlarge [this message]
2020-03-21  7:29     ` Neil Bothwick
2020-03-21  9:34     ` John Covici
2020-03-21 10:22     ` Michael
2020-03-21 14:13 ` Daniel Frey

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='sqtTnejr3T0JMBkDDwmCtSYqIw24BHd-9kKLlfCVxe41MR3zGgfEj30OHI5MR_QZgVqU7EdL1mk7Mb5IdNAwFgUodqZCI73WBqdpPCCHFGo=@protonmail.com' \
    --to=madscientistatlarge@protonmail.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