From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update circle
Date: Wed, 22 Aug 2018 10:18:07 +0100 [thread overview]
Message-ID: <20180822101807.47092841@digimed.co.uk> (raw)
In-Reply-To: <20180822182443.18693b55@linux-0ft9>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
On Wed, 22 Aug 2018 18:24:43 +1000, Zoltán Kócsi wrote:
> I have a Gentoo machine, which has not been updated for a while. Quite
> a long while, actually.
>
> Now I needed to install a package, and I did so. It went up, no
> problem. Except that it relies on a newer version of openrc than
> what's on the system. From here it's all downhill:
>
> emerge openrc:
> - Fails, as the current portage is EAPI 5 (whatever that is), thus all
> EAPI 6 packages are masked. Must upgrade portage.
>
> emerge portage:
> - Fails, as it needs tar-1.30 and the installed tar is 1.27. Must update
> tar.
>
> emerge tar:
> - Fails, as tar-1.30 needs EAPI 6. Must upgrade portage.
>
> It seems that I'm kind of stuck. Wiping the disk and rebuilding the
> system from scratch is absolutely not an option, the existing (and
> running) system must be updated somehow.
>
> I would appreciate any advice, I'm in complete darkness about the
> internal workings of portage (would be happy to find some detailed docs
> about that, by the way, preferably in PDF).
You don't say what version of portage you have, nor whether you are
running stable or testing. The latest stable postage, 2.3.40-r1, is EAPI
5 and depends on >=tar-1.27. The same is true of the latest testing,
2.3.48. Even the 9999 version depends on tar 1.27, although that one is
EAPI 6. Some actual portage output would be useful here.
--
Neil Bothwick
Irritable? Who the bloody hell are you calling irritable?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-22 9:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 8:24 [gentoo-user] Update circle Zoltán Kócsi
2018-08-22 8:54 ` Corentin “Nado” Pazdera
2018-08-22 9:15 ` Zoltán Kócsi
2018-08-22 9:27 ` Neil Bothwick
2018-08-22 9:42 ` Zoltán Kócsi
2018-08-22 10:11 ` Neil Bothwick
2018-08-22 10:25 ` Arve Barsnes
2018-08-22 9:40 ` Corentin “Nado” Pazdera
2018-08-22 9:18 ` Neil Bothwick [this message]
2018-08-22 14:17 ` [gentoo-user] " Nuno Silva
2018-08-23 10:18 ` Zoltán Kócsi
2018-08-23 10:25 ` Adam Carter
2018-09-01 8:35 ` Wol's lists
2018-09-01 9:39 ` Peter Humphrey
2018-09-01 10:35 ` Wols Lists
2018-09-01 13:24 ` Peter Humphrey
2018-08-23 14:27 ` Grant Edwards
2018-08-31 0:01 ` Taiidan
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=20180822101807.47092841@digimed.co.uk \
--to=neil@digimed.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