| 1 |
On Fri, Feb 28, 2014 at 09:53:57PM -0500, Rick "Zero_Chaos" Farina wrote: |
| 2 |
> On 12/31/2013 06:43 PM, Andreas K. Huettel wrote: |
| 3 |
> > Am Dienstag, 31. Dezember 2013, 23:30:14 schrieb Mike Gilbert: |
| 4 |
> >> I have noticed that the arch profile directories (profiles/arch/$ARCH) |
| 5 |
> >> are not EAPI 5 capable. These profiles are inherited by both the default |
| 6 |
> >> and hardened profiles and contain arch-specific settings. They are often |
| 7 |
> >> used to override masks set in the base profile. |
| 8 |
|
| 9 |
> To ease this transition, I've drafted a news item based on info from |
| 10 |
> zmedico's blog about when eapi 5 was first supported. |
| 11 |
> |
| 12 |
> This is, in my eyes, the simplest way to transition users who may be on |
| 13 |
> really, really, really outdated systems. It occurred to me I could make |
| 14 |
> a minimal snapshot instead, but it seems much much safer to do this for |
| 15 |
> now. Please review the news article. |
| 16 |
|
| 17 |
I agree, and it's much appreciated. |
| 18 |
Just a couple of minor typos. |
| 19 |
|
| 20 |
> Title: Profile EAPI 5 requirement |
| 21 |
> Author: Zero_Chaos <zerochaos@g.o> |
| 22 |
> Content-Type: text/plain |
| 23 |
> Posted: 2014-03-02 |
| 24 |
> Revision: 1 |
| 25 |
> News-Item-Format: 1.0 |
| 26 |
> Display-If-Installed: <2.2.0_alpha130 |
| 27 |
> |
| 28 |
> In its last session, the Gentoo council decided that the |
| 29 |
|
| 30 |
Capital 'C' for Council, same as Trustees. |
| 31 |
|
| 32 |
> entire profile tree will be updated to require EAPI=5 support. |
| 33 |
> |
| 34 |
> http://www.gentoo.org/proj/en/council/meeting-logs/20140114.txt |
| 35 |
> |
| 36 |
> For all non-deprecated profiles this requirement has already been in |
| 37 |
> place for |
| 38 |
> over one year. If you have updated your system at any point during 2013, and |
| 39 |
> followed the instructions in the profile deprecation warnings (which |
| 40 |
> cannot really easily be overlooked), and are running an up-to-date portage |
| 41 |
> version, there is absolutely nothing that you need to do now. |
| 42 |
> |
| 43 |
> If you are running an installation that has not been updated for more |
| 44 |
> than a |
| 45 |
> year, the portage tree you have just updated to is may be incompatible |
| 46 |
|
| 47 |
s/is // |
| 48 |
|
| 49 |
> with your |
| 50 |
> portage version, and the profile you are using may be gone. |
| 51 |
> |
| 52 |
> It is still possible to upgrade, if you follow these simple steps: |
| 53 |
|
| 54 |
I'd: s/if you follow/following/ (less to read, less conditional) |
| 55 |
but it's not an error of any sort. |
| 56 |
|
| 57 |
> 1.) Do not panic. |
| 58 |
|
| 59 |
Heh I like :) |
| 60 |
|
| 61 |
> 2.) Download a portage snapshot from |
| 62 |
> http://dev.gentoo.org/~zerochaos/snapshots |
| 63 |
> 3.) Unpack the snapshot to /tmp/ |
| 64 |
> 4.) If you are not already, become root |
| 65 |
> 5.) rsync --recursive --links --safe-links --perms --times --force |
| 66 |
> - --whole-file --delete --stats --human-readable --exclude=/distfiles |
| 67 |
> - --exclude=/local --exclude=/packages --verbose --progress |
| 68 |
> - --omit-dir-times /tmp/portage /usr/portage |
| 69 |
> 6.) If needed, set your profile to a modern one (typically named 13.0) |
| 70 |
> 7.) emerge --update --oneshot portage |
| 71 |
> |
| 72 |
> Now that you have a modern copy of portage, you can go back to updating |
| 73 |
> your system as usual. |
| 74 |
> Please update your system at LEAST twice a year to avoid issues like |
| 75 |
> this in the future. |
| 76 |
> Thanks for flying Gentoo. |
| 77 |
|
| 78 |
Now I see why you were asking about default rsync in #-portage :) |
| 79 |
|
| 80 |
Very nice, and thanks for doing this. |
| 81 |
|
| 82 |
Regards, |
| 83 |
igli |
| 84 |
-- |
| 85 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |
Archives