From: n952162 <n952162@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "masked by: EAPI 7" trying up update "portage" - how to proceed
Date: Sun, 14 Jun 2020 00:05:03 +0200 [thread overview]
Message-ID: <ab79ae78-20db-e2a4-a76f-49ef65715ab5@web.de> (raw)
In-Reply-To: <2499156.vuYhMxLoTh@farino>
cool! I'll give that a try tomorrow.
Thank you.
On 2020-06-13 21:42, Andreas K. Hüttel wrote:
> Am Donnerstag, 11. Juni 2020, 09:47:50 EEST schrieb n952162:
>> I haven't clue what to do here. Can somebody supply a good URL or
>> explanation?
>>
> In the meantime a new ebuild format version (EAPI) has been introduced; your
> old portage can't process that, and as a result doesnt understand many new
> ebuilds.
>
> Portage disregards ebuilds where it doesnt know the format, but of course if
> these are needed to update Portage itself, you're somewhat screwed.
>
> Luckily there is a very simple workaround.
>
> Download a recent portage (the packager) tarball, or clone git master portage:
> https://anongit.gentoo.org/git/proj/portage.git
>
> Then run the "emerge" command inside that checkout, by giving its full path,
> the same way as you would otherwise run emerge. This updates your system and
> ideally afterwards your system portage is new and shiny, so you can delete the
> git clone again.
>
next prev parent reply other threads:[~2020-06-13 22:05 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
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 [this message]
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=ab79ae78-20db-e2a4-a76f-49ef65715ab5@web.de \
--to=n952162@web.de \
--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