On 28.03.2013 21:49, Michael Orlitzky wrote:
On 03/28/2013 01:43 PM, Nick Khamis wrote:
First hickup
emerge -puDN1 world
!!! Unable to parse profile: '/etc/portage/make.profile'
!!! ParseError: Profile contains unsupported EAPI '5':
'/usr/portage/profiles/eapi-5-files/eapi'
!!! Your current profile is invalid. If you have just changed your profile
!!! configuration, you should revert back to the previous configuration.
!!! Allowed actions are limited to --help, --info, --search, --sync, and
We were always running hardened. Never changed the profile.
Hmm.. this is probably /someone's/ bug. Nevertheless, all you have to do
to fix it us update portage to the current stable version, which
supports EAPI5. Can you switch to another profile temporarily and get
portage updated?
I guess this is related to the recent profile upgrade (as of 2013-02-10).
In my
$ eselect news list
I get the last news item related to this upgrade.
As it states,
"Everyone should upgrade as soon as possible (but please make sure
sys-apps/portage is updated to current stable *before* you switch
profile)..... this formally requires a new profile tree with EAPI=5."
So, read the news item, emerge portage, then
# eselect profile
and you're done.
--
Best wishes,
Yuri K. Shatroff
