1 |
>>>>> On Sun, 24 Feb 2019, Aaron Bauman wrote: |
2 |
|
3 |
> Following up on Michał's work with the amd64 17.1 profiles, I have |
4 |
> revised the original news item for review with the intent of moving the |
5 |
> profiles to stable. |
6 |
|
7 |
> These profiles were initially published by Michał in December 2017 as |
8 |
> exp and were moved to dev status in December 2018. As such, these profiles |
9 |
> will now be marked stable following the news item review. |
10 |
|
11 |
"Changes that require a re-read of the news item (i.e., most changes |
12 |
that are not spelling or formatting related) should instead use a new |
13 |
news item." (GLEP 42) |
14 |
|
15 |
> === |
16 |
|
17 |
> Title: amd64 17.1 Profiles |
18 |
> Author: Michał Górny <mgorny@g.o> |
19 |
> Posted: 2019-12-23 |
20 |
> Revision: 4 |
21 |
> News-Item-Format: 2.0 |
22 |
> Display-If-Profile: default/linux/amd64/13.0 |
23 |
> Display-If-Profile: default/linux/amd64/13.0/selinux |
24 |
> Display-If-Profile: default/linux/amd64/13.0/desktop |
25 |
> Display-If-Profile: default/linux/amd64/13.0/desktop/gnome |
26 |
> Display-If-Profile: default/linux/amd64/13.0/desktop/gnome/systemd |
27 |
> Display-If-Profile: default/linux/amd64/13.0/desktop/plasma |
28 |
> Display-If-Profile: default/linux/amd64/13.0/desktop/plasma/systemd |
29 |
> Display-If-Profile: default/linux/amd64/13.0/developer |
30 |
> Display-If-Profile: default/linux/amd64/13.0/no-multilib |
31 |
> Display-If-Profile: default/linux/amd64/13.0/systemd |
32 |
> Display-If-Profile: default/linux/amd64/17.0 |
33 |
> Display-If-Profile: default/linux/amd64/17.0/selinux |
34 |
> Display-If-Profile: default/linux/amd64/17.0/hardened |
35 |
> Display-If-Profile: default/linux/amd64/17.0/hardened/selinux |
36 |
> Display-If-Profile: default/linux/amd64/17.0/desktop |
37 |
> Display-If-Profile: default/linux/amd64/17.0/desktop/gnome |
38 |
> Display-If-Profile: default/linux/amd64/17.0/desktop/gnome/systemd |
39 |
> Display-If-Profile: default/linux/amd64/17.0/desktop/plasma |
40 |
> Display-If-Profile: default/linux/amd64/17.0/desktop/plasma/systemd |
41 |
> Display-If-Profile: default/linux/amd64/17.0/developer |
42 |
> Display-If-Profile: default/linux/amd64/17.0/no-multilib |
43 |
> Display-If-Profile: default/linux/amd64/17.0/no-multilib/hardened |
44 |
> Display-If-Profile: default/linux/amd64/17.0/no-multilib/hardened/selinux |
45 |
> Display-If-Profile: default/linux/amd64/17.0/systemd |
46 |
|
47 |
> The 17.1 amd64 profiles have been in the Gentoo repository for several months |
48 |
> and have been tested in exp and dev profile statuses. These profiles switch to |
49 |
> a more standard 'no SYMLINK_LIB' multilib layout, and require explicit migration |
50 |
> as described below. They are now considered stable. |
51 |
|
52 |
Flip the order of the 2nd and 3rd sentence? You're talking about |
53 |
stability, then explain the profiles, then stability again. |
54 |
|
55 |
Also, please keep line wrapping consistent with the rest of the text, |
56 |
i.e. at 72 characters. |
57 |
|
58 |
> In these profiles, the lib->lib64 compatibility symlink is removed. |
59 |
> The 'lib' directory becomes a separate directory, that is used |
60 |
> for cross-arch and native non-library packages (gcc, clang) and 32-bit |
61 |
> libraries on the multilib profile (for better compatibility with |
62 |
> prebuilt x86 packages). |
63 |
|
64 |
> Migration from both 13.0 and 17.0 profiles are supported. In case |
65 |
|
66 |
s/are/is/ (Subject is "migration" and it's singular.) |
67 |
|
68 |
> of the former, please read the news item for 17.0 upgrade first |
69 |
> and enable gcc 6.4.0 or newer first as explained there. |
70 |
|
71 |
> The migration is performed using app-portage/unsymlink-lib tool. |
72 |
> The following steps can be used to upgrade your system: |
73 |
|
74 |
> 1. Sync and upgrade your system to the newest package versions |
75 |
> to reduce the risk of issues. |
76 |
|
77 |
> 2. Install the tool, e.g. via 'emerge -1v app-portage/unsymlink-lib' |
78 |
|
79 |
> 3. Run 'unsymlink-lib --analyze' and check the output for obvious |
80 |
> mistakes. If you need to perform any changes to the system, remember |
81 |
> to run 'unsymlink-lib --analyze' again afterwards. |
82 |
|
83 |
> [past this point do not call emerge or modify /usr manually] |
84 |
|
85 |
> 4. This is a very good time to make a backup. |
86 |
|
87 |
> 5. Run 'unsymlink-lib --migrate'. You can add '--pretend' first to see |
88 |
> what is going to happen. |
89 |
|
90 |
> 6. Reboot your system and see if it still boots. Check if important |
91 |
> programs work. In particular, check if e.g. 'emerge --info' works |
92 |
> (but do not install anything). If you hit any serious problems, |
93 |
> you can use 'unsymlink-lib --rollback' to revert the changes |
94 |
> and return to step 3. |
95 |
|
96 |
> 7. Run 'unsymlink-lib --finish'. You can add '--pretend' first to see |
97 |
> what is going to happen but note that you're going to see a very long |
98 |
> list of files to remove. |
99 |
|
100 |
> 8. Switch the profile, e.g.: |
101 |
|
102 |
> eselect profile set --force default/linux/amd64/17.1/desktop |
103 |
|
104 |
> [at this point you can start using emerge again] |
105 |
|
106 |
> 9. Rebuild sys-devel/gcc. If you are switching from 13.0 profiles, |
107 |
> rebuild sys-devel/binutils and sys-libs/glibc afterwards. |
108 |
|
109 |
> 10. If you are using a multilib profile, rebuild all 32-bit packages. |
110 |
> This can be done using: |
111 |
|
112 |
> emerge -1v /lib32 /usr/lib32 |
113 |
|
114 |
> Alternatively, if you are switching from one of the 13.0 profiles |
115 |
> you can rebuild all packages as detailed in the 17.0 news item. |
116 |
|
117 |
> 11. Once the last 32-bit package is rebuilt, your package manager |
118 |
> should remove the orphaned /lib32 and /usr/lib32 symlinks. If that |
119 |
> does not happen, remove them manually. |
120 |
|
121 |
> For known issues, please see bug #506276 [1]. If you have any problems |
122 |
> with the new profiles or the migration procedure, please report a bug |
123 |
> and make it block the tracker. |
124 |
|
125 |
> For more information on the layout, please see the wiki article |
126 |
> on AMD64 multilib layouts [2]. |
127 |
|
128 |
> [1]:https://bugs.gentoo.org/506276 |
129 |
> [2]:https://wiki.gentoo.org/wiki/Project:AMD64/Multilib_layout |