| 1 |
On 02/10/2013 03:45 PM, Andreas K. Huettel wrote: |
| 2 |
> Am Montag, 11. Februar 2013, 00:34:19 schrieb Michał Górny: |
| 3 |
> |
| 4 |
>>> |
| 5 |
>>> actually *do* to one's system? |
| 6 |
>> |
| 7 |
>> Out of curiosity, does portage suggest switching to the new profiles |
| 8 |
>> even if it doesn't support its EAPI? |
| 9 |
> |
| 10 |
> Unfortunately, it seems yes. (Feature request?) |
| 11 |
|
| 12 |
It's possible to include additional instructions in the deprecated file. |
| 13 |
All lines after the first one as upgrade instructions. |
| 14 |
|
| 15 |
For future portage versions, I've fixed it to behavior better: |
| 16 |
|
| 17 |
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=34d8c817080f34f1a0b44cf05b99beacfc0d6314 |
| 18 |
|
| 19 |
This fix updates the profile deprecation warning to look like this: |
| 20 |
|
| 21 |
!!! Your current profile is deprecated and not supported anymore. |
| 22 |
!!! Use eselect profile to update your profile. |
| 23 |
!!! Please upgrade to the following profile if possible: |
| 24 |
default/linux/x86/13.0/desktop |
| 25 |
|
| 26 |
!!! Unable to parse profile: |
| 27 |
'/usr/portage/profiles/default/linux/x86/13.0/desktop' |
| 28 |
!!! ParseError: Profile contains unsupported EAPI '5': |
| 29 |
'/usr/portage/profiles/eapi-5-files/eapi' |
| 30 |
|
| 31 |
* You must update portage before you can migrate to the above profile. |
| 32 |
* In order to update portage, run 'emerge --oneshot portage'. |
| 33 |
-- |
| 34 |
Thanks, |
| 35 |
Zac |
Archives