From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 15D36138010 for ; Thu, 28 Mar 2013 18:03:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 686FAE0928; Thu, 28 Mar 2013 18:03:23 +0000 (UTC) Received: from mail-la0-f42.google.com (mail-la0-f42.google.com [209.85.215.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C4F2EE07E1 for ; Thu, 28 Mar 2013 18:03:21 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id fe20so18332689lab.15 for ; Thu, 28 Mar 2013 11:03:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=PLyEPbRiv5oOQUToQc5bMhoLYBKXAe6q65tBSgQVmc0=; b=Bx5j4bUtPMbWLRFi7s+/Gh8epB2jFlBIu/FlAsUT1Hp+Zl/F4b9Dyp0J6tDTEyr8PS mRAQNWqbgi0kbqLa7gWzykExL6HlD4TF7wIUNtFY7XNE7nrQUi1YOR8RBPx+xGF6o+cU 4m4TWOlXeyj9ERkD6sT/AYmC/0zdBl9kTkFlaBx6JySaVlYyg8VvvaCCLAk0bL3yXnql aLqO/NRrLrv4zX9Cbh5Qo6DQK8JdKdAIUjGtR/HHUAlZAjm7rw/fmUue4Yuij82ZIJ+B ZKDKRZxgrs83zwxd9lK1WVuCqE5xsJwsBURiZF5mKBmYChAGt7qqfnLsgIA5AbzFFFPE k3qQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.112.30.104 with SMTP id r8mr33909lbh.82.1364493799787; Thu, 28 Mar 2013 11:03:19 -0700 (PDT) Received: by 10.114.58.43 with HTTP; Thu, 28 Mar 2013 11:03:19 -0700 (PDT) In-Reply-To: References: <5154744D.9080805@orlitzky.com> <5154792B.5020507@orlitzky.com> <51547EE8.8060802@orlitzky.com> <515482A2.1010708@orlitzky.com> Date: Thu, 28 Mar 2013 14:03:19 -0400 Message-ID: Subject: Re: [gentoo-user] Updating our live servers. I'm scared! From: Nick Khamis To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 9b24033b-2655-4be1-9030-0a98b25ae92c X-Archives-Hash: c32470298230af176fdcfa7a778ac426 But we never changed our profile? Always running hardened server. N. On 3/28/13, Nick Khamis 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 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? >> >> >> >