1 |
Please note that the 2021-07-07 migration date is preliminary. |
2 |
|
3 |
Bug: https://bugs.gentoo.org/699422 |
4 |
Signed-off-by: Sam James <sam@g.o> |
5 |
--- |
6 |
.../2021-06-30-libxcrypt-migration.en.txt | 46 +++++++++++++++++++ |
7 |
1 file changed, 46 insertions(+) |
8 |
create mode 100644 2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt |
9 |
|
10 |
diff --git a/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt |
11 |
new file mode 100644 |
12 |
index 0000000..2dd8b1c |
13 |
--- /dev/null |
14 |
+++ b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt |
15 |
@@ -0,0 +1,46 @@ |
16 |
+Title: migrating from glibc[crypt] to libxcrypt in ~arch |
17 |
+Author: Andreas K. Hüttel <dilfridge@g.o> |
18 |
+Author: Sam James <sam@g.o> |
19 |
+Posted: 2021-06-30 |
20 |
+Revision: 1 |
21 |
+News-Item-Format: 2.0 |
22 |
+ |
23 |
+The implementation of libcrypt.so within glibc has been deprecated |
24 |
+for a long time and will be removed in the near future. |
25 |
+ |
26 |
+For this reason, we are following other distributions (where |
27 |
+this has been tested for years already) and switching to the |
28 |
+external libxcrypt implementation, starting with ~arch |
29 |
+installations. |
30 |
+ |
31 |
+This will be a regular update, and in nearly all cases you |
32 |
+will not have to take any action and not observe any problems. |
33 |
+ |
34 |
+We do recommend, however, that your system is *fully* up |
35 |
+to date first. This is a standard recommendation but in this |
36 |
+specific case, it is useful to have a simplified depgraph |
37 |
+to ensure that Portage is able to smoothly calculate |
38 |
+an upgrade path. |
39 |
+ |
40 |
+That is, please take the opportunity to fully upgrade your |
41 |
+systems now, before the migration occurs, to simplify matters. |
42 |
+ |
43 |
+This change will occur on 2021-07-07 for ~arch users. Stable |
44 |
+users will update at a later date. |
45 |
+ |
46 |
+If for whatever reason you do *not* wish to switch now - |
47 |
+which is only delaying the inevitable - you |
48 |
+need to take the following steps: |
49 |
+* unmask and enable the crypt USE flag of sys-libs/glibc |
50 |
+* mask the system USE flag of sys-libs/libxcrypt |
51 |
+* mask >=virtual/libcrypt-2 |
52 |
+ |
53 |
+If you wish to manually migrate now, there are a series |
54 |
+of steps described on the wiki (see below), but the outline is: |
55 |
+* unforce the crypt USE flag of sys-libs/glibc and disable it |
56 |
+* unmask the system USE flag of sys-libs/libxcrypt and enable it |
57 |
+* unmask >=virtual/libcrypt-2 |
58 |
+ |
59 |
+For more information, please see: |
60 |
+* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation |
61 |
+* https://bugs.gentoo.org/699422 |
62 |
-- |
63 |
2.32.0 |