From: "Corentin “Nado” Pazdera" <nado@troglodyte.be>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update circle
Date: Wed, 22 Aug 2018 09:40:29 +0000 [thread overview]
Message-ID: <b0681ecb7bba9676c244746fb336aa92@troglodyte.be> (raw)
In-Reply-To: <20180822191554.55798b0f@linux-0ft9>
August 22, 2018 11:16 AM, "Zoltán Kócsi" <zoltan@bendor.com.au> wrote:
> Corentin,
>
>> What does emerge -vuDN --verbose-conflicts --with-bdeps=y world say?
>
> $ emerge -vuDN --verbose-conflicts --with-bdeps=y world
>
> !!! Invalid news item:
> /usr/portage/metadata/news/2017-11-21-old-wine-versions-moving-to-overlay/2017-11-21-old-wine-versio
> s-moving-to-overlay.en.txt !!!
> line 5: News-Item-Format: 2.0
>
> [ ... several more warnings like the above ... ]
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
>
> !!! Ebuilds for the following packages are either all
> !!! masked or don't exist:
> sys-apps/elfix
>
> !!! All ebuilds that could satisfy ">=app-portage/elt-patches-20170422"
> have been masked. !!! One of the following masked packages is required
> to complete your request:
> - app-portage/elt-patches-20170826.1::gentoo (masked by: EAPI 6)
> - app-portage/elt-patches-20170815::gentoo (masked by: EAPI 6)
> - app-portage/elt-patches-20170422::gentoo (masked by: EAPI 6)
>
> The current version of portage supports EAPI '5'. You must upgrade to a
> newer version of portage before EAPI masked packages can be installed.
> (dependency required by "app-admin/logrotate-3.9.1::gentoo" [ebuild])
> (dependency required by "@selected" [set])
> (dependency required by "@world" [argument])
> For more information, see the MASKED PACKAGES section in the emerge
> man page or refer to the Gentoo Handbook.
>
>> What’s your portage version?
>
> $ equery -q list "*/*" | grep portage
> app-portage/gentoolkit-0.3.0.8-r2
> app-portage/pfl-2.4-r3
> app-portage/portage-utils-0.41
> sys-apps/portage-2.2.18
>
>> What profile are you using? (eselect profile show)
>
> $ eselect profile show
> Current /etc/portage/make.profile symlink:
> hardened/linux/x86
>
>> What is your gcc version?
>
> $ gcc --version
> gcc (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) 4.7.3
> Copyright (C) [...]
>
> Thanks!
>
> Best Reagrds,
>
> Zoltan
Given how old this system is, I think it will be easier to setup a chroot with latest stage3 and buildpkg system tools in it.
From the top of my head, you’d need to repackage portage and deps, python, gcc (you will love that one).
I suggest reading the wiki for gcc upgrades as 4.7.3 is really old.
Regards,
Corentin “Nado” Pazdera
next prev parent reply other threads:[~2018-08-22 9:40 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 [this message]
2018-08-22 9:18 ` Neil Bothwick
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=b0681ecb7bba9676c244746fb336aa92@troglodyte.be \
--to=nado@troglodyte.be \
--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