| 1 |
On 28.03.2013 21:49, Michael Orlitzky wrote: |
| 2 |
> On 03/28/2013 01:43 PM, Nick Khamis wrote: |
| 3 |
>> First hickup |
| 4 |
>> |
| 5 |
>> emerge -puDN1 world |
| 6 |
>> !!! Unable to parse profile: '/etc/portage/make.profile' |
| 7 |
>> !!! ParseError: Profile contains unsupported EAPI '5': |
| 8 |
>> '/usr/portage/profiles/eapi-5-files/eapi' |
| 9 |
>> !!! Your current profile is invalid. If you have just changed your profile |
| 10 |
>> !!! configuration, you should revert back to the previous configuration. |
| 11 |
>> !!! Allowed actions are limited to --help, --info, --search, --sync, and |
| 12 |
>> |
| 13 |
>> |
| 14 |
>> We were always running hardened. Never changed the profile. |
| 15 |
>> |
| 16 |
> |
| 17 |
> Hmm.. this is probably /someone's/ bug. Nevertheless, all you have to do |
| 18 |
> to fix it us update portage to the current stable version, which |
| 19 |
> supports EAPI5. Can you switch to another profile temporarily and get |
| 20 |
> portage updated? |
| 21 |
|
| 22 |
I guess this is related to the recent profile upgrade (as of 2013-02-10). |
| 23 |
In my |
| 24 |
$ eselect news list |
| 25 |
I get the last news item related to this upgrade. |
| 26 |
As it states, |
| 27 |
"Everyone should upgrade as soon as possible (but please make sure |
| 28 |
sys-apps/portage is updated to current stable *before* you switch |
| 29 |
profile)..... this formally requires a new profile tree with EAPI=5." |
| 30 |
|
| 31 |
So, read the news item, emerge portage, then |
| 32 |
# eselect profile |
| 33 |
and you're done. |
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
Best wishes, |
| 38 |
Yuri K. Shatroff |
Archives