| 1 |
On 03/28/2013 01:43 PM, Nick Khamis wrote: |
| 2 |
> First hickup |
| 3 |
> |
| 4 |
> emerge -puDN1 world |
| 5 |
> !!! Unable to parse profile: '/etc/portage/make.profile' |
| 6 |
> !!! ParseError: Profile contains unsupported EAPI '5': |
| 7 |
> '/usr/portage/profiles/eapi-5-files/eapi' |
| 8 |
> !!! Your current profile is invalid. If you have just changed your profile |
| 9 |
> !!! configuration, you should revert back to the previous configuration. |
| 10 |
> !!! Allowed actions are limited to --help, --info, --search, --sync, and |
| 11 |
> |
| 12 |
> |
| 13 |
> We were always running hardened. Never changed the profile. |
| 14 |
> |
| 15 |
|
| 16 |
Hmm.. this is probably /someone's/ bug. Nevertheless, all you have to do |
| 17 |
to fix it us update portage to the current stable version, which |
| 18 |
supports EAPI5. Can you switch to another profile temporarily and get |
| 19 |
portage updated? |
Archives