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

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

[Jarry]

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

-- 
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.

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

[Dale]

Jarry wrote:
> 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
>


From my understanding of the devs on -dev, the base profile is the
server profile now.  So select a base profile and carry on. 

[10]  default/linux/amd64/13.0

That one should work. 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

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

[Marc Joliet]

[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]

Am Sun, 10 Feb 2013 18:25:39 +0100
schrieb Jarry <mr.jarry@gmail.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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Nuno Silva]

On 2013-02-10, Jarry wrote:

> 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.

No, the only reason the server profile existed was to have the name
"server" on it. Debate on the -dev list quickly led to the conclusion
that there was no point in keeping a separate "server" profile (we
already have the base profiles which are quite minimalistic, so they
*are* what the server profile should be, anyway).

In fact, if you are going to ask "they why did we have two different
profiles", well, that's how the discussion got to the point where the
decision was to ditch the /server profile.

From what I remember, differences were only a *couple* USE flags. So
just sitch to the base profile. 

Now this could have used a news item, yes.

-- 
Nuno Silva (aka njsg)
http://njsg.sdf-eu.org/

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

[Alan McKinnon]

On 10/02/2013 19:25, Jarry wrote:
> 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.

You'll be getting a news item real soon now [1]

Basically, the 13.0 profiles were written to make use of EAPI=5. You'll
need to install a recent portage first though, but don;t worry, the most
recent stable and ~ version both work fine in this regard.

The server profile has gone away as it was little used and didn't do
very much - it changed little if anything from it's parent profile. So
just like the news item is going to tell you, eselect profile to a
somewhat equivalent one (IIRC default/linux/amd64/13.0) and tweak it to
match what you used to have - this will involve little more than
eye-balling emerge world's output paying attention to any USE flags that
changed their default.


[1] OK, the news items, or more specifically the lack of timeous news
items in advance. This is the second occurrence in recent times where
devs have had to do some back-pedalling, the first was udev with it's
TMPDEVFS fiasco. I myself am getting a teeny bit pissed off with this
now. I think a large collection of user should pen a nice polite letter
to whomever deals with such things asking for more attention to be paid
to QA matters like this.


-- 
Alan McKinnon
alan.mckinnon@gmail.com

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

[Nuno Silva]

On 2013-02-10, Alan McKinnon wrote:

> On 10/02/2013 19:25, Jarry wrote:
>
>> !!! 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 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...
[...]
> [1] OK, the news items, or more specifically the lack of timeous news
> items in advance. This is the second occurrence in recent times where
> devs have had to do some back-pedalling, the first was udev with it's
> TMPDEVFS fiasco. I myself am getting a teeny bit pissed off with this
> now. I think a large collection of user should pen a nice polite letter
> to whomever deals with such things asking for more attention to be paid
> to QA matters like this.

+1

I have no doubts that devs have lots of work to do, but it's a rather
serious situation if the difference between unstable and stable land is
*not* used as an advantage when it comes to deal with situations like
this and udev's kernel requirements and network rules.

I guess a good rule of thumb would be: if a stabilization/profile change
or introduced error message will require users to change their settings
by hand, change their kernel config to match new requirements in order
to have an usable system or to treat some packages/flags in a different
way, this should not go forward until a news item has been prepared to
notify users about it.

-- 
Nuno Silva (aka njsg)
http://njsg.sdf-eu.org/

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

[Tanstaafl]

On 2013-02-12 6:30 PM,  (Nuno Silva) <<nunojsilva@ist.utl.pt (Nuno 
Silva)> wrote:
> I have no doubts that devs have lots of work to do, but it's a rather
> serious situation if the difference between unstable and stable land is
> *not* used as an advantage when it comes to deal with situations like
> this and udev's kernel requirements and network rules.
>
> I guess a good rule of thumb would be: if a stabilization/profile change
> or introduced error message will require users to change their settings
> by hand, change their kernel config to match new requirements in order
> to have an usable system or to treat some packages/flags in a different
> way, this should not go forward until a news item has been prepared to
> notify users about it.

Add "with an appropriate bake-in time *after* the news item is released 
to provide time for stable users to digest and understand the 
implications, and for unstable users to thrash out any issues before 
pushing it s-to stable." before the period at the end of that last 
sentence and I agree wholeheartedly.

Question:

Is there a well defined 'bake-in' time for things like this?

If not, there should be.