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