[gentoo-dev] Enabling EAPI 5 in arch profile directories

[gentoo-dev] Enabling EAPI 5 in arch profile directories

[Mike Gilbert]

I have noticed that the arch profile directories (profiles/arch/$ARCH)
are not EAPI 5 capable. These profiles are inherited by both the default
and hardened profiles and contain arch-specific settings. They are often
used to override masks set in the base profile.

The base profile already has an EAPI 5 equivalent in profiles/eapi-5-files.

I would like to add use.stable.mask to the arch profiles to avoid
duplicating entries in profiles/default/linux/$ARCH/13.0/use.stable.mask
and profiles/hardened/linux/$ARCH/use.stable.mask. This would make
future stabilizations of dev-lang/python easier to coordinate. [1]

Is it acceptable to just bump eapi to 5 in the existing arch profiles?
This would render the default/linux/$ARCH/10.0 profiles unusable in old
version of portage.

Here are a couple of alternatives:

1. Add profiles/eapi-5-files/$ARCH.
2. Add profiles/$ARCH/eapi-5-files.

In either case, the default (13.0) and hardened profiles would be
adjusted to inherit these.

Which option do we prefer? Is there a better option?

[1] https://bugs.gentoo.org/show_bug.cgi?id=474128#c33

Re: [gentoo-dev] Enabling EAPI 5 in arch profile directories

[Andreas K. Huettel]

[-- Attachment #1: Type: Text/Plain, Size: 1156 bytes --]

Am Dienstag, 31. Dezember 2013, 23:30:14 schrieb Mike Gilbert:
> I have noticed that the arch profile directories (profiles/arch/$ARCH)
> are not EAPI 5 capable. These profiles are inherited by both the default
> and hardened profiles and contain arch-specific settings. They are often
> used to override masks set in the base profile.

[...]

> Here are a couple of alternatives:
> 
> 1. Add profiles/eapi-5-files/$ARCH.
> 2. Add profiles/$ARCH/eapi-5-files.

Here's option 3: 
In a few days the "one year waiting time" after making EAPI5 profiles the 
default is over, and (pending revisit by the council and agreement) the whole 
profiles tree can be switched to EAPI5.
This means the files from the eapi-5-files directory move to a more central 
location and the eapi-5-files directory can be removed. 
With that change the arch dirs automatically also become EAPI5 capable if done 
properly.

See also 
http://www.gentoo.org/proj/en/council/meeting-logs/20130108-summary.txt

Best & a happy new year, 
Andreas

-- 
Andreas K. Huettel
Gentoo Linux developer (council, kde)
dilfridge@gentoo.org
http://www.akhuettel.de/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-dev] Enabling EAPI 5 in arch profile directories

[Rick "Zero_Chaos" Farina]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/31/2013 06:43 PM, Andreas K. Huettel wrote:
> Am Dienstag, 31. Dezember 2013, 23:30:14 schrieb Mike Gilbert:
>> I have noticed that the arch profile directories (profiles/arch/$ARCH)
>> are not EAPI 5 capable. These profiles are inherited by both the default
>> and hardened profiles and contain arch-specific settings. They are often
>> used to override masks set in the base profile.
> 
> [...]
> 
>> Here are a couple of alternatives:
>>
>> 1. Add profiles/eapi-5-files/$ARCH.
>> 2. Add profiles/$ARCH/eapi-5-files.
> 
> Here's option 3: 
> In a few days the "one year waiting time" after making EAPI5 profiles the 
> default is over, and (pending revisit by the council and agreement) the whole 
> profiles tree can be switched to EAPI5.
> This means the files from the eapi-5-files directory move to a more central 
> location and the eapi-5-files directory can be removed. 
> With that change the arch dirs automatically also become EAPI5 capable if done 
> properly.
> 
> See also 
> http://www.gentoo.org/proj/en/council/meeting-logs/20130108-summary.txt
> 
> Best & a happy new year, 
> Andreas
> 


To ease this transition, I've drafted a news item based on info from
zmedico's blog about when eapi 5 was first supported.

This is, in my eyes, the simplest way to transition users who may be on
really, really, really outdated systems.  It occurred to me I could make
a minimal snapshot instead, but it seems much much safer to do this for
now.  Please review the news article.

Thanks!
Zero_Chaos

PS> You can skip review of the body line lengths, I will adjust them to
spec (72) as needed after the review, any and all current linewrap is
from my email client.

- ----------------------

Title: Profile EAPI 5 requirement
Author: Zero_Chaos <zerochaos@gentoo.org>
Content-Type: text/plain
Posted: 2014-03-02
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <2.2.0_alpha130

In its last session, the Gentoo council decided that the
entire profile tree will be updated to require EAPI=5 support.

http://www.gentoo.org/proj/en/council/meeting-logs/20140114.txt

For all non-deprecated profiles this requirement has already been in
place for
over one year. If you have updated your system at any point during 2013, and
followed the instructions in the profile deprecation warnings (which
cannot really easily be overlooked), and are running an up-to-date portage
version, there is absolutely nothing that you need to do now.

If you are running an installation that has not been updated for more
than a
year, the portage tree you have just updated to is may be incompatible
with your
portage version, and the profile you are using may be gone.

It is still possible to upgrade, if you follow these simple steps:

1.) Do not panic.
2.) Download a portage snapshot from
http://dev.gentoo.org/~zerochaos/snapshots
3.) Unpack the snapshot to /tmp/
4.) If you are not already, become root
5.) rsync --recursive --links --safe-links --perms --times --force
- --whole-file --delete --stats --human-readable --exclude=/distfiles
- --exclude=/local --exclude=/packages --verbose --progress
- --omit-dir-times /tmp/portage /usr/portage
6.) If needed, set your profile to a modern one (typically named 13.0)
7.) emerge --update --oneshot portage

Now that you have a modern copy of portage, you can go back to updating
your system as usual.
Please update your system at LEAST twice a year to avoid issues like
this in the future.
Thanks for flying Gentoo.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTEUvEAAoJEKXdFCfdEflK5lAP/RTivl0QjlB2kyWZbtVIURMR
X6ELgIkBggrgYvwMqBdz8JG+YFc4Q0gi2xDz9QE+13ysUYCFUmibbasukb2WiVtA
zNyoNHxoZQEmBuKzDNg3QzkcVsxD+SQ97fq3r2iRYN6tVXbDn5r+i4kCLivDws7y
Knc3ankf9ShrY3qjJdH3M1xe4kRyX8RBeq2/5kvl43TLu1T3zLJ4bY+RlOX1lOJC
MB01akcJ45gbJ1bAYrT0nN2Q0HC40tKV4I3uNFcllEkjOkv4vmMSQR2ZrcTo+f5C
cAaiHTO4zDeHEKmmtI9j/t2ui3GVbelnooFPuH/6IS5NNmkILIo3a3UQsXgugzJX
7seAaGVzoxgMRUHoA9On5M1FWCFf6Z+JE/PbaJMhZUePVcivgGT8RvmnkSsIexHZ
4tjVlIjjULFLDz6i229K+RtmsO7b3EV+RXNw6hO8UIjz65QevZ84aNib8ipGJ+Lm
b7xOCjIS7yNZAtb91PWiE/PoZC0MilAC2xBE6ex/dX1qZPCLpvCPTgQ7hu83GEBX
h9gqYbMuL/Q+mHG/4PwKppMMmx///Hs/aowLRUGJdN61rxBu6VD69Shnxy3N4OO1
pTviiPh0xvv0HSHd61mX/8cdx7GEn39oyd3inwShFvE6cwtn1QqgbS0MZeMqQVX+
Ih3725/4uXsyM9NS0q3r
=prsT
-----END PGP SIGNATURE-----

[gentoo-dev] Re: Enabling EAPI 5 in arch profile directories

[Steven J. Long]

On Fri, Feb 28, 2014 at 09:53:57PM -0500, Rick "Zero_Chaos" Farina wrote:
> On 12/31/2013 06:43 PM, Andreas K. Huettel wrote:
> > Am Dienstag, 31. Dezember 2013, 23:30:14 schrieb Mike Gilbert:
> >> I have noticed that the arch profile directories (profiles/arch/$ARCH)
> >> are not EAPI 5 capable. These profiles are inherited by both the default
> >> and hardened profiles and contain arch-specific settings. They are often
> >> used to override masks set in the base profile.
 
> To ease this transition, I've drafted a news item based on info from
> zmedico's blog about when eapi 5 was first supported.
> 
> This is, in my eyes, the simplest way to transition users who may be on
> really, really, really outdated systems.  It occurred to me I could make
> a minimal snapshot instead, but it seems much much safer to do this for
> now.  Please review the news article.

I agree, and it's much appreciated.
Just a couple of minor typos.

> Title: Profile EAPI 5 requirement
> Author: Zero_Chaos <zerochaos@gentoo.org>
> Content-Type: text/plain
> Posted: 2014-03-02
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Installed: <2.2.0_alpha130
> 
> In its last session, the Gentoo council decided that the

Capital 'C' for Council, same as Trustees.

> entire profile tree will be updated to require EAPI=5 support.
> 
> http://www.gentoo.org/proj/en/council/meeting-logs/20140114.txt
> 
> For all non-deprecated profiles this requirement has already been in
> place for
> over one year. If you have updated your system at any point during 2013, and
> followed the instructions in the profile deprecation warnings (which
> cannot really easily be overlooked), and are running an up-to-date portage
> version, there is absolutely nothing that you need to do now.
> 
> If you are running an installation that has not been updated for more
> than a
> year, the portage tree you have just updated to is may be incompatible

s/is //

> with your
> portage version, and the profile you are using may be gone.
> 
> It is still possible to upgrade, if you follow these simple steps:

I'd: s/if you follow/following/ (less to read, less conditional)
but it's not an error of any sort.

> 1.) Do not panic.

Heh I like :)

> 2.) Download a portage snapshot from
> http://dev.gentoo.org/~zerochaos/snapshots
> 3.) Unpack the snapshot to /tmp/
> 4.) If you are not already, become root
> 5.) rsync --recursive --links --safe-links --perms --times --force
> - --whole-file --delete --stats --human-readable --exclude=/distfiles
> - --exclude=/local --exclude=/packages --verbose --progress
> - --omit-dir-times /tmp/portage /usr/portage
> 6.) If needed, set your profile to a modern one (typically named 13.0)
> 7.) emerge --update --oneshot portage
> 
> Now that you have a modern copy of portage, you can go back to updating
> your system as usual.
> Please update your system at LEAST twice a year to avoid issues like
> this in the future.
> Thanks for flying Gentoo.

Now I see why you were asking about default rsync in #-portage :)

Very nice, and thanks for doing this.

Regards,
igli
-- 
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-)

Re: [gentoo-dev] Re: Enabling EAPI 5 in arch profile directories

[Alec Warner]

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

On Fri, Mar 7, 2014 at 5:57 PM, Steven J. Long
<slong@rathaus.eclipse.co.uk>wrote:

> On Fri, Feb 28, 2014 at 09:53:57PM -0500, Rick "Zero_Chaos" Farina wrote:
> > On 12/31/2013 06:43 PM, Andreas K. Huettel wrote:
> > > Am Dienstag, 31. Dezember 2013, 23:30:14 schrieb Mike Gilbert:
> > >> I have noticed that the arch profile directories (profiles/arch/$ARCH)
> > >> are not EAPI 5 capable. These profiles are inherited by both the
> default
> > >> and hardened profiles and contain arch-specific settings. They are
> often
> > >> used to override masks set in the base profile.
>
> > To ease this transition, I've drafted a news item based on info from
> > zmedico's blog about when eapi 5 was first supported.
> >
> > This is, in my eyes, the simplest way to transition users who may be on
> > really, really, really outdated systems.  It occurred to me I could make
> > a minimal snapshot instead, but it seems much much safer to do this for
> > now.  Please review the news article.
>
> I agree, and it's much appreciated.
> Just a couple of minor typos.
>
> > Title: Profile EAPI 5 requirement
> > Author: Zero_Chaos <zerochaos@gentoo.org>
> > Content-Type: text/plain
> > Posted: 2014-03-02
> > Revision: 1
> > News-Item-Format: 1.0
> > Display-If-Installed: <2.2.0_alpha130
> >
> > In its last session, the Gentoo council decided that the
>
> Capital 'C' for Council, same as Trustees.
>
> > entire profile tree will be updated to require EAPI=5 support.
> >
> > http://www.gentoo.org/proj/en/council/meeting-logs/20140114.txt
> >
> > For all non-deprecated profiles this requirement has already been in
> > place for
> > over one year. If you have updated your system at any point during 2013,
> and
> > followed the instructions in the profile deprecation warnings (which
> > cannot really easily be overlooked), and are running an up-to-date
> portage
> > version, there is absolutely nothing that you need to do now.
> >
> > If you are running an installation that has not been updated for more
> > than a
> > year, the portage tree you have just updated to is may be incompatible
>
> s/is //
>
> > with your
> > portage version, and the profile you are using may be gone.
> >
> > It is still possible to upgrade, if you follow these simple steps:
>
> I'd: s/if you follow/following/ (less to read, less conditional)
> but it's not an error of any sort.
>
> > 1.) Do not panic.
>
> Heh I like :)
>
> > 2.) Download a portage snapshot from
> > http://dev.gentoo.org/~zerochaos/snapshots
> > 3.) Unpack the snapshot to /tmp/
>

I'd honestly just write this in a script and give it to the users. There
are problems with it like:

When to use root.
Unpacking stuff in /tmp is difficult to do safely due to rampant symlink
attacks.
The URL to download may change.
Finding the correct portdir (might not be /usr/portage.)

-A


> > 4.) If you are not already, become root
> > 5.) rsync --recursive --links --safe-links --perms --times --force
> > - --whole-file --delete --stats --human-readable --exclude=/distfiles
> > - --exclude=/local --exclude=/packages --verbose --progress
> > - --omit-dir-times /tmp/portage /usr/portage
> > 6.) If needed, set your profile to a modern one (typically named 13.0)
> > 7.) emerge --update --oneshot portage
>
>
> > Now that you have a modern copy of portage, you can go back to updating
> > your system as usual.
> > Please update your system at LEAST twice a year to avoid issues like
> > this in the future.
> > Thanks for flying Gentoo.
>
> Now I see why you were asking about default rsync in #-portage :)
>
> Very nice, and thanks for doing this.
>
> Regards,
> igli
> --
> #friendly-coders -- We're friendly, but we're not /that/ friendly ;-)
>
>

[-- Attachment #2: Type: text/html, Size: 5293 bytes --]