Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [RFC] amd64 17.1 profiles stable
Date: Sun, 24 Feb 2019 09:00:24
Message-Id: 1550998802.734.4.camel@gentoo.org
In Reply to: [gentoo-dev] [RFC] amd64 17.1 profiles stable by Aaron Bauman
1 On Sat, 2019-02-23 at 19:44 -0500, Aaron Bauman wrote:
2 > Title: amd64 17.1 Profiles
3 > Author: Michał Górny <mgorny@g.o>
4
5 Please put yourself here, as you're taking over.
6
7 > Posted: 2019-12-23
8
9 Cool date, bro.
10
11 > Revision: 4
12
13 To be honest, I'm not sure if updating the old news item is a good
14 solution. People who have read it already (and dismissed as irrelevant
15 at the time) would not see it again, would they? So maybe adding it
16 as a new news item (and possibly removing the old one) would be a better
17 course of action.
18
19 > News-Item-Format: 2.0
20 > Display-If-Profile: default/linux/amd64/13.0
21 > Display-If-Profile: default/linux/amd64/13.0/selinux
22 > Display-If-Profile: default/linux/amd64/13.0/desktop
23 > Display-If-Profile: default/linux/amd64/13.0/desktop/gnome
24 > Display-If-Profile: default/linux/amd64/13.0/desktop/gnome/systemd
25 > Display-If-Profile: default/linux/amd64/13.0/desktop/plasma
26 > Display-If-Profile: default/linux/amd64/13.0/desktop/plasma/systemd
27 > Display-If-Profile: default/linux/amd64/13.0/developer
28 > Display-If-Profile: default/linux/amd64/13.0/no-multilib
29 > Display-If-Profile: default/linux/amd64/13.0/systemd
30 > Display-If-Profile: default/linux/amd64/17.0
31 > Display-If-Profile: default/linux/amd64/17.0/selinux
32 > Display-If-Profile: default/linux/amd64/17.0/hardened
33 > Display-If-Profile: default/linux/amd64/17.0/hardened/selinux
34 > Display-If-Profile: default/linux/amd64/17.0/desktop
35 > Display-If-Profile: default/linux/amd64/17.0/desktop/gnome
36 > Display-If-Profile: default/linux/amd64/17.0/desktop/gnome/systemd
37 > Display-If-Profile: default/linux/amd64/17.0/desktop/plasma
38 > Display-If-Profile: default/linux/amd64/17.0/desktop/plasma/systemd
39 > Display-If-Profile: default/linux/amd64/17.0/developer
40 > Display-If-Profile: default/linux/amd64/17.0/no-multilib
41 > Display-If-Profile: default/linux/amd64/17.0/no-multilib/hardened
42 > Display-If-Profile: default/linux/amd64/17.0/no-multilib/hardened/selinux
43 > Display-If-Profile: default/linux/amd64/17.0/systemd
44 >
45 > The 17.1 amd64 profiles have been in the Gentoo repository for several months
46 > and have been tested in exp and dev profile statuses. These profiles switch to
47 > a more standard 'no SYMLINK_LIB' multilib layout, and require explicit migration
48 > as described below. They are now considered stable.
49
50 The text below has been wrapped at 72 chars. Please use a consistent
51 wrapping for the whole news item (whichever you choose).
52
53 Probably worthwhile to put emphasis that old profiles are going to be
54 deprecated and users actually should start migrating.
55
56 > In these profiles, the lib->lib64 compatibility symlink is removed.
57 > The 'lib' directory becomes a separate directory, that is used
58 > for cross-arch and native non-library packages (gcc, clang) and 32-bit
59 > libraries on the multilib profile (for better compatibility with
60 > prebuilt x86 packages).
61 >
62 > Migration from both 13.0 and 17.0 profiles are supported. In case
63 > of the former, please read the news item for 17.0 upgrade first
64 > and enable gcc 6.4.0 or newer first as explained there.
65 >
66 > The migration is performed using app-portage/unsymlink-lib tool.
67 > The following steps can be used to upgrade your system:
68 >
69 > 1. Sync and upgrade your system to the newest package versions
70 > to reduce the risk of issues.
71 >
72 > 2. Install the tool, e.g. via 'emerge -1v app-portage/unsymlink-lib'
73 >
74 > 3. Run 'unsymlink-lib --analyze' and check the output for obvious
75 > mistakes. If you need to perform any changes to the system, remember
76 > to run 'unsymlink-lib --analyze' again afterwards.
77 >
78 > [past this point do not call emerge or modify /usr manually]
79 >
80 > 4. This is a very good time to make a backup.
81 >
82 > 5. Run 'unsymlink-lib --migrate'. You can add '--pretend' first to see
83 > what is going to happen.
84 >
85 > 6. Reboot your system and see if it still boots. Check if important
86 > programs work. In particular, check if e.g. 'emerge --info' works
87 > (but do not install anything). If you hit any serious problems,
88 > you can use 'unsymlink-lib --rollback' to revert the changes
89 > and return to step 3.
90 >
91 > 7. Run 'unsymlink-lib --finish'. You can add '--pretend' first to see
92 > what is going to happen but note that you're going to see a very long
93 > list of files to remove.
94 >
95 > 8. Switch the profile, e.g.:
96 >
97 > eselect profile set --force default/linux/amd64/17.1/desktop
98 >
99 > [at this point you can start using emerge again]
100 >
101 > 9. Rebuild sys-devel/gcc. If you are switching from 13.0 profiles,
102 > rebuild sys-devel/binutils and sys-libs/glibc afterwards.
103 >
104 > 10. If you are using a multilib profile, rebuild all 32-bit packages.
105 > This can be done using:
106 >
107 > emerge -1v /lib32 /usr/lib32
108 >
109 > Alternatively, if you are switching from one of the 13.0 profiles
110 > you can rebuild all packages as detailed in the 17.0 news item.
111 >
112 > 11. Once the last 32-bit package is rebuilt, your package manager
113 > should remove the orphaned /lib32 and /usr/lib32 symlinks. If that
114 > does not happen, remove them manually.
115 >
116 > For known issues, please see bug #506276 [1]. If you have any problems
117 > with the new profiles or the migration procedure, please report a bug
118 > and make it block the tracker.
119 >
120 > For more information on the layout, please see the wiki article
121 > on AMD64 multilib layouts [2].
122 >
123 > [1]:https://bugs.gentoo.org/506276
124 > [2]:https://wiki.gentoo.org/wiki/Project:AMD64/Multilib_layout
125
126 --
127 Best regards,
128 Michał Górny

Attachments

File name MIME type
signature.asc application/pgp-signature