gentoo Easter resync : 12.04.2020

13 files changed, 153 insertions, 124 deletions

diff --git a/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt b/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt
deleted file mode 100644
index 47d54f476d90..000000000000
--- a/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt
+++ /dev/null
@@ -1,35 +0,0 @@
-Title: ffmpeg/libav conflict management: USE=libav
-Author: Michał Górny <mgorny@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-02-01
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Installed: media-video/ffmpeg
-Display-If-Installed: media-video/libav
-
-The support for automatic choice between ffmpeg and libav is going to be
-deprecated in favor of explicit choice via USE flags. This change aims
-to solve multiple repeating issues, including Portage undesirably
-wanting to replace one package with the other, lack of proper reverse
-dependency on ffmpeg/libav upgrades and some of the hard-to-understand
-upgrade failures involving blockers. It also may be used to make ffmpeg
-and libav co-installable in the future.
-
-The current USE=ffmpeg will maintain its role of enabling optional
-support for ffmpeg or a compatible implementation (libav) in a package.
-However, whenever appropriate additional USE=libav will be introduced to
-control the preference of one implementation over the other.
-
-Users who currently use libav need to enable USE=libav in
-/etc/portage/make.conf. It should be noted that users still need to
-enable USE=ffmpeg on packages with optional libav support as well.
-Users who currently use ffmpeg need to take no action.
-
-Please also note that some packages support only one of the two
-implementations. An attempt to install one of those packages may result
-in blockers requiring the user changes the global USE=libav state.
-
-Please do not alter the state of 'libav' flag on a per-package basis
-(e.g. via package.use). The flag needs to be set globally to have
-consistent value throughout all packages. Otherwise, blockers will
-prevent upgrades.
diff --git a/metadata/news/2015-04-16-ffmpeg-default/2015-04-16-ffmpeg-default.en.txt b/metadata/news/2015-04-16-ffmpeg-default/2015-04-16-ffmpeg-default.en.txt
deleted file mode 100644
index 82c01f18678a..000000000000
--- a/metadata/news/2015-04-16-ffmpeg-default/2015-04-16-ffmpeg-default.en.txt
+++ /dev/null
@@ -1,25 +0,0 @@
-Title: FFmpeg default
-Author: Ben de Groot <yngwin@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-04-16
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: media-video/ffmpeg
-Display-If-Installed: media-video/libav
-
-Since the choice between ffmpeg and libav has been made more
-explicit, there has been a lot of discussion about what the
-default implementation should be. It can be concluded that
-media-video/ffmpeg has wider support, and would be somewhat
-more convenient for most end-users.
-
-For this reason the default implementation has been switched
-back from media-video/libav to media-video/ffmpeg by removing
-the libav useflag from the base profile.
-
-If the libav useflag is already globally enabled or disabled
-in /etc/portage/make.conf, then no further action is required.
-
-Users who implicitly relied on libav being enabled in their
-profile, and who wish to continue using libav, should enable
-USE=libav in their /etc/portage/make.conf file.
diff --git a/metadata/news/2015-10-22-gcc-5-new-c++11-abi/2015-10-22-gcc-5-new-c++11-abi.en.txt b/metadata/news/2015-10-22-gcc-5-new-c++11-abi/2015-10-22-gcc-5-new-c++11-abi.en.txt
deleted file mode 100644
index 9760753cee3c..000000000000
--- a/metadata/news/2015-10-22-gcc-5-new-c++11-abi/2015-10-22-gcc-5-new-c++11-abi.en.txt
+++ /dev/null
@@ -1,26 +0,0 @@
-Title: GCC 5 Defaults to the New C++11 ABI
-Author: Mike Frysinger <vapier@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-10-22
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Installed: >=sys-devel/gcc-5
-
-GCC 5 uses the new C++ ABI by default.  When building new code, you might run
-into link time errors that include lines similar to:
-...: undefined reference to '_ZNSt6chrono12steady_clock3nowEv@GLIBCXX_3.4.17'
-
-Or you might see linkage failures with "std::__cxx11::string" in the output.
-
-These are signs that you need to rebuild packages using the new C++ ABI.
-You can quickly do so by using revdep-rebuild (from gentoolkit).
-
-For gentoolkit-0.3.1 or higher:
-# revdep-rebuild --library 'libstdc++.so.6' -- --exclude gcc
-
-For previous versions of gentoolkit:
-# revdep-rebuild --library 'libstdc\+\+\.so\.6' -- --exclude gcc
-
-For more details, feel free to peruse:
-https://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/
-https://blogs.gentoo.org/blueness/2015/03/10/the-c11-abi-incompatibility-problem-in-gentoo/
diff --git a/metadata/news/2016-08-11-grub2_multislot_default/2016-08-11-grub2_multislot_default.en.txt b/metadata/news/2016-08-11-grub2_multislot_default/2016-08-11-grub2_multislot_default.en.txt
deleted file mode 100644
index 2cd1891c405a..000000000000
--- a/metadata/news/2016-08-11-grub2_multislot_default/2016-08-11-grub2_multislot_default.en.txt
+++ /dev/null
@@ -1,21 +0,0 @@
-Title: Grub2 multislot default setting is changing
-Author: William Hubbs <williamh@gentoo.org>
-Author: Ian Stakenvicius <axs@gentoo.org>
-Content-Type: text/plain
-Posted: 2016-08-11
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: >=sys-boot/grub-2
-
-The multislot use flag in sys-boot/grub-2.x is no longer enabled by
-default.
-
-When the flag is enabled, all upstream binaries and documentation are
-renamed to "grub2" so as not to collide with grub-0.  Now that the use
-flag is no longer default-enabled, these names will revert back to
-their upstream defaults.  For example, grub2-mkconfig will become
-grub-mkconfig, grub2-install will become grub-install, etc.
-
-If you wish to retain the previous naming scheme, please make sure to
-explicitly enable USE="multislot" on sys-boot/grub in the usual manner.
-
diff --git a/metadata/news/2020-02-19-openssh-8_2-service-breakage/2020-02-19-openssh-8_2-service-breakage.en.txt b/metadata/news/2020-02-19-openssh-8_2-service-breakage/2020-02-19-openssh-8_2-service-breakage.en.txt
new file mode 100644
index 000000000000..40a309deafbc
--- /dev/null
+++ b/metadata/news/2020-02-19-openssh-8_2-service-breakage/2020-02-19-openssh-8_2-service-breakage.en.txt
@@ -0,0 +1,30 @@
+Title: OpenSSH 8.2_p1 running sshd breakage
+Author: Patrick McLean <chutzpah@gentoo.org>
+Posted: 2020-02-20
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: <net-misc/openssh-8.2
+
+If sshd is running, and a system is upgraded from
+<net-misc/openssh-8.2_p1 to >=net-misc/openssh-8.2_p1, any new ssh
+connection will fail until sshd is restarted.
+
+Before restarting sshd, it is *strongly* recommended that you test your
+configuration with the following command (as root):
+    sshd -t
+
+If your system is booted with openrc, use this command (as root) 
+to restart sshd:
+    rc-service sshd --nodeps restart
+
+If your system is booted with systemd, use this command (as root)
+to restart sshd:
+    systemctl restart sshd
+
+WARNING: On systemd booted machines with PAM disabled, this command
+         will terminate all currently open ssh connections. It is 
+         *strongly* recommended that you validate your configuration
+         before restarting sshd.
+
+If you are using systemd socket activation for sshd, then no action is
+required.
diff --git a/metadata/news/2020-03-30-stable-ia64-keywords-removed/2020-03-30-stable-ia64-keywords-removed.en.txt b/metadata/news/2020-03-30-stable-ia64-keywords-removed/2020-03-30-stable-ia64-keywords-removed.en.txt
new file mode 100644
index 000000000000..ad55ad168961
--- /dev/null
+++ b/metadata/news/2020-03-30-stable-ia64-keywords-removed/2020-03-30-stable-ia64-keywords-removed.en.txt
@@ -0,0 +1,14 @@
+Title: Stable ia64 keywords removed
+Author: Matt Turner <mattst88@gentoo.org>
+Posted: 2020-03-30
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Keyword: ia64
+
+The Gentoo/IA64 team no longer thinks that the time invested in package
+stabilization is warranted for the small number of users on IA64. As a
+result, we will drop all "ia64" keywords to "~ia64" on 2020-04-03 and will
+add "~ia64" to ACCEPT_KEYWORDS in the profile.
+
+Users need not make any changes to their systems, and the Gentoo/IA64 team
+has no plans to remove support for the architecture.
diff --git a/metadata/news/2020-04-03-deprecation-of-legacy-x11-input-drivers/2020-04-03-deprecation-of-legacy-x11-input-drivers.en.txt b/metadata/news/2020-04-03-deprecation-of-legacy-x11-input-drivers/2020-04-03-deprecation-of-legacy-x11-input-drivers.en.txt
new file mode 100644
index 000000000000..6f7dd7bbbc26
--- /dev/null
+++ b/metadata/news/2020-04-03-deprecation-of-legacy-x11-input-drivers/2020-04-03-deprecation-of-legacy-x11-input-drivers.en.txt
@@ -0,0 +1,45 @@
+Title: Deprecation of legacy X11 input drivers
+Author: Piotr Karbowski <slashbeast@gentoo.org>
+Posted: 2020-04-03
+Revision: 2
+News-Item-Format: 2.0
+Display-If-Installed: x11-drivers/xf86-input-mouse
+Display-If-Installed: x11-drivers/xf86-input-keyboard
+
+The Gentoo X11 Team is announcing the deprecation and future removal of
+the legacy X11 input drivers x11-drivers/xf86-input-mouse and
+x11-drivers/xf86-input-keyboard. As of 2020-05-01 those input drivers
+will be masked for removal.
+
+These drivers have been deprecated for many years, first by
+xf86-input-evdev and then by xf86-input-libinput.
+
+The only use for those drivers remain in deployments which intentionally
+opt-out of using udev, as both evdev and libinput require udev during
+runtime, however given that upstream has already removed the Linux
+support from xf86-input-keyboard, future X11 releases will no longer
+support xf86-input-keyboard on Linux rendering those installation
+infeasible to use without udev.
+
+In order to ensure frictionless upgrade path for future X11 releases, we
+have decided to deprecate those drivers that are not in active use by
+pretty much any installation of Gentoo.
+
+No action is required from end-users who are already using libinput (or
+evdev). To check which driver is in use, one can use
+
+    $ grep 'Using input driver' ~/.local/share/xorg/Xorg.0.log
+
+for the systems running xorg-server as regular user (-suid
++elogind/+systemd) or by running
+
+    # grep 'Using input driver' /var/log/Xorg.0.log
+
+for those running xorg-server as root.
+
+If however neither libinput or evdev is in use, one should append
+'libinput' to the INPUT_DEVICES variable inside /etc/portage/make.conf
+while removing 'keyboard' and 'mouse' if present, then update @world
+with new USE flags
+
+    # emerge -N @world
diff --git a/metadata/news/2020-04-03-kubernetes-moving-to-single-package/2020-04-03-kubernetes-moving-to-single-package.en.txt b/metadata/news/2020-04-03-kubernetes-moving-to-single-package/2020-04-03-kubernetes-moving-to-single-package.en.txt
new file mode 100644
index 000000000000..499b30a1feb6
--- /dev/null
+++ b/metadata/news/2020-04-03-kubernetes-moving-to-single-package/2020-04-03-kubernetes-moving-to-single-package.en.txt
@@ -0,0 +1,31 @@
+Title: K8s Moving to a Single Package
+Author: William Hubbs <williamh@gentoo.org>
+Posted: 2020-04-03
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: sys-cluster/kubeadm
+Display-If-Installed: sys-cluster/kube-apiserver
+Display-If-Installed: sys-cluster/kube-controller-manager
+Display-If-Installed: sys-cluster/kubectl
+Display-If-Installed: sys-cluster/kubelet
+Display-If-Installed: sys-cluster/kube-proxy
+Display-If-Installed: sys-cluster/kube-scheduler
+
+Formerly, we packaged kubernetes as seven separate packages:
+
+sys-cluster/kubeadm, sys-cluster/kube-apiserver,
+sys-cluster/kube-controller-manager, sys-cluster/kubectl,
+sys-cluster/kubelet, sys-cluster/kube-proxy and
+sys-cluster/kube-scheduler.
+
+Starting with kubernetes 1.18.0, 1.17.5 and 1.16.9, these will be merged
+into one package, sys-cluster/kubernetes. The components of this package
+which are build and installed will be selectable by use flags.
+
+If you are using 1.16.x or 1.17.x and would like to migrate to the
+single package without upgrading, I have also made 1.16.8 and 1.17.4
+available in this new package.
+
+Currently, everything is built and installed by default; however, I am
+open to changing this if there is a better way to configure the default
+build.
diff --git a/metadata/news/2020-04-03-kubernetes-moving-to-single-package/2020-04-03-kubernetes-moving-to-single-package.en.txt.asc b/metadata/news/2020-04-03-kubernetes-moving-to-single-package/2020-04-03-kubernetes-moving-to-single-package.en.txt.asc
new file mode 100644
index 000000000000..e9f1aefe605f
--- /dev/null
+++ b/metadata/news/2020-04-03-kubernetes-moving-to-single-package/2020-04-03-kubernetes-moving-to-single-package.en.txt.asc
@@ -0,0 +1,16 @@
+-----BEGIN PGP SIGNATURE-----
+
+iQIzBAABCAAdFiEEnB9e/J8YI6T0NBsJm0Co7cr65zMFAl6HwJ0ACgkQm0Co7cr6
+5zNd5xAAsSSs++Ga+KQUVziwYdWBxC/AizJssBsVfPD4leyVz80bX+JYAqblqsCo
+pVyNpA64dcOo9nEY7JAGEoSnvuND2IUutt8sKs4Wjgc/B9kt7IIqaSYlmLfbEBo1
+3ozdUQ8RIAalsQwjJMuShq/RgK1D/NKqqEVuDR9zhuW1X81fNUaKVf2QDFpm6rJV
+Ho50Uwaac5Wkn9fruIeinl0YYn338FEpabgFfuVcABhNYJr/f9CJ5yjdV06CBFJH
+cjlTlwlnQQl599zEO44fq9ZvYRn7aUAzzyA8ykRi7gCsqEOdc6v1HunDRNDOBR1w
+ftMm8Du7rEr0nyqEJw7/CqS+UgNn4uJ6tB8LF151ZApE3DDoulfrEtQODAe9Xxv+
+4WFm+T2oX+9Ii1vueDrDjG6uoiUPBIiRV8Rbd7fstOdsbmGvdqFLAgs5oQiPfp0U
+l8VPHoezg42kr0Zjy30Poubzl6dDoLlRYcIHjQIIYlXPMoql6U0T3IIYb7uaQWtl
+piJ3Zs/B7Co8FhJAXHmP0fZ0vbggF+q/ax+QJCOq+fpO1PUqG9d8qb11NgnNiQeN
+RhncuwGL8hbobrDswTyawfxo9hHv3ORryAE/qNS9xpVFj2cG2rDdail6Vw/l64UR
+Agg18g4xzeyKbri0LzkURQCsLJVg22U2GFRAz20v8/BSnmCnXdE=
+=x3lR
+-----END PGP SIGNATURE-----
diff --git a/metadata/news/Manifest b/metadata/news/Manifest
index 687dd405a18b..961e06a692e5 100644
--- a/metadata/news/Manifest
+++ b/metadata/news/Manifest
@@ -1,23 +1,23 @@
 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA512
 
-MANIFEST Manifest.files.gz 13002 BLAKE2B 47e7135a6a305185482ecd03c9679ad57a3a6b2c2960a15e2ff9bd1141ba078ea01d13d5bce936f860090db1a93d8226d869a2594d126db9ed34cf0ed5907801 SHA512 fdddccc915b4305e95506ac62eccf0d13e35b757d53e29ea36e8894697c26bdb906b011e6465bb8a6bec7f2dc0853d3e7b36336c72ab7a013b59fd2c277c7b98
-TIMESTAMP 2020-02-29T17:08:56Z
+MANIFEST Manifest.files.gz 13175 BLAKE2B 7eb738320345232ed2736a961e6688799f400d3000b5a8c07e207eb5018330e5e1d98a631168fb83ee021c13c98bebe7361bfa07f5507ec69c1f3ace0b23fceb SHA512 11dd46c9fdf08776322324c26f6a98dcb2de725556bea172e4668c76998844721c7894523de2828e7e1355dca7b7a057a368b55db3e47ffe97e8e0908203a328
+TIMESTAMP 2020-04-12T01:38:57Z
 -----BEGIN PGP SIGNATURE-----
 
-iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAl5amqhfFIAAAAAALgAo
+iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAl6ScTFfFIAAAAAALgAo
 aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUx
 RDZBQkI2M0JGQ0ZCNEJBMDJGREYxQ0VDNTkwRUVBQzkxODkyNTAACgkQ7FkO6skY
-klAM9hAAjU6+PvTEwMNp6BpH0of9PQBhdPFgYim5+H49RDeW8YkEpFkEjxHVratL
-9hhUNo84wT69Sv5oYras3tOPjSqsjwTNJ51/8rcyz3jfnIsEf30Y5sBCx5MN91TI
-iOmq7+tOIJ3Iap0HLyi1Bhvy6Qge8WnghDR32eJljK+aUC5dSjG8Bhmc4A8sOcSz
-r2nYU2QMCD7N2MpADFsIHvOJwHX/CWIrgFyhQ2iUZSZhkSb+GEyqZu4z7J1rXkMe
-SsuXEhCqAGfKkVj5BEHgccyMdyF6WPmyUPnQpXRRqHFvBM//17emPh8QokycmL43
-wGdehd+wAp7xkiftfmdawUI/maDNqnSS8Jh1Z3JLVKp1GZ9e0v8FKj7mTnR1CIg3
-ZKdHaQfr7GzTMa3HpQK7+CMAoChxZDzx4kVS+v3/GuWUpNDHbnyN7ETbG5fsUbsH
-tA3SCtFbmuKjEYw+5bM9C2hzJwjc2oWm4yAjvq68c0CsEHIJld+P71D7ppLTydMl
-itnV2CpsyN2jEsbWcoQyUvvnq7TpDeI/LEtjqGJpVdGNrDCl0lzAaJY0Dxd6zSa7
-KrslexBQv1N+h9yZDtYrr/Cfbgs/JlICzD1+T5GY4Y3GrXwtRKq1B5lNYBWKU0o8
-A0vRpKIMsPWTPcBI5JKGFVgkOJKhyVRcypxYu3nBUMEw1GE0ki4=
-=A1Bb
+klBNgg/9G52SnSzcD3qo0v0o1Bm4SdVkgHnroq9RX4obV5MnxoXattkQeDEBLS/u
+Cdis+6RCXXOHv/qaeiQiyW4f8kYZ9VVIGgeivy6sSl9CRWNXVI6swpPit1lMgiLP
++kEczT+XMe9PZEd6jXMK+ECoEmgdeY+F37HGHuLD3132dDffIdR/MX9BURBe+8PV
+Pu7uOOMrD31hjkNCOaQb7v2Uj9frn5phZ3VD/RgzHjlQKN8IRLE8K5oEDWVHny08
+JSFJ9fvS4Mh2coaLMOfgwCGYAPXQGXaytS68Wjrnt/VAdiooORsersTh/FYIhsAQ
+hA4nej/Bz8c7z+v7AevrdDQ+wANbctTjtwmN9aj1vipUnpPWQDYK/bKGNaRWsbvz
+2J18GupQiQKCtVpTClG2nuuzQEZs6KmGFu6ZtJqMPrd2R7+/cAxxaVQL+g32ECGz
+1oZ1mpJRwp9qqK1yZ/Rx/2ys+w3bXDATjY0VvjlRXYJObddG8deO0q9pnjtOsiPI
+S+0QAmXvUUHNbMzqxHcgyBDcgPogAqqL/mgXDuIMHRmJjKCbt8XBKlwI2wjPSNhK
+1DJdfbbSb88Aev5SIItjuvyteAonasj2cwRDw/1z/rKOvRC9bI8deVsRAkNrvGE+
+czE0k9HatbEf+DfQoAQwku9gN7/rkECIMMY3nkFwkB9v2KKDRvA=
+=W/bt
 -----END PGP SIGNATURE-----
diff --git a/metadata/news/Manifest.files.gz b/metadata/news/Manifest.files.gz
index d9d1a60c8d10..ebaf491520b3 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 166b262f78ad..5259482477da 100644
--- a/metadata/news/timestamp.chk
+++ b/metadata/news/timestamp.chk
@@ -1 +1 @@
-Sat, 29 Feb 2020 17:08:53 +0000
+Sun, 12 Apr 2020 01:38:54 +0000
diff --git a/metadata/news/timestamp.commit b/metadata/news/timestamp.commit
index a35a8357ed5f..6fcc4a7ef77d 100644
--- a/metadata/news/timestamp.commit
+++ b/metadata/news/timestamp.commit
@@ -1 +1 @@
-bb6ecae5a95bc13b2ec01a5bf3188d87df9a0c2c 1581078273 2020-02-07T12:24:33+00:00
+50254233f26f276c0597fb72614d982657f2227d 1586370336 2020-04-08T18:25:36+00:00