8 files changed, 161 insertions, 66 deletions
diff --git a/metadata/news/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.ru.txt b/metadata/news/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.ru.txt
deleted file mode 100644
index d52db1143a5a..000000000000
--- a/metadata/news/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.ru.txt
+++ /dev/null
@@ -1,47 +0,0 @@
-Title: Миграция в ~arch с glibc[crypt] на libxcrypt
-Author: Andreas K. Hüttel <dilfridge@gentoo.org>
-Author: Sam James <sam@gentoo.org>
-Translator: Alexey Sokolov <alexey+gentoo@asokolov.org>
-Posted: 2021-06-30
-Revision: 1
-News-Item-Format: 2.0
-
-Реализация библиотеки libcrypt.so в glibc давно устарела и скоро
-будет удалена.
-
-Прочие дистрибутивы годы назад уже переключились на внешнюю
-реализацию под названием libxcrypt. Мы решили последовать их примеру
-и тоже переключиться на libxcrypt. Вначале изменения затронут системы
-на ~arch.
-
-Это будет обычное обновление, и, скорее всего, вам не нужно будет
-предпринимать никаких действий, и проблем возникнуть не должно.
-
-Однако, мы рекомендуем сперва *полностью* обновить систему.
-Это стандартная рекомендация, но в этом конкретном случае
-более простой граф зависимостей поможет portage вычислить
-порядок обновлений.
-
-Так что, чтобы упростить процесс обновления, пожалуйста,
-обновите систему сейчас, до начала самой миграции.
-
-Для пользователей ~arch изменение произойдёт 14 июля 2021,
-пользователи стабильной ветки перейдут на libxcrypt позже.
-
-Если по какой-либо причине вы *не* хотите пока переходить
-на libxcrypt (всего лишь отлагая неизбежное), выполните
-следующие действия:
-* размаскируйте и включите USE-флаг crypt пакета sys-libs/glibc
-* замаскируйте USE-флаг system пакета sys-libs/libxcrypt
-* замаскируйте >=virtual/libcrypt-2
-
-Если вы хотите перейти на libxcrypt уже, точная процедура
-описана в wiki (см. ниже), но суть такая:
-* принудительно выключите USE-флаг crypt пакета sys-libs/glibc
-* размаскируйте USE-флаги system и, если требуется, split-usr
-  пакета sys-libs/libxcrypt
-* размаскируйте ~virtual/libcrypt-2
-
-Дополнительные сведения можно найти здесь:
-* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation
-* https://bugs.gentoo.org/699422
diff --git a/metadata/news/2021-07-17-new-ppc64-profiles/2021-07-17-new-ppc64-profiles.en.txt b/metadata/news/2021-07-17-new-ppc64-profiles/2021-07-17-new-ppc64-profiles.en.txt
new file mode 100644
index 000000000000..63449633166e
--- /dev/null
+++ b/metadata/news/2021-07-17-new-ppc64-profiles/2021-07-17-new-ppc64-profiles.en.txt
@@ -0,0 +1,78 @@
+Title: new ppc64 profiles
+Author: Georgy Yakovlev <gyakovlev@gentoo.org>
+Posted: 2021-07-17
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Profile: default/linux/powerpc/ppc64/17.0/64bit-userland
+Display-If-Profile: default/linux/powerpc/ppc64/17.0/64bit-userland/desktop
+Display-If-Profile: default/linux/powerpc/ppc64/17.0/64bit-userland/desktop/gnome
+Display-If-Profile: default/linux/powerpc/ppc64/17.0/64bit-userland/desktop/gnome/systemd
+Display-If-Profile: default/linux/powerpc/ppc64/17.0/64bit-userland/developer
+
+A new set of ppc64 profiles has been added to the Gentoo
+repository in Jan 2020.  These profiles switch to a more standard
+'no SYMLINK_LIB' multilib layout, and require explicit migration as
+described below.  They are considered stable at the moment, and we would
+like to request all users to upgrade their systems.  The old profiles
+will be deprecated in the near future.
+
+In the new profiles, the lib->lib64 compatibility symlink is removed.
+64-bit libraries need to be installed directly to lib64.  /lib
+and /usr/lib become real directories, that are used for cross-arch
+and native non-library packages (gcc, clang).
+
+The migration is performed using app-portage/unsymlink-lib tool.
+The following steps can be used to upgrade your system:
+
+1. Sync and upgrade your system to the newest package versions
+   to reduce the risk of issues.
+
+2. Install the tool:
+
+     # emerge -1v app-portage/unsymlink-lib
+
+3. Run 'unsymlink-lib --analyze' and check the output for obvious
+   mistakes.  If you need to perform any changes to the system, remember
+   to run 'unsymlink-lib --analyze' again afterwards.
+
+[past this point do not call emerge or modify /usr manually]
+
+4. This is a very good time to make a backup.
+
+5. Run 'unsymlink-lib --migrate'.  You can add '--pretend' first to see
+   what is going to happen.
+
+6. Reboot your system.  Check if important programs work.
+   In particular, verify that e.g. 'emerge --info' works (but do not
+   install anything).  If you hit any serious problems, you can use
+   'unsymlink-lib --rollback' to revert the changes and return to
+   step 4.
+
+7. Run 'unsymlink-lib --finish'.  You can add '--pretend' first to see
+   what is going to happen but note that you're going to see a very long
+   list of files to remove.
+
+8. Switch the profile, e.g.:
+
+     # eselect profile set default/linux/ppc64/17.0
+
+[at this point you can start using emerge again]
+
+9. Rebuild the toolchain:
+
+      # emerge -1v sys-devel/gcc:10
+      [ repeat for other slots you will be using ]
+      # emerge -1v sys-devel/binutils
+      # emerge -1v sys-libs/glibc
+
+For known issues, please see bugs #506276 [2] and #640184[3] .
+If you have any problems with the new profiles or the migration procedure,
+please report a bug and make it block the tracker.
+
+For more information on the layout, please see the wiki article
+on AMD64 multilib layouts [4], it applies to PPC64 as well.
+
+[1] https://gentoo.org/support/news-items/2017-11-30-new-17-profiles.html
+[2] https://bugs.gentoo.org/506276
+[3] https://bugs.gentoo.org/640184
+[4] https://wiki.gentoo.org/wiki/Project:AMD64/Multilib_layout
diff --git a/metadata/news/2021-07-20-perl-5_34-upgrade/2021-07-20-perl-5_34-upgrade.en.txt b/metadata/news/2021-07-20-perl-5_34-upgrade/2021-07-20-perl-5_34-upgrade.en.txt
new file mode 100644
index 000000000000..bc1baa111ece
--- /dev/null
+++ b/metadata/news/2021-07-20-perl-5_34-upgrade/2021-07-20-perl-5_34-upgrade.en.txt
@@ -0,0 +1,46 @@
+Title: Perl 5.34 upgrade now stable
+Author: Sam James <sam@gentoo.org>
+Posted: 2021-07-20
+Revision: 1
+News-Item-Format: 2.0
+
+The Perl project in Gentoo has begun stabilisation of Perl 5.34 [0]
+which is the latest stable version released upstream.
+
+While the package manager usually handles this upgrade cleanly, 
+there are some bugs [1][2][3] which affect Portage's dependency resolution
+that sometimes mean rebuilds occur in the wrong order - this is
+exacerbated by the packaging model used for Perl (but not its fault).
+
+We therefore recommend the following procedure for users:
+1. Sync your tree:
+# emerge --sync
+
+2. Perform a full world upgrade, e.g.:
+# emerge -a -uvDU @world --keep-going=y
+
+3. If any failures occur, please run perl-cleaner --all, then try again:
+# perl-cleaner --all
+
+4. Perform a world upgrade again.
+
+5. Once complete, depclean:
+# emerge -a --depclean
+
+If the upgrade fails with conflicts, please try --backtrack=1000 or some
+other large number.
+
+Rarely, it may be necessary to perform a one-off installation of a package,
+but usually `perl-cleaner` will resolve the issue. If an error message occurs
+after running perl-cleaner, try e.g. for a fictional package dev-perl/foo:
+# emerge -a --oneshot --verbose dev-perl/foo
+
+If you have any issues, please consult the standard support channels [4]
+(such as our forums or IRC channels) and we will do our best to get your
+system working well again.
+
+[0] https://bugs.gentoo.org/802639
+[1] https://bugs.gentoo.org/592880
+[2] https://bugs.gentoo.org/793992
+[3] https://bugs.gentoo.org/199856
+[4] https://www.gentoo.org/support/
diff --git a/metadata/news/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt b/metadata/news/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.en.txt
index 16b5596c9978..824919824ee9 100644
--- a/metadata/news/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt
+++ b/metadata/news/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.en.txt
@@ -1,7 +1,7 @@
 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
+Posted: 2021-07-23
 Revision: 1
 News-Item-Format: 2.0
 
@@ -42,6 +42,24 @@ of steps described on the wiki (see below), but the outline is:
 and enable it
 * unmask ~virtual/libcrypt-2
 
-For more information, please see:
+Please note that if you last changed your password before ~2008,
+it may be using md5crypt or similar other weak mechanisms in /etc/shadow;
+a bug in PAM [0][1] may mean that you were unable to login. We recommend
+using "passwd" to change/refresh your password so it is using modern
+methods. A new version of PAM has been added to the tree to resolve this issue.
+
+In some cases, Portage may schedule a rebuild of certain packages in an
+incorrect order [2]. If building a package fails, please try upgrading
+libcrypt and libxcrypt first:
+
+# emerge -v1 virtual/libcrypt sys-libs/libxcrypt
+
+And then continue the world upgrade with Portage's "--keep-going=y".
+
+For more information or troubleshooting tips, please see:
 * https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation
 * https://bugs.gentoo.org/699422
+
+[0] https://bugs.gentoo.org/802267
+[1] https://bugs.gentoo.org/802807
+[2] https://bugs.gentoo.org/802210
diff --git a/metadata/news/Manifest b/metadata/news/Manifest
index e97dcc6f525c..297d58cf9bf7 100644
--- a/metadata/news/Manifest
+++ b/metadata/news/Manifest
@@ -1,23 +1,23 @@
 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA512
 
-MANIFEST Manifest.files.gz 12937 BLAKE2B b67d6f5f22884e63e4c0f83264d7e6d68fc0526ff33c69a3576e0e5e9c8efccb1907d22d356ee4a397aa70ba9113cb0088e5398317a03fa33db8ae72b561b19e SHA512 5c063a98b2f883695d6c90f6ac28151f0416e3f5c5e1b57359c01ada17f290c7119a2d0d7ca51484bfbc33ddaa124c9524490aa328265bca01129ccefee350c4
-TIMESTAMP 2021-07-17T17:39:10Z
+MANIFEST Manifest.files.gz 13127 BLAKE2B 48dcdc744faac295d7e940945e2b94bc36fdb9280374bfc294be22c17310f4955e8cf9ed86e79377561110355907e899de6dbb881be09a380095cf3f459a4d0c SHA512 1e3e0397f22b3a604da99aad6077f9ef3eab37fc45ead99cd2477203abb00c21ec19cfd941874474dcdfe39c72bb1da6fc88446968c21e2b8cd07dd690e2c3d2
+TIMESTAMP 2021-07-24T00:39:02Z
 -----BEGIN PGP SIGNATURE-----
 
-iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAmDzFb5fFIAAAAAALgAo
+iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAmD7YSZfFIAAAAAALgAo
 aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUx
 RDZBQkI2M0JGQ0ZCNEJBMDJGREYxQ0VDNTkwRUVBQzkxODkyNTAACgkQ7FkO6skY
-klC7ZA//ezSl74d4/ms/vvGMp4ym4VZpKRtl3Kqr9s15yuOuLKuZYQocIThhu0+f
-TuVUqBPkmJrSihBmIBx1WfqR12s5LGeogq79qQZBDK//ZYNI+AtuyshlqKq7+HZU
-Ab3LIBYSsuVPZsh0wjZOK5Kw9N7g9yixAHQHh7A6EXQPzEhFb5XtlROv3YSqnTGN
-NP6fZ6gxqbJrFTezdH5NIcko4ti3xANAAbwFny6kH32y4WIUnhB6osXNsHlZvrMQ
-X5LURrooybuPd8eUkCOuWTo1IQJs/f172nnCog1mKtuxI+A0nxvetmjZ9Q7S6IQL
-kIggHkNYq5jQFxhSPTv2vBDhbP29PkBFi166wniDIKtHbHmrFH3QqQExOad4Kz7+
-8b8zX5+G/ZJG+2GAwFPIkM88ygahQgqv5e1uGErAWpjtjEpzV5EDR8iRQW1YiQgw
-PTNuBBMipwFFeodwQElOho0Zp72SnHidKJnlBo9esrtb/CwPZj5in9rdLl42V6Cc
-fNQgH/90hkH6MxTksHOYK/MwSCpL5DBNKCmayFJPeLgSMOToP7oy6hmgiqVymlDm
-Eh98yb2K+ZHVl2dCZo5jQdbt1LpdGRVFXGp1Jvzx2zVRYg0pL60lXR20MUzl+Und
-orafHtvj5Ces6ZPM9phh6k1M50FqUj/GCIyQrqrGraiUMKn6oAk=
-=atCV
+klCayA/+KUiBWkfrNUKi46VKG4I3enb24cLRmQxGG1k613hdph7uMdjaklTEQcAn
+iI/Ce8zu+T7sAP6ezBpRSoUGwHste/TOlJiVZKxq8SUnhXEQ88vHsAd+IutdgrDO
+Wz2M6DKzSq+KpuTmx40FuPUsq2L2suoZDKpF8K3ikoBKudwJy9XwehqVEOGv4Riz
+EfLEEDtATt61gMmzOJPC/rsGvXyV6aVy7LKup0hpulxHgcf//7j/UpRpcAWNHcWS
+W8DGg7MmYqP6d9YMM5Uqx6GgtjQgG5YGnTVEUts+uD+d7ADw3Ck9EHCK86rAkCe/
+gJPQa8nGupcreNDOC62O77yXb2H2JQA4BRSGbOpIaC89CoOP4q55GQcBGi8zD7mb
+bZpOMieiTJ5JVgyPsrVyUT/TnH4urChesX+8GvVa9cp+Evs/P1Nr+6tcU8AyVidy
+Hkn+LSDh6SNK5pRI5+/b7+sYs9pyLaMKC/CCBhNQ2NfNs8fGjxfQ2LsvEoKNbCsC
+/pYdh37QPQlzEOrkM0TjNxrs/OJiMAUrP4ny8SB73ktUV/wDnhZt4Ck7L7T+CO3B
+trcSTXs1WwNraqT7ZMHFwik79bkNY3DiC+hzbc71HCWkGCCS3UkKtIc81ne2ZDA9
+7RFoF35NgnbNtGkK5xBGmOHNtTGcuf10Ab/6+Y9moh6sgthLMC4=
+=DKbm
 -----END PGP SIGNATURE-----
diff --git a/metadata/news/Manifest.files.gz b/metadata/news/Manifest.files.gz
index 06b2346a272b..f3814ce251db 100644
--- a/metadata/news/Manifest.files.gz
+++ b/metadata/news/Manifest.files.gz
diff --git a/metadata/news/timestamp.chk b/metadata/news/timestamp.chk
index 598a38ee3e84..33f7bb267cb6 100644
--- a/metadata/news/timestamp.chk
+++ b/metadata/news/timestamp.chk
@@ -1 +1 @@
-Sat, 17 Jul 2021 17:39:07 +0000
+Sat, 24 Jul 2021 00:38:58 +0000
diff --git a/metadata/news/timestamp.commit b/metadata/news/timestamp.commit
index 0e28f3af939d..a853494374d0 100644
--- a/metadata/news/timestamp.commit
+++ b/metadata/news/timestamp.commit
@@ -1 +1 @@
-39030e75ff64153246c72edd13c30e5295b8a0ff 1626435584 2021-07-16T11:39:44+00:00
+0d11e58acccb28e8371d53ed53806a8a2d7b16be 1626997272 2021-07-22T23:41:12+00:00