Mailing List Archive

Please note that the 2021-07-07 migration date is preliminary.

Bug: https://bugs.gentoo.org/699422
Signed-off-by: Sam James <sam@gentoo.org>
---
.../2021-06-30-libxcrypt-migration.en.txt | 46 +++++++++++++++++++
1 file changed, 46 insertions(+)
create mode 100644 2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt

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
new file mode 100644
index 0000000..2dd8b1c
--- /dev/null
+++ b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt
@@ -0,0 +1,46 @@
+Title: migrating from glibc[crypt] to libxcrypt in ~arch
+Author: Andreas K. Hüttel <dilfridge@gentoo.org>
+Author: Sam James <sam@gentoo.org>
+Posted: 2021-06-30
+Revision: 1
+News-Item-Format: 2.0
+
+The implementation of libcrypt.so within glibc has been deprecated
+for a long time and will be removed in the near future.
+
+For this reason, we are following other distributions (where
+this has been tested for years already) and switching to the
+external libxcrypt implementation, starting with ~arch
+installations.
+
+This will be a regular update, and in nearly all cases you
+will not have to take any action and not observe any problems.
+
+We do recommend, however, that your system is *fully* up
+to date first. This is a standard recommendation but in this
+specific case, it is useful to have a simplified depgraph
+to ensure that Portage is able to smoothly calculate
+an upgrade path.
+
+That is, please take the opportunity to fully upgrade your
+systems now, before the migration occurs, to simplify matters.
+
+This change will occur on 2021-07-07 for ~arch users. Stable
+users will update at a later date.
+
+If for whatever reason you do *not* wish to switch now -
+which is only delaying the inevitable - you
+need to take the following steps:
+* unmask and enable the crypt USE flag of sys-libs/glibc
+* mask the system USE flag of sys-libs/libxcrypt
+* mask >=virtual/libcrypt-2
+
+If you wish to manually migrate now, there are a series
+of steps described on the wiki (see below), but the outline is:
+* unforce the crypt USE flag of sys-libs/glibc and disable it
+* unmask the system USE flag of sys-libs/libxcrypt and enable it
+* unmask >=virtual/libcrypt-2
+
+For more information, please see:
+* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation
+* https://bugs.gentoo.org/699422
--
2.32.0