On 2020-06-14 10:23, n952162 wrote:
On 2020-06-14 00:05, n952162 wrote:
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.
Unfortunately, I couldn't get that to work, using this command, first
with tgt=@world, then @system, then portage, I got thousands of lines of
output before failure to calculate the dependencies. Log files attached
(world contains both @world and @system).
sudo $HOME/adm/gentoo/src/portage/bin/emerge -vuUD --backtrack=100
--with-bdeps=y $tgt
I see that there are new lines in the dependencies table that I've never
encountered before:
[blocks B ] <x11-proto/randrproto-1.5.0-r1
("<x11-proto/randrproto-1.5.0-r1" is blocking x11-base/xorg-proto-2019.2)
I get these (using the emerge from the git repository) for all of
@world, @system, and portage.
Is there a way to handle that?
