From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "masked by: EAPI 7" trying up update "portage" - how to proceed
Date: Thu, 11 Jun 2020 19:09:03 -0400 [thread overview]
Message-ID: <CAGfcS_kbR+hRvVxUYWh6SJM=nApgWc-dgmGJT=XZHW1T=rmHig@mail.gmail.com> (raw)
In-Reply-To: <bb87cb06-118f-52f2-0ac3-f6d4a6d85fdc@web.de>
On Thu, Jun 11, 2020 at 5:45 PM n952162 <n952162@web.de> wrote:
>
>
> * portage-2.3.89-bug-718578.patch BLAKE2B SHA512 size ;-)
> ... [ ok ]
> * Please follow the instructions in the news item:
> * 2019-06-05-amd64-17-1-profiles-are-now-stable
> * or choose the 17.0 profile.
> * ERROR: sys-apps/portage-2.3.99-r2::gentoo failed (setup phase):
> * ERROR: 17.1 migration has not been performed!!
You switched to the 17.1 profile without following the instructions in
the news item you said you read. :)
eselect news read 2019-06-05-amd64-17-1-profiles-are-now-stable
What profile were you on before you started messing with everything?
Hopefully that was 17.0 because if not you need to do a migration for
that, which is the subject of another news item.
If you were on 17.0 before then I would finish getting all packages up
to date on 17.0 before moving to 17.1. The first step of the 17.1
migration instructions is to make sure all your packages are up to
date, and yours obviously are not.
Really though you do not want to go changing profiles without reading
all the news.
BTW, is it becoming clear why it is best to update Gentoo at least
ever few months? :)
--
Rich
next prev parent reply other threads:[~2020-06-11 23:09 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 6:47 [gentoo-user] "masked by: EAPI 7" trying up update "portage" - how to proceed n952162
2020-06-11 8:10 ` Neil Bothwick
2020-06-11 12:47 ` Rich Freeman
2020-06-11 19:36 ` n952162
2020-06-11 20:01 ` Rich Freeman
2020-06-11 20:10 ` n952162
2020-06-11 21:05 ` Jack
2020-06-11 21:10 ` n952162
2020-06-11 21:22 ` n952162
2020-06-11 21:59 ` Jack
2020-06-11 22:05 ` n952162
2020-06-11 22:43 ` Jack
2020-06-12 6:32 ` n952162
2020-06-14 7:01 ` n952162
2020-06-14 16:02 ` antlists
2020-06-14 18:22 ` n952162
2020-06-11 21:06 ` Rich Freeman
2020-06-11 21:15 ` n952162
2020-06-11 20:28 ` n952162
2020-06-11 20:35 ` Rich Freeman
2020-06-11 20:43 ` n952162
2020-06-11 21:20 ` Rich Freeman
2020-06-11 21:45 ` n952162
2020-06-11 22:09 ` n952162
2020-06-11 23:09 ` Rich Freeman [this message]
2020-06-12 6:40 ` n952162
2020-06-12 8:00 ` n952162
2020-06-12 13:49 ` Rich Freeman
2020-06-12 14:00 ` Jack
2020-06-12 14:38 ` Michael
2020-06-12 14:42 ` J. Roeleveld
2020-06-12 14:48 ` n952162
2020-06-12 14:53 ` Rich Freeman
2020-06-12 14:50 ` Michael
2020-06-12 14:44 ` n952162
2020-06-12 14:52 ` Michael
2020-06-12 17:15 ` Peter Humphrey
2020-06-12 14:50 ` Rich Freeman
2020-06-12 15:05 ` Jack
2020-06-12 15:14 ` Michael
2020-06-12 13:45 ` Rich Freeman
2020-06-11 19:07 ` n952162
2020-06-13 19:42 ` Andreas K. Hüttel
2020-06-13 22:05 ` n952162
2020-06-14 8:23 ` n952162
2020-06-14 20:07 ` n952162
2020-06-14 22:06 ` Neil Bothwick
2020-06-15 11:26 ` n952162
2020-06-15 14:20 ` J. Roeleveld
2020-06-15 14:36 ` n952162
2020-06-15 15:49 ` [gentoo-user] " Grant Edwards
2020-06-15 16:25 ` J. Roeleveld
2020-06-15 19:49 ` Peter Humphrey
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='CAGfcS_kbR+hRvVxUYWh6SJM=nApgWc-dgmGJT=XZHW1T=rmHig@mail.gmail.com' \
--to=rich0@gentoo.org \
--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