| 1 |
On 10/02/2013 19:25, Jarry wrote: |
| 2 |
> Hi gentoo-users, |
| 3 |
> |
| 4 |
> today after syncing portage tree I tried to update my system, |
| 5 |
> but I was "greeted" with message: |
| 6 |
> |
| 7 |
> !!! Your current profile is deprecated and not supported anymore. |
| 8 |
> !!! Use eselect profile to update your profile. |
| 9 |
> !!! Please upgrade to the following profile if possible: |
| 10 |
> default/linux/amd64/13.0 |
| 11 |
> |
| 12 |
> So I reverted to previous snapshot just to see what I had before |
| 13 |
> ("eselect profile list" did not show any selected). Till today |
| 14 |
> I had "default/linux/amd64/10.0/server". To my big surprise, |
| 15 |
> there is no "server" profile for "default/linux/amd64/13.0". |
| 16 |
> |
| 17 |
> So is server-profile not suported anymore??? I hope devs had |
| 18 |
> good reason for this, but anyway a change like *this* should |
| 19 |
> definitely be communicated with users in advance... |
| 20 |
> |
| 21 |
> Right now I'm not sure if Gentoo is not supported for server |
| 22 |
> at all or "13.0" is substitution for "10.0/server". But before |
| 23 |
> there were pure "10.0" and "10.0/server" profiles. So it seems |
| 24 |
> to me server profile was simply removed without any substitution. |
| 25 |
|
| 26 |
You'll be getting a news item real soon now [1] |
| 27 |
|
| 28 |
Basically, the 13.0 profiles were written to make use of EAPI=5. You'll |
| 29 |
need to install a recent portage first though, but don;t worry, the most |
| 30 |
recent stable and ~ version both work fine in this regard. |
| 31 |
|
| 32 |
The server profile has gone away as it was little used and didn't do |
| 33 |
very much - it changed little if anything from it's parent profile. So |
| 34 |
just like the news item is going to tell you, eselect profile to a |
| 35 |
somewhat equivalent one (IIRC default/linux/amd64/13.0) and tweak it to |
| 36 |
match what you used to have - this will involve little more than |
| 37 |
eye-balling emerge world's output paying attention to any USE flags that |
| 38 |
changed their default. |
| 39 |
|
| 40 |
|
| 41 |
[1] OK, the news items, or more specifically the lack of timeous news |
| 42 |
items in advance. This is the second occurrence in recent times where |
| 43 |
devs have had to do some back-pedalling, the first was udev with it's |
| 44 |
TMPDEVFS fiasco. I myself am getting a teeny bit pissed off with this |
| 45 |
now. I think a large collection of user should pen a nice polite letter |
| 46 |
to whomever deals with such things asking for more attention to be paid |
| 47 |
to QA matters like this. |
| 48 |
|
| 49 |
|
| 50 |
-- |
| 51 |
Alan McKinnon |
| 52 |
alan.mckinnon@×××××.com |
Archives