| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 12/31/2013 06:43 PM, Andreas K. Huettel wrote: |
| 5 |
> Am Dienstag, 31. Dezember 2013, 23:30:14 schrieb Mike Gilbert: |
| 6 |
>> I have noticed that the arch profile directories (profiles/arch/$ARCH) |
| 7 |
>> are not EAPI 5 capable. These profiles are inherited by both the default |
| 8 |
>> and hardened profiles and contain arch-specific settings. They are often |
| 9 |
>> used to override masks set in the base profile. |
| 10 |
> |
| 11 |
> [...] |
| 12 |
> |
| 13 |
>> Here are a couple of alternatives: |
| 14 |
>> |
| 15 |
>> 1. Add profiles/eapi-5-files/$ARCH. |
| 16 |
>> 2. Add profiles/$ARCH/eapi-5-files. |
| 17 |
> |
| 18 |
> Here's option 3: |
| 19 |
> In a few days the "one year waiting time" after making EAPI5 profiles the |
| 20 |
> default is over, and (pending revisit by the council and agreement) the whole |
| 21 |
> profiles tree can be switched to EAPI5. |
| 22 |
> This means the files from the eapi-5-files directory move to a more central |
| 23 |
> location and the eapi-5-files directory can be removed. |
| 24 |
> With that change the arch dirs automatically also become EAPI5 capable if done |
| 25 |
> properly. |
| 26 |
> |
| 27 |
> See also |
| 28 |
> http://www.gentoo.org/proj/en/council/meeting-logs/20130108-summary.txt |
| 29 |
> |
| 30 |
> Best & a happy new year, |
| 31 |
> Andreas |
| 32 |
> |
| 33 |
|
| 34 |
|
| 35 |
To ease this transition, I've drafted a news item based on info from |
| 36 |
zmedico's blog about when eapi 5 was first supported. |
| 37 |
|
| 38 |
This is, in my eyes, the simplest way to transition users who may be on |
| 39 |
really, really, really outdated systems. It occurred to me I could make |
| 40 |
a minimal snapshot instead, but it seems much much safer to do this for |
| 41 |
now. Please review the news article. |
| 42 |
|
| 43 |
Thanks! |
| 44 |
Zero_Chaos |
| 45 |
|
| 46 |
PS> You can skip review of the body line lengths, I will adjust them to |
| 47 |
spec (72) as needed after the review, any and all current linewrap is |
| 48 |
from my email client. |
| 49 |
|
| 50 |
- ---------------------- |
| 51 |
|
| 52 |
Title: Profile EAPI 5 requirement |
| 53 |
Author: Zero_Chaos <zerochaos@g.o> |
| 54 |
Content-Type: text/plain |
| 55 |
Posted: 2014-03-02 |
| 56 |
Revision: 1 |
| 57 |
News-Item-Format: 1.0 |
| 58 |
Display-If-Installed: <2.2.0_alpha130 |
| 59 |
|
| 60 |
In its last session, the Gentoo council decided that the |
| 61 |
entire profile tree will be updated to require EAPI=5 support. |
| 62 |
|
| 63 |
http://www.gentoo.org/proj/en/council/meeting-logs/20140114.txt |
| 64 |
|
| 65 |
For all non-deprecated profiles this requirement has already been in |
| 66 |
place for |
| 67 |
over one year. If you have updated your system at any point during 2013, and |
| 68 |
followed the instructions in the profile deprecation warnings (which |
| 69 |
cannot really easily be overlooked), and are running an up-to-date portage |
| 70 |
version, there is absolutely nothing that you need to do now. |
| 71 |
|
| 72 |
If you are running an installation that has not been updated for more |
| 73 |
than a |
| 74 |
year, the portage tree you have just updated to is may be incompatible |
| 75 |
with your |
| 76 |
portage version, and the profile you are using may be gone. |
| 77 |
|
| 78 |
It is still possible to upgrade, if you follow these simple steps: |
| 79 |
|
| 80 |
1.) Do not panic. |
| 81 |
2.) Download a portage snapshot from |
| 82 |
http://dev.gentoo.org/~zerochaos/snapshots |
| 83 |
3.) Unpack the snapshot to /tmp/ |
| 84 |
4.) If you are not already, become root |
| 85 |
5.) rsync --recursive --links --safe-links --perms --times --force |
| 86 |
- --whole-file --delete --stats --human-readable --exclude=/distfiles |
| 87 |
- --exclude=/local --exclude=/packages --verbose --progress |
| 88 |
- --omit-dir-times /tmp/portage /usr/portage |
| 89 |
6.) If needed, set your profile to a modern one (typically named 13.0) |
| 90 |
7.) emerge --update --oneshot portage |
| 91 |
|
| 92 |
Now that you have a modern copy of portage, you can go back to updating |
| 93 |
your system as usual. |
| 94 |
Please update your system at LEAST twice a year to avoid issues like |
| 95 |
this in the future. |
| 96 |
Thanks for flying Gentoo. |
| 97 |
|
| 98 |
-----BEGIN PGP SIGNATURE----- |
| 99 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 100 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 101 |
|
| 102 |
iQIcBAEBAgAGBQJTEUvEAAoJEKXdFCfdEflK5lAP/RTivl0QjlB2kyWZbtVIURMR |
| 103 |
X6ELgIkBggrgYvwMqBdz8JG+YFc4Q0gi2xDz9QE+13ysUYCFUmibbasukb2WiVtA |
| 104 |
zNyoNHxoZQEmBuKzDNg3QzkcVsxD+SQ97fq3r2iRYN6tVXbDn5r+i4kCLivDws7y |
| 105 |
Knc3ankf9ShrY3qjJdH3M1xe4kRyX8RBeq2/5kvl43TLu1T3zLJ4bY+RlOX1lOJC |
| 106 |
MB01akcJ45gbJ1bAYrT0nN2Q0HC40tKV4I3uNFcllEkjOkv4vmMSQR2ZrcTo+f5C |
| 107 |
cAaiHTO4zDeHEKmmtI9j/t2ui3GVbelnooFPuH/6IS5NNmkILIo3a3UQsXgugzJX |
| 108 |
7seAaGVzoxgMRUHoA9On5M1FWCFf6Z+JE/PbaJMhZUePVcivgGT8RvmnkSsIexHZ |
| 109 |
4tjVlIjjULFLDz6i229K+RtmsO7b3EV+RXNw6hO8UIjz65QevZ84aNib8ipGJ+Lm |
| 110 |
b7xOCjIS7yNZAtb91PWiE/PoZC0MilAC2xBE6ex/dX1qZPCLpvCPTgQ7hu83GEBX |
| 111 |
h9gqYbMuL/Q+mHG/4PwKppMMmx///Hs/aowLRUGJdN61rxBu6VD69Shnxy3N4OO1 |
| 112 |
pTviiPh0xvv0HSHd61mX/8cdx7GEn39oyd3inwShFvE6cwtn1QqgbS0MZeMqQVX+ |
| 113 |
Ih3725/4uXsyM9NS0q3r |
| 114 |
=prsT |
| 115 |
-----END PGP SIGNATURE----- |
Archives