From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: "masked by: EAPI 7" trying up update "portage" - how to proceed
Date: Mon, 15 Jun 2020 20:49:53 +0100 [thread overview]
Message-ID: <1761293.tdWV9SEqCh@peak> (raw)
In-Reply-To: <rc85ai$1auc$1@ciao.gmane.io>
On Monday, 15 June 2020 16:49:39 BST Grant Edwards wrote:
> On 2020-06-15, J. Roeleveld <joost@antarean.org> wrote:
> ><Snipped lengthy output>
> >
> > With a system that has not been updated for over 3 years, I would suggest
> > to Start from scratch and copy the config across.
>
> That's definitely, by far, the fastest and easiest way to get to a
> working, current system.
>
> > If you do insist on trying to work through this,
>
> Which is something many of us have done once just to see if we could.
>
> It's not something one tends to do a second time. :)
Once bitten, twice shy... :)
--
Regards,
Peter.
prev parent reply other threads:[~2020-06-15 19:51 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
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 [this message]
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=1761293.tdWV9SEqCh@peak \
--to=peter@prh.myzen.co.uk \
--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