But we never changed our profile? Always running hardened server. N.
On 3/28/13, Nick Khamis <sym...@gmail.com> wrote: > I switched to the default profile from hardened: > > eselect profile list > Available profile symlink targets: > [1] default/linux/x86/13.0 * > > env-update > !!! Unable to parse profile: '/etc/portage/make.profile' > !!! ParseError: Profile contains unsupported EAPI '5': > '/usr/portage/profiles/default/linux/x86/13.0/eapi' >>>> Regenerating /etc/ld.so.cache... > > And still can't update portage. > > N. > > On 3/28/13, Michael Orlitzky <mich...@orlitzky.com> 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? >> >> >> >
