Re: [gentoo-user] No server profile anymore???

[Marc Joliet]

Am Sun, 10 Feb 2013 18:25:39 +0100
schrieb Jarry <mr.jarry@×××××.com>:

> Hi gentoo-users,
>
> today after syncing portage tree I tried to update my system,
> but I was "greeted" with message:
>
> !!! Your current profile is deprecated and not supported anymore.
> !!! Use eselect profile to update your profile.
> !!! Please upgrade to the following profile if possible:
>        default/linux/amd64/13.0
>
> So I reverted to previous snapshot just to see what I had before
> ("eselect profile list" did not show any selected). Till today
> I had "default/linux/amd64/10.0/server". To my big surprise,
> there is no "server" profile for "default/linux/amd64/13.0".
>
> So is server-profile not suported anymore??? I hope devs had
> good reason for this, but anyway a change like *this* should
> definitely be communicated with users in advance...
>
> Right now I'm not sure if Gentoo is not supported for server
> at all or "13.0" is substitution for "10.0/server". But before
> there were pure "10.0" and "10.0/server" profiles. So it seems
> to me server profile was simply removed without any substitution.
>
> Jarry

I know it's not the same as a news entry, but it was announced on Planet Gentoo:

http://dilfridge.blogspot.nl/2013/02/gentoo-100-to-130-profiles-upgrade.html

The differences to the parent profile were apparently very minimal. From the
post:

> If you have used a server profile so far, you should migrate to its parent,
> i.e. from "default/linux/amd64/10.0/server" to "default/linux/amd64/13.0". This
> may change the default value of some use-flags (the setting in "server" was
> USE="-perl -python snmp truetype xml"), so you may want to check the setting of
> these flags after switching profile, but otherwise nothing happens.

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup