summaryrefslogtreecommitdiff
path: root/metadata/news
diff options
context:
space:
mode:
authorV3n3RiX <venerix@koprulu.sector>2021-12-05 02:47:11 +0000
committerV3n3RiX <venerix@koprulu.sector>2021-12-05 02:47:11 +0000
commit2771f79232c273bc2a57d23bf335dd81ccf6af28 (patch)
treec8af0fd04194aed03cf067d44e53c7edd3e9ab84 /metadata/news
parente9d044d4b9b71200a96adfa280848858c0f468c9 (diff)
gentoo resync : 05.12.2021
Diffstat (limited to 'metadata/news')
-rw-r--r--metadata/news/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.en.txt65
-rw-r--r--metadata/news/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.ru.txt67
-rw-r--r--metadata/news/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt14
-rw-r--r--metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt7
-rw-r--r--metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt1
-rw-r--r--metadata/news/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt45
-rw-r--r--metadata/news/Manifest30
-rw-r--r--metadata/news/Manifest.files.gzbin15700 -> 15567 bytes
-rw-r--r--metadata/news/timestamp.chk2
-rw-r--r--metadata/news/timestamp.commit2
10 files changed, 82 insertions, 151 deletions
diff --git a/metadata/news/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.en.txt b/metadata/news/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.en.txt
deleted file mode 100644
index 824919824ee9..000000000000
--- a/metadata/news/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.en.txt
+++ /dev/null
@@ -1,65 +0,0 @@
-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-07-23
-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-14 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 and split-usr (if applicable) USE flag of sys-libs/libxcrypt
-and enable it
-* unmask ~virtual/libcrypt-2
-
-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/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.ru.txt b/metadata/news/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.ru.txt
deleted file mode 100644
index 0aa0b34bb2c6..000000000000
--- a/metadata/news/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.ru.txt
+++ /dev/null
@@ -1,67 +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-07-23
-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
-
-Обратите внимание: если последний раз вы меняли пароль до ~2008 года, он
-может использовать в /etc/shadow слабые хеш-функции, такие как md5crypt.
-При этом ошибка в PAM [0][1] может помешать вам войти в систему.
-Мы рекомендуем вам сменить пароль командой "passwd", чтобы были использованы
-современные методы хеширования паролей. Новая версия PAM с исправлением этой
-ошибки уже добавлена в дерево.
-
-В некоторых случаях Portage может попытаться пересобрать некоторые
-пакеты в неправильном порядке [2]. Если какой-то пакет не собирается,
-попробуйте сначала обновить libcrypt и libxcrypt:
-
-# emerge -v1 virtual/libcrypt sys-libs/libxcrypt
-
-А затем продолжите обновление системы с помощью опции Portage
-"--keep-going=y".
-
-Дополнительные сведения можно найти здесь:
-* 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/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt b/metadata/news/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt
index fd360d7c003f..c2b2b76c5d3b 100644
--- a/metadata/news/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt
+++ b/metadata/news/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt
@@ -23,13 +23,25 @@ in order for Portage to replace eudev with sys-fs/udev once the
package.mask is in place. We fully support udev on musl, whereas uclibc
will still have to rely on eudev before also being removed on 2022-01-01.
- **WARNING**
+ **WARNING 1**
If you happen to have an INSTALL_MASK with a blanket "*systemd*" glob,
you will inevitably break your system. sys-fs/udev contains "systemd" in
some of its filenames, hence a blanket filter rule will likely lead to
a non-functional udev installation.
+
+ **WARNING 2**
+
+If you DO NOT want the "predictable interface naming" of newer versions
+of udev and instead prefer the old style (e.g. "eth0"), there are several
+options available.
+
+The simplest is to pass 'net.ifnames=0' on the kernel command line.
+
+See the wiki for more information:
+https://wiki.gentoo.org/wiki/Udev#Optional:_Disable_or_override_predictable_network_interface_naming.
+
Rationale
The integration of udev into the systemd git repo introduced numerous
diff --git a/metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt b/metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt
index 7154bc497e2e..68aa6af5e8f1 100644
--- a/metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt
+++ b/metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt
@@ -93,7 +93,12 @@ Step 3. Given that there are possible other side-effects of the corruption/bug,
Note that binary packages may need to be discarded given they may
contain corrupt metadata.
- If no libraries were broken, it is likely safe to skip this step.
+ If no libraries were broken, it is likely safe to skip this step. It
+ should be sufficient, for resource-constrained machines, to simply
+ rebuild any broken libraries and their consumers (reverse-dependencies):
+ revdep-rebuild may help you do this.
+
+ (If you do not know what that means, please proceed with Step 3.)
Please see the wiki [0] for a full description of the background
of this problem and handling corner cases such as e.g. already
diff --git a/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt b/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt
index feddaf62ba42..1b80f95cc5ea 100644
--- a/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt
+++ b/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt
@@ -44,6 +44,7 @@ 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
+* unmask virtual/libcrypt:0/1
If you wish to manually migrate now, there are a series
of steps described on the wiki (see below), but the outline is:
diff --git a/metadata/news/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt b/metadata/news/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt
new file mode 100644
index 000000000000..c977ae7f9725
--- /dev/null
+++ b/metadata/news/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt
@@ -0,0 +1,45 @@
+Title: Full MariaDB database restore maybe required
+Author: Thomas Deutschmann <whissi@gentoo.org>
+Posted: 2021-11-23
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: dev-db/mariadb
+Display-If-Installed: sys-cluster/galera
+
+On 2021-11-21, keywords for dev-db/mariadb:10.6 were removed to
+address a file collision with dev-db/mariadb-connector-c. This
+unintentionally triggered a version downgrade for users who had
+successfully upgraded to dev-db/mariadb:10.6 already. [Link 1].
+
+However, downgrades are not supported in MySQL/MariaDB [Link 2].
+
+In case you already fully upgraded to MariaDB 10.6 (which includes
+executing mysql_upgrade command) and unintentionally downgraded your
+MariaDB instance afterwards during the time window when keywords were
+removed, you maybe experiencing different problems:
+
+At best, your unwanted downgraded MariaDB instance prevented startup
+so all you have to do is upgrade to MariaDB 10.6 again to resume
+services.
+
+In case previous MariaDB version was able to start, you are encouraged
+to do a full backup as soon as possible using mysqldump command and
+manually restore each database ("logical downgrade") to prevent any
+data corruption.
+
+Depending on used feature set and from which version you upgraded,
+it is maybe required to do a full restore from a previous backup before
+MariaDB 10.6 upgrade to restore services and prevent any data loss or
+future runtime errors.
+
+In case you are using MariaDB in a cluster and/or Galera setup you
+probably have to rebuild the entire cluster in case the upgrade to
+MariaDB 10.6 was already replicated (using pt-table-checksum from
+dev-db/percona-toolkit can help you to validate your cluster).
+
+Keep in mind that due to the downgrade, point-in-time recovery may
+not be available to the extent that you are used to.
+
+Link 1: https://bugs.gentoo.org/825234
+
+Link 2: https://mariadb.com/kb/en/downgrading-between-major-versions-of-mariadb/
diff --git a/metadata/news/Manifest b/metadata/news/Manifest
index 588431309298..d10d172b6d8d 100644
--- a/metadata/news/Manifest
+++ b/metadata/news/Manifest
@@ -1,23 +1,23 @@
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
-MANIFEST Manifest.files.gz 15700 BLAKE2B 97bd3c94da0f1c427e67e570c2f7ed2d562d6be0adb35a45b3d0148652b9db2c3cb50cb1f572b6b2f5848acb86aa3e27cda606fa4e25357e4cb5dc735b5722ce SHA512 7ec20dcded0dfce802c6b83d4c68e38933c4e940811c83a74df260f6e0a57cbac1d023459bfb1d10a0d3456409fe31706911fd92033d7c318e73a83e2fdebf40
-TIMESTAMP 2021-11-13T11:39:12Z
+MANIFEST Manifest.files.gz 15567 BLAKE2B cd532bfb719406d28a57b3ff201e523cf2465ccb1ef12e028056ad08a70f52dac0ff2cdc2a1a6becac028f9420789fb8a7eccc136e85b813e2211dafca969b00 SHA512 4e4ccf855d52fe6ae642b0d51ffccea68f2f449bae6351a417bf21dc995a0926b8f758b22b2da537dd40a13b2b13e05609df664d895495aa3ba215abacbda0be
+TIMESTAMP 2021-12-05T01:39:13Z
-----BEGIN PGP SIGNATURE-----
-iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAmGPo+BfFIAAAAAALgAo
+iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAmGsGEJfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUx
RDZBQkI2M0JGQ0ZCNEJBMDJGREYxQ0VDNTkwRUVBQzkxODkyNTAACgkQ7FkO6skY
-klB8pQ/+NvJOpHq15LbF1pB2H2UgjzoO3Oh6IPmJ0nbANmWdiFxMh/F8WnFSjzWL
-utkklFMPBq+KyxHgqd1ZMVROHMKJyfVtqY39sJgeZZuog9iyOnHuwcahSWpw6cuI
-TuV8xEH1eoZmVU35/zJh2vQL4thTMCveisQVpi/f0FqYyX9pdWiQQYAhve9bgq0H
-HhT0Ga3eODMQb7wOMHav7t4yjxoiv+LCf+nUNIFawrYe8DPxSwLRaZkWHMJZHAIK
-ZRmVELS+E406//cnGYaZGu7mkvLTlqjJEUs2GXz8isyks7ZSOfQ3VQpcyGBgOUzn
-mkQ5+z0ciMgLar1T57U4hRFTEsWvW/dMV2/Vy9Ddh7Rjodo/JgwJI6E2cbKxt7xH
-uBEDRHHCCT1roDVg5qQUVHVRZVgk3wE8kSrHZXmoB9hmGZ18fg88axXJCUaL9OD0
-32Db058CvRAqOsGYq08YDWTuzZGIL+tfSbSwmnYelCB51ieWCzmjKcGePeu6pCBH
-XUsxknxWt1SqFr2+SE53yLNtEpKs19YOYk6T+4pQPl4EuEFElqmob9cEWd0hHOj1
-SL0N0aLeTCs3RT+pg5sjqSvmcUnIRXsReyN0kYkord+sWHDxqufPHqkwlOhkLTYc
-J8BksrYIPCjZHNHJL/739oxwGdx4dRkRJUmkTQoxufMiK+cMI5E=
-=Uc/M
+klCJ7A//VPSPxc0VN8bqxrN4DRiSlag3ilj0PS1XjNGQfuCqTzmw8riIk0fCzzIA
+qyjTxDCmijbs1X/ccpmlfW+Xp+71vvGtqdXbjrLHAAXC1ESCD4ycQNp13X53uF1p
+Ujsgz5VrcQYtiuqrIzqpxOoZb66VIzuIIkhyaobh+dUDWmAJD2OkBL9WCPgz/kTF
+/M4enGDNDq9K9zaA8Rt8uqfldOqc2GB8/w9tcTFqsgfXX9hQbONH/3yQtSJyDpTU
+iHrxrgO+iqsTqpGwGMky5N9KJmicIWr6qqk36lk9r+RjPEgGgDXdlGf9gCMACnTR
+A6L6PLbqPPgj8REQXnVr1CIfp4nIuj4co/L4jzK34hIHXqgiaZqOznGUh17VqAcE
+Nt/Kj9CeR1QBzc37/qtqqgNVgWqJvlMoqA8HJdeBtJ3JrN9Ge8LSk/wiQFBrKusq
+BycsUaxVBODJ0cZTSjV8Z5GeAQNVOyL/sB88ijyoZXeAmIxibeoj1vwW2i89BvOa
+eNCbTO0x1qKAA323HztjCUA9YNLL2ISA/IQz60Idk5M+HBQa6LB0mSoajc67PK5V
+PPbKxB5959xOAxUD08Rz3YPD6fEM1YFupAgZIQE2NHjatmZj3JkKUv1m8Rt5AGqZ
+Xo+pLVgwK1rtQeh/1ux2MNFZqYuQghriuBGuABBs3wWS6yFY9q8=
+=6cp7
-----END PGP SIGNATURE-----
diff --git a/metadata/news/Manifest.files.gz b/metadata/news/Manifest.files.gz
index f30b88eb4f7a..1f5f7a232566 100644
--- a/metadata/news/Manifest.files.gz
+++ b/metadata/news/Manifest.files.gz
Binary files differ
diff --git a/metadata/news/timestamp.chk b/metadata/news/timestamp.chk
index 221f6aa77c30..6510b8316a75 100644
--- a/metadata/news/timestamp.chk
+++ b/metadata/news/timestamp.chk
@@ -1 +1 @@
-Sat, 13 Nov 2021 11:39:08 +0000
+Sun, 05 Dec 2021 01:39:08 +0000
diff --git a/metadata/news/timestamp.commit b/metadata/news/timestamp.commit
index ef4c21db9c70..ddafe0205a8f 100644
--- a/metadata/news/timestamp.commit
+++ b/metadata/news/timestamp.commit
@@ -1 +1 @@
-1c4eb83b3e4a1f453d16e8a2356ddf61651b5310 1636693106 2021-11-12T04:58:26+00:00
+eba63773624dd2dbdceefdf8ab2c88aab22dab40 1638408994 2021-12-02T01:36:34+00:00