| 1 |
But we never changed our profile? Always running hardened server. |
| 2 |
|
| 3 |
N. |
| 4 |
|
| 5 |
On 3/28/13, Nick Khamis <symack@×××××.com> wrote: |
| 6 |
> I switched to the default profile from hardened: |
| 7 |
> |
| 8 |
> eselect profile list |
| 9 |
> Available profile symlink targets: |
| 10 |
> [1] default/linux/x86/13.0 * |
| 11 |
> |
| 12 |
> env-update |
| 13 |
> !!! Unable to parse profile: '/etc/portage/make.profile' |
| 14 |
> !!! ParseError: Profile contains unsupported EAPI '5': |
| 15 |
> '/usr/portage/profiles/default/linux/x86/13.0/eapi' |
| 16 |
>>>> Regenerating /etc/ld.so.cache... |
| 17 |
> |
| 18 |
> And still can't update portage. |
| 19 |
> |
| 20 |
> N. |
| 21 |
> |
| 22 |
> On 3/28/13, Michael Orlitzky <michael@××××××××.com> wrote: |
| 23 |
>> On 03/28/2013 01:43 PM, Nick Khamis wrote: |
| 24 |
>>> First hickup |
| 25 |
>>> |
| 26 |
>>> emerge -puDN1 world |
| 27 |
>>> !!! Unable to parse profile: '/etc/portage/make.profile' |
| 28 |
>>> !!! ParseError: Profile contains unsupported EAPI '5': |
| 29 |
>>> '/usr/portage/profiles/eapi-5-files/eapi' |
| 30 |
>>> !!! Your current profile is invalid. If you have just changed your |
| 31 |
>>> profile |
| 32 |
>>> !!! configuration, you should revert back to the previous configuration. |
| 33 |
>>> !!! Allowed actions are limited to --help, --info, --search, --sync, and |
| 34 |
>>> |
| 35 |
>>> |
| 36 |
>>> We were always running hardened. Never changed the profile. |
| 37 |
>>> |
| 38 |
>> |
| 39 |
>> Hmm.. this is probably /someone's/ bug. Nevertheless, all you have to do |
| 40 |
>> to fix it us update portage to the current stable version, which |
| 41 |
>> supports EAPI5. Can you switch to another profile temporarily and get |
| 42 |
>> portage updated? |
| 43 |
>> |
| 44 |
>> |
| 45 |
>> |
| 46 |
> |
Archives