From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "masked by: EAPI 7" trying up update "portage" - how to proceed
Date: Mon, 15 Jun 2020 16:20:24 +0200 [thread overview]
Message-ID: <4585048.31r3eYUQgx@eve> (raw)
In-Reply-To: <ad9a6d99-b41e-0d72-7f9d-2acf07a9b61e@web.de>
On Monday, June 15, 2020 1:26:06 PM CEST n952162 wrote:
> Thank you for the response. Unfortunately it didn't work. The logs are
> attached (tgt=portage, system, world) and summarized below.
>
> Perl keeps coming up as a problem, so, as an example, I tried to build
> perl, including all the packages that say they need it on the command
> line. Emerge comes back with the same result. I can't understand why,
> e.g. Data-Dump requires perl 5.24:
>
> dev-lang/perl:0/5.24=[-build(-)] required by
> (dev-perl/Data-Dump-1.230.0:0/0::gentoo, installed) USE="" ABI_X86="(64)"
>
> when it's included on the command line to re-emerge:
>
> + sudo $HOME/adm/gentoo/src/portage/bin/emerge -vuUD --verbose-conflicts
> --backtrack=100 --with-bdeps=y dev-perl/Text-CharWidth
> dev-perl/HTML-Tree *dev-perl/Data-Dump* dev-perl/TermReadKey
> dev-perl/HTML-Form dev-perl/LWP-MediaTypes dev-perl/XML-Parser
> dev-perl/Text-WrapI18N app-text/po4a dev-perl/HTTP-Date
> dev-perl/Unicode-EastAsianWidth dev-perl/IO-HTML dev-perl/SGMLSpm
> dev-perl/Locale-gettext dev-perl/WWW-Mechanize dev-perl/HTML-Tagset
> dev-perl/Date-Manip dev-perl/File-Listing dev-lang/perl
>
<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.
If you do insist on trying to work through this, I would suggest the following
(READ and understand all steps before executing any):
0) Make sure you do NOT change your profile. (As you adjusted it from 13.0 to
17.1, change it back to 13.0, or if not available, 17.0)
- Profile 17.1 is NOT going to work at this point.
1) Rename the world and world_sets files to (temporarily) clear the entire
world-set
(These files are located in "/var/lib/portage")
2) execute: "emerge -vauDN --with-bdeps=y --backtrack=200 @world" and
alternate with "emerge --update --newuse --deep @world" until both have
nothing left to do.
3) execute "emerge -va --depclean"
- This is a LARGE set, don't worry, it will all come back (You DID backup the
files in step 1, right?)
4) Fix any config-file changes that are left over and follow this with steps
"2", "3" and "4" until your system is clean.
5) Install, configure and compile the kernel and ensure you can reboot the
system. (This is important for the next step)
6) Follow the news-item regarding migrating to 17.1 and follow this exactly.
(Your install is extremely basic, so it should be nice and easy)
7) Reinstall all needed software (read your world and world_set backup-files
to see what you had before and ONLY install those that you actually need)
8) Fix any config-files that are needed for the software you re-installed in
step 7
9) Congratulate yourself for managing to upgrade a system after 3+ years
In my experience, when the system has not been updated for this long, the
fastest way to resolve this is to start from scratch with a backup of any
config and data files.
--
Joost
next prev parent reply other threads:[~2020-06-15 14:22 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 [this message]
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=4585048.31r3eYUQgx@eve \
--to=joost@antarean.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