summaryrefslogtreecommitdiff
path: root/metadata/news
diff options
context:
space:
mode:
Diffstat (limited to 'metadata/news')
-rw-r--r--metadata/news/2015-02-02-nfs-service-changes/2015-02-02-nfs-service-changes.en.txt39
-rw-r--r--metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt77
-rw-r--r--metadata/news/2015-04-06-apache-addhandler-addtype/2015-04-06-apache-addhandler-addtype.en.txt100
-rw-r--r--metadata/news/2015-05-01-shorewall-changes/2015-05-01-shorewall-changes.en.txt43
-rw-r--r--metadata/news/2015-06-08-udev-init-scripts-changes/2015-06-08-udev-init-scripts-changes.en.txt20
-rw-r--r--metadata/news/2015-08-11-nepomuk-removal/2015-08-11-nepomuk-removal.en.txt24
-rw-r--r--metadata/news/2015-08-26-ruby-19-removal/2015-08-26-ruby-19-removal.en.txt26
-rw-r--r--metadata/news/2015-09-09-libvirt-init-script-changes/2015-09-09-libvirt-init-script-changes.en.txt24
-rw-r--r--metadata/news/2015-10-07-openrc-0-18-localmount-and-netmount-changes/2015-10-07-openrc-0-18-localmount-and-netmount-changes.en.txt17
-rw-r--r--metadata/news/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt62
-rw-r--r--metadata/news/2015-12-16-python-abiflags-rebuild-needed/2015-12-16-python-abiflags-rebuild-needed.en.txt53
-rw-r--r--metadata/news/2019-02-13-virtual-mysql-depenedency/2019-02-13-virtual-mysql-depenedency.en.txt19
-rw-r--r--metadata/news/2019-08-30-php-5_6-deprecation/2019-08-30-php-5_6-deprecation.en.txt69
-rw-r--r--metadata/news/2020-12-26-most-stable-hppa-keywords-removed/2020-12-26-most-stable-hppa-keywords-removed.en.txt15
-rw-r--r--metadata/news/Manifest30
-rw-r--r--metadata/news/Manifest.files.gzbin12077 -> 10052 bytes
-rw-r--r--metadata/news/README7
-rw-r--r--metadata/news/timestamp.chk2
-rw-r--r--metadata/news/timestamp.commit2
19 files changed, 39 insertions, 590 deletions
diff --git a/metadata/news/2015-02-02-nfs-service-changes/2015-02-02-nfs-service-changes.en.txt b/metadata/news/2015-02-02-nfs-service-changes/2015-02-02-nfs-service-changes.en.txt
deleted file mode 100644
index 7e1b2be650ca..000000000000
--- a/metadata/news/2015-02-02-nfs-service-changes/2015-02-02-nfs-service-changes.en.txt
+++ /dev/null
@@ -1,39 +0,0 @@
-Title: nfs service changes
-Author: William Hubbs <williamh@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-02-02
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <=net-fs/nfs-utils-1.3.1-r1
-
-The upgrade to nfs-utils-1.3.1-r1 includes significant service changes
-both for OpenRC and systemd users.
-
-OpenRC users:
-
-The OpenRC service which handled mounting nfs file systems has been
-changed to only start the nfs client daemons and renamed to nfsclient.
-Because of this change, if you use OpenRC and mount nfs file systems,
-you need to perform the following steps:
-
-Add nfsclient to the runlevel nfsmount was in before. For example, if
-nfsmount was in the default runlevel, run this command:
-
-rc-update add nfsclient default
-
-If you use a permanent network connection to the server, make sure
-netmount is in the same runlevel as nfsclient. If not, it is recommended
-that net-fs/autofs be set up to handle your network mounts.
-
-Systemd users:
-
-The nfs systemd units have been renamed. If you are exporting nfs
-mounts, you should enable the rpcbind and nfs-server services. If you
-are mounting nfs mounts systemd should automatically detect this and
-start the nfs-client service.
-
-More Information:
-
-The following wiki page has more information about nfs file systems:
-
-http://wiki.gentoo.org/wiki/NFSv4
diff --git a/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt b/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt
deleted file mode 100644
index aeff021602be..000000000000
--- a/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt
+++ /dev/null
@@ -1,77 +0,0 @@
-Title: New portage plug-in sync system
-Author: Brian Dolbec <dolsen@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-02-02
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <sys-apps/portage-2.3.62
-
-There is a new plug-in sync system in >=sys-apps/portage-2.2.16.
-This system will allow third party modules to be easily installed. Look
-for a new layman plug-in sync module in layman's next release. Next is
-a brief look at the changes. See the url [1] listed below for detailed
-descriptions and usage.
-
-Changes: /etc/portage/repos.conf/*
- New setting for all repository types (needed):
- auto-sync = yes/no, true/false # default if absent: yes/true
-
- New for git sync-type: (applies to clone only)
- sync-depth = n where n = {0,1,2,3,...} (optional, default = 1)
- 0 -- full history
- 1 -- shallow clone, only current state (default)
- 2,3,... number of history changes to download
-
- New sync-type modules:
- sync-type = svn # sync a subversion repository
- sync-type = websync # Perform an emerge-webrsync operation
- sync-type = laymanator # (if installed) runs a layman -s action
-
- New native portage postsync hooks
- /etc/portage/postsync.d/*
- Runs hooks once, only after all repos have been synced.
- /etc/portage/repo.postsync.d/*
- Runs each script with three arguments:
- repo name, sync-uri, location
- Each script is run at the completion of every repo synced.
-
-Migration:
- Edit /etc/portage/repos.conf/*.conf files, add the auto-sync option
- to each repository definition. Edit sync-type option to one of the
- supported types {rsync, git, cvs, svn, websync, laymanator}.
- [some-repo]
- ...
- sync-type = rsync
- auto-sync = yes
-
- For an existing /etc/portage/repos.conf/layman.conf file:
- 1) change/add the sync-type
- sync-type = laymanator
- 2) Ensure you have the correct layman version installed with
- it's laymanator module also installed.
- Alternate method:
- Please see the wiki page url [1] for detailed instructions.
-
-Primary control of all sync operations has been moved from emerge to
-emaint. "emerge --sync" now just calls the emaint sync module with the
---auto option. The --auto option performs a sync on only those
-repositories with the auto-sync setting not set to 'no' or 'false'. If
-it is absent, then it will default to yes and "emerge --sync" will sync
-the repository.
-
-NOTE: As a result of the default auto-sync = True/Yes setting, commands
- like "eix-sync", "esync -l", "emerge --sync && layman -S" will cause
- many repositories to be synced multiple times in a row. Please edit
- your configs or scripts to adjust for the new operation.
-
-WARNING:
- Due to the above default. For any repos that you EXPLICITLY do not
- want to be synced. You MUST set "auto-sync = no"
-
-The 'emaint sync' module operates similar to layman. It can sync
-single or multiple repos. See "emaint --help" or for more details and
-examples see the wiki page listed below [1].
-
-Additional help and project API documentation can be found at:
-
-[1] https://wiki.gentoo.org/wiki/Project:Portage/Sync
diff --git a/metadata/news/2015-04-06-apache-addhandler-addtype/2015-04-06-apache-addhandler-addtype.en.txt b/metadata/news/2015-04-06-apache-addhandler-addtype/2015-04-06-apache-addhandler-addtype.en.txt
deleted file mode 100644
index f90d09191dee..000000000000
--- a/metadata/news/2015-04-06-apache-addhandler-addtype/2015-04-06-apache-addhandler-addtype.en.txt
+++ /dev/null
@@ -1,100 +0,0 @@
-Title: Apache AddHandler/AddType exploit protection
-Author: Sebastian Pipping <sping@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-04-06
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Installed: www-servers/apache
-
-Apache's directives AddHandler [1] and AddType [2] can be used
-to map certain file name extensions (e.g. .php) to a handler
-(e.g. application/x-httpd-php). While a line like
-
- AddHandler application/x-httpd-php .php .php5 .phtml
- ^^^^^^^
-matches index.php, it also matches index.php.png.
-With
-
- AddType application/x-httpd-php .php .php5 .phtml
- ^^^^
-index.php.png is not executed, but index.php.disabled still is.
-
-
-Apache's notes on multiple file extensions [3] document
-a multi-language website as a context where that behavior
-may be helpful. Unfortunately, it can also be a security threat.
-
-Combined with (not just PHP) applications that support
-file upload, the AddHandler/AddType directive can get you into
-remote code execution situations.
-
-That is why >=app-eselect/eselect-php-0.7.1-r4 avoids AddHandler
-and is shipping
-
- <FilesMatch "\.(php|php5|phtml)$">
- SetHandler application/x-httpd-php
- </FilesMatch>
-
-instead.
-
-
-Why this news entry?
-
- * Since Apache configuration lives below /etc,
- you need to run etc-update (or a substitute)
- to actually have related fixes applied.
- To get them into the running instance of Apache,
- you need to make it reload its configuration, e.g.
-
- sudo /etc/init.d/apache2 reload
-
- * If you are currently relying on AddHandler to execute
- secret_database_stuff.php.inc, moving away from AddHandler
- could result in serving your database credentials in plain
- text. A command like
-
- find /var/www/ -name '*.php.*' \
- -o -name '*.php5.*' \
- -o -name '*.phtml.*'
-
- may help discovering PHP files that would no longer be executed.
-
- Shipping automatic protection for this scenario is not trivial,
- but you could manually install protection based on this recipe:
-
- <FilesMatch "\.(php|php5|phtml|phps)\.">
- # a) Apache 2.2 / Apache 2.4 + mod_access_compat
- #Order Deny,Allow
- #Deny from all
-
- # b) Apache 2.4 + mod_authz_core
- #Require all denied
-
- # c) Apache 2.x + mod_rewrite
- #RewriteEngine on
- #RewriteRule .* - [R=404,L]
- </FilesMatch>
-
- * You may be using AddHandler or AddType in other places,
- including off-package files. Please have a look.
-
- * app-eselect/eselect-php is not the only package affected.
- There is a dedicated tracker bug at [4].
- As of the moment, affected packages include:
-
- app-eselect/eselect-php[apache2]
- net-nds/gosa-core
- www-apache/mod_fastcgi
- www-apache/mod_flvx
- www-apache/mod_python
- www-apache/mod_suphp
- www-apps/moinmoin
- www-apps/rt[-lighttpd]
-
-
-Thanks to Nico Suhl, Michael Orlitzky and Marc Schiffbauer.
-
-[1] https://httpd.apache.org/docs/current/mod/mod_mime.html#addhandler
-[2] https://httpd.apache.org/docs/current/mod/mod_mime.html#addtype
-[3] https://httpd.apache.org/docs/current/mod/mod_mime.html#multipleext
-[4] https://bugs.gentoo.org/show_bug.cgi?id=544560
diff --git a/metadata/news/2015-05-01-shorewall-changes/2015-05-01-shorewall-changes.en.txt b/metadata/news/2015-05-01-shorewall-changes/2015-05-01-shorewall-changes.en.txt
deleted file mode 100644
index 08d1cdbf1bb4..000000000000
--- a/metadata/news/2015-05-01-shorewall-changes/2015-05-01-shorewall-changes.en.txt
+++ /dev/null
@@ -1,43 +0,0 @@
-Title: shorewall is now a single package
-Author: Ian Delaney <idella4@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-05-01
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: net-firewall/shorewall-core
-Display-If-Installed: net-firewall/shorewall6
-Display-If-Installed: net-firewall/shorewall-lite
-Display-If-Installed: net-firewall/shorewall6-lite
-Display-If-Installed: net-firewall/shorewall-init
-
-Starting with net-firewall/shorewall-4.6 we have re-integrated
-
- - net-firewall/shorewall-core
- - net-firewall/shorewall6
- - net-firewall/shorewall-lite
- - net-firewall/shorewall6-lite
- - net-firewall/shorewall-init
-
-into a new all-in-one net-firewall/shorewall ebuild (see bug 522278).
-
-The new all-in-one ebuild makes maintenance a lot more easier because the
-package is proxy-maintained and finding someone who is willing to help
-you bumping 6 packages each time you provide an update was not easy in
-the past.
-
-Because net-firewall/shorewall{-core,6,-lite,6-lite,init} is now
-integrated in net-firewall/shorewall, we have to hard mask these old
-ebuilds in the new monolithic ebuild to prevent file collisions.
-
-Due to this block we cannot migrate to the new version without user
-interaction. Please remove the previous split ebuilds from your system if
-you want to upgrade:
-
- $ emerge --ask --unmerge 'net-firewall/shorewall-*' \
- 'net-firewall/shorewall6*'
-
-
-Please note:
-Since the second shorewall-4.6 ebuild is now stabilized and shorewall-4.5
-is not compatible with the perl-5.20 (see bug 524558) we will start the
-removal process for shorewall-4.5 ebuilds within the next 30 days.
diff --git a/metadata/news/2015-06-08-udev-init-scripts-changes/2015-06-08-udev-init-scripts-changes.en.txt b/metadata/news/2015-06-08-udev-init-scripts-changes/2015-06-08-udev-init-scripts-changes.en.txt
deleted file mode 100644
index 5ab36d74f995..000000000000
--- a/metadata/news/2015-06-08-udev-init-scripts-changes/2015-06-08-udev-init-scripts-changes.en.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-Title: udev-init-scripts-29 important changes
-Author: William Hubbs <williamh@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-06-08
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Installed: <=sys-fs/udev-init-scripts-29
-
-In udev-init-scripts-29 and newer, the udev service script has been
-split into udev, udev-settle and udev-trigger.
-
-This means the settings in /etc/conf.d/udev have also been migrated
-to the appropriate /etc/conf.d files, so be careful when you update your
-configuration settings.
-
-udev and udev-trigger will be added to your sysinit runlevel, but not
-udev-settle. udev-settle should not be added to a runlevel. Instead, if
-a service needs this, it should add "need udev-settle" to its
-dependencies.
-
diff --git a/metadata/news/2015-08-11-nepomuk-removal/2015-08-11-nepomuk-removal.en.txt b/metadata/news/2015-08-11-nepomuk-removal/2015-08-11-nepomuk-removal.en.txt
deleted file mode 100644
index 488c980fbed5..000000000000
--- a/metadata/news/2015-08-11-nepomuk-removal/2015-08-11-nepomuk-removal.en.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-Title: Nepomuk removal
-Author: Johannes Huber <johu@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-08-11
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: dev-db/virtuoso-server
-
-With KDE SC 4.13.0 release the default semantic desktop search engine
-switched from Nepomuk to Baloo.[1] This change was honoured in Gentoo
-by changing the semantic-desktop use flag to cover the new engine and
-moving the old to nepomuk use flag.
-
-The underlaying storage backend for Nepomuk aka Virtuoso DB has a lot
-of unsolved upstream issues[2], therefore we will remove it. This means
-packages with build options on the old stack will drop them. Other
-packages which hard requiring it will be removed.
-
-If you are still using Nepomuk you can switch to Baloo by globally
-enable semantic-desktop and disabling nepomuk use flag in
-/etc/portage/make.conf or using one of the kde desktop profiles.
-
-[1] https://www.kde.org/announcements/4.13/
-[2] https://bugs.gentoo.org/buglist.cgi?quicksearch=virtuoso
diff --git a/metadata/news/2015-08-26-ruby-19-removal/2015-08-26-ruby-19-removal.en.txt b/metadata/news/2015-08-26-ruby-19-removal/2015-08-26-ruby-19-removal.en.txt
deleted file mode 100644
index 97c2465f7004..000000000000
--- a/metadata/news/2015-08-26-ruby-19-removal/2015-08-26-ruby-19-removal.en.txt
+++ /dev/null
@@ -1,26 +0,0 @@
-Title: Ruby 1.9 removal; Ruby 2.0/2.1 default
-Author: Manuel Rüger <mrueg@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-08-26
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Installed: <dev-lang/ruby-2.0
-
-Ruby MRI 1.9 has been retired by upstream in February 2015.[1]
-We remove Ruby MRI 1.9 support from the tree now. In parallel Ruby MRI 2.1
-support will be activated in base profile's RUBY_TARGETS variable by default
-in conjunction with Ruby MRI 2.0.
-
-If your currently eselected Ruby interpreter is ruby19, our recommendation is
-to change it to ruby20. At the moment Ruby MRI 2.0 delivers the best possible
-support of all Ruby interpreters in tree.
-
-Check the current setting via:
-
- eselect ruby show
-
-Change the current setting to Ruby MRI 2.0 via:
-
- eselect ruby set ruby20
-
-[1] https://www.ruby-lang.org/en/news/2015/02/23/support-for-ruby-1-9-3-has-ended/
diff --git a/metadata/news/2015-09-09-libvirt-init-script-changes/2015-09-09-libvirt-init-script-changes.en.txt b/metadata/news/2015-09-09-libvirt-init-script-changes/2015-09-09-libvirt-init-script-changes.en.txt
deleted file mode 100644
index 83ed083c6ce1..000000000000
--- a/metadata/news/2015-09-09-libvirt-init-script-changes/2015-09-09-libvirt-init-script-changes.en.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-Title: libvirt-1.2.19 init script changes
-Author: Doug Goldstein <cardoe@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-09-09
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <app-emulation/libvirt-1.2.19
-
-OpenRC Users:
-
-In libvirt-1.2.19 and newer, the libvirtd init script has been split into
-libvirtd and libvirt-guests.
-
-The purpose of this change is to separate the management of the libvirtd
-daemon from the libvirt domains/guests. This means that a number of settings
-from /etc/conf.d/libvirtd have been moved to /etc/conf.d/libvirt-guests. These
-settings have not been auto-migrated and you are advised to review
-/etc/conf.d/libvirt-guests to ensure the behaviors are as you expect.
-
-You must add libvirt-guests to the same runlevel where you run libvirtd
-currently. Otherwise your domains/guests will not be gracefully shutdown and
-could result in data loss. To do this run the following commands:
- $ rc-update add libvirt-guests
- $ service libvirt-guests start
diff --git a/metadata/news/2015-10-07-openrc-0-18-localmount-and-netmount-changes/2015-10-07-openrc-0-18-localmount-and-netmount-changes.en.txt b/metadata/news/2015-10-07-openrc-0-18-localmount-and-netmount-changes/2015-10-07-openrc-0-18-localmount-and-netmount-changes.en.txt
deleted file mode 100644
index 7b2b688d7147..000000000000
--- a/metadata/news/2015-10-07-openrc-0-18-localmount-and-netmount-changes/2015-10-07-openrc-0-18-localmount-and-netmount-changes.en.txt
+++ /dev/null
@@ -1,17 +0,0 @@
-Title: OpenRC-0.18 localmount and netmount changes
-Author: William Hubbs <williamh@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-10-07
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <=sys-apps/openrc-0.18
-
-The behaviour of localmount and netmount is changing on Linux systems.
-In the past, these services always started successfully. However, now they
-will fail if a file system they attempt to mount cannot be mounted.
-
-If you have file systems listed in fstab which should not be mounted at
-boot time, make sure to add noauto to the mount options. If you have
-file systems that you want to attempt to mount at boot time but failure
-should be allowed, add nofail to the mount options for these file
-systems in fstab.
diff --git a/metadata/news/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt b/metadata/news/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt
deleted file mode 100644
index 3d5c76cba3d4..000000000000
--- a/metadata/news/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt
+++ /dev/null
@@ -1,62 +0,0 @@
-Title: Future Support of hardened-sources Kernel
-Author: Anthony G. Basile <blueness@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-10-21
-Revision: 3
-News-Item-Format: 1.0
-Display-If-Installed: sys-kernel/hardened-sources
-Display-If-Profile: hardened/linux/amd64
-Display-If-Profile: hardened/linux/amd64/no-multilib
-Display-If-Profile: hardened/linux/amd64/no-multilib/selinux
-Display-If-Profile: hardened/linux/amd64/selinux
-Display-If-Profile: hardened/linux/amd64/x32
-Display-If-Profile: hardened/linux/arm/armv6j
-Display-If-Profile: hardened/linux/arm/armv7a
-Display-If-Profile: hardened/linux/ia64
-Display-If-Profile: hardened/linux/musl/amd64
-Display-If-Profile: hardened/linux/musl/amd64/x32
-Display-If-Profile: hardened/linux/musl/arm/armv7a
-Display-If-Profile: hardened/linux/musl/mips
-Display-If-Profile: hardened/linux/musl/mips/mipsel
-Display-If-Profile: hardened/linux/musl/ppc
-Display-If-Profile: hardened/linux/musl/x86
-Display-If-Profile: hardened/linux/powerpc/ppc32
-Display-If-Profile: hardened/linux/powerpc/ppc64/32bit-userland
-Display-If-Profile: hardened/linux/powerpc/ppc64/64bit-userland
-Display-If-Profile: hardened/linux/uclibc/amd64
-Display-If-Profile: hardened/linux/uclibc/arm/armv7a
-Display-If-Profile: hardened/linux/uclibc/mips
-Display-If-Profile: hardened/linux/uclibc/mips/mipsel
-Display-If-Profile: hardened/linux/uclibc/ppc
-Display-If-Profile: hardened/linux/uclibc/x86
-Display-If-Profile: hardened/linux/x86
-Display-If-Profile: hardened/linux/x86/selinux
-
-For many years, the Grsecurity team [1] has been supporting two versions of
-their security patches against the Linux kernel, a stable and a testing
-version, and Gentoo has made both of these available to our users through the
-hardened-sources package. However, on August 26 of this year, the team
-announced they would no longer be making the stable version publicly
-available, citing trademark infringement by a major embedded systems company
-as the reason. [2] The stable patches are now only available to sponsors of
-Grsecurity and can no longer be distributed in Gentoo. However, the team did
-assure us that they would continue to release and support the testing version
-as they have in the past.
-
-What does this means for users of hardened-sources? Gentoo will continue to
-make the testing version available through our hardened-sources package but we
-will have to drop support for the 3.x series. In a few days, those ebuilds
-will be removed from the tree and you will be required to upgrade to a 4.x
-series kernel. Since the hardened-sources package only installs the kernel
-source tree, you can continue using a currently built 3.x series kernel but
-bear in mind that we cannot support you, nor will upstream. Also keep in mind
-that the 4.x series will not be as reliable as the 3.x series was, so
-reporting bugs promptly will be even more important. Gentoo will continue to
-work closely with upstream to stay on top of any problems, but be prepared for
-the occasional "bad" kernel. The more reporting we receive from our users,
-the better we will be able to decide which hardened-sources kernels to mark
-stable and which to drop.
-
-Refs.
-[1] https://grsecurity.net
-[2] https://grsecurity.net/announce.php
diff --git a/metadata/news/2015-12-16-python-abiflags-rebuild-needed/2015-12-16-python-abiflags-rebuild-needed.en.txt b/metadata/news/2015-12-16-python-abiflags-rebuild-needed/2015-12-16-python-abiflags-rebuild-needed.en.txt
deleted file mode 100644
index 7fa3adea7a79..000000000000
--- a/metadata/news/2015-12-16-python-abiflags-rebuild-needed/2015-12-16-python-abiflags-rebuild-needed.en.txt
+++ /dev/null
@@ -1,53 +0,0 @@
-Title: Python ABIFLAGS rebuild needed
-Author: Mike Gilbert <floppym@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-12-16
-Revision: 5
-News-Item-Format: 1.0
-Display-If-Installed: =dev-lang/python-3.3.5-r4
-Display-If-Installed: =dev-lang/python-3.3.5-r5
-Display-If-Installed: =dev-lang/python-3.3.5-r6
-Display-If-Installed: =dev-lang/python-3.3.5-r7
-Display-If-Installed: =dev-lang/python-3.3.5-r8
-Display-If-Installed: =dev-lang/python-3.3.5-r9
-Display-If-Installed: ~dev-lang/python-3.3.6
-Display-If-Installed: =dev-lang/python-3.4.3-r4
-Display-If-Installed: =dev-lang/python-3.4.3-r5
-Display-If-Installed: =dev-lang/python-3.4.3-r6
-Display-If-Installed: =dev-lang/python-3.4.3-r7
-Display-If-Installed: =dev-lang/python-3.4.3-r8
-Display-If-Installed: =dev-lang/python-3.4.3-r9
-Display-If-Installed: ~dev-lang/python-3.4.4
-Display-If-Installed: ~dev-lang/python-3.4.5
-Display-If-Installed: =dev-lang/python-3.5.0-r3
-Display-If-Installed: =dev-lang/python-3.5.0-r4
-Display-If-Installed: =dev-lang/python-3.5.0-r5
-Display-If-Installed: =dev-lang/python-3.5.0-r6
-Display-If-Installed: =dev-lang/python-3.5.0-r7
-Display-If-Installed: =dev-lang/python-3.5.0-r8
-Display-If-Installed: =dev-lang/python-3.5.0-r9
-Display-If-Installed: ~dev-lang/python-3.5.1
-Display-If-Installed: ~dev-lang/python-3.5.2
-
-For several years, Gentoo has been patching python3 in a way that is
-incompatible with PEP 3149 [1]. Gentoo has been enabling the PyMalloc feature,
-but our python packages have not carried the appropriate ABI flag.
-
-We have removed this patch from the most recent dev-lang/python ebuilds at
-the time of this writing. One result of this is that any packages which
-install python extension modules must be rebuilt.
-
-You may experience build failures in related packages until this rebuild has
-been completed.
-
-You can rebuild affected packages using the following commands.
-
-emerge -1v $(find /usr/lib*/python3* -name '*cpython-3[3-5].so')
-emerge -1v /usr/include/python3.{3,4,5}
-
-It is possible that these commands will do nothing (or display a syntax error)
-if all affected packages have already been rebuilt, causing the relevent files
-to no longer exist.
-
-References:
-[1] https://www.python.org/dev/peps/pep-3149/
diff --git a/metadata/news/2019-02-13-virtual-mysql-depenedency/2019-02-13-virtual-mysql-depenedency.en.txt b/metadata/news/2019-02-13-virtual-mysql-depenedency/2019-02-13-virtual-mysql-depenedency.en.txt
deleted file mode 100644
index 29258deef397..000000000000
--- a/metadata/news/2019-02-13-virtual-mysql-depenedency/2019-02-13-virtual-mysql-depenedency.en.txt
+++ /dev/null
@@ -1,19 +0,0 @@
-Title: MySQL server and library dependency shift
-Author: Brian Evans <grknight@gentoo.org>
-Posted: 2019-02-13
-Revision: 1
-News-Item-Format: 2.0
-Display-If-Installed: virtual/mysql
-
-Due to the complexity of supporting multiple client libraries,
-the Gentoo MySQL maintainers have decided to drop dependencies on the
-server installation where it is not absolutely necessary.
-
-This will mean that packages might not automatically install the server
-as a dependency since it does not have to exist on the local machine.
-
-To ensure uninterrupted service, verify that the server package,
-such as dev-db/mariadb, dev-db/mysql, etc, is included in the world file
-where it is in operation. This can be accomplished by running emerge
-with the --noreplace option.
-Eg.: emerge --noreplace dev-db/mariadb
diff --git a/metadata/news/2019-08-30-php-5_6-deprecation/2019-08-30-php-5_6-deprecation.en.txt b/metadata/news/2019-08-30-php-5_6-deprecation/2019-08-30-php-5_6-deprecation.en.txt
deleted file mode 100644
index 5e7218bfcfda..000000000000
--- a/metadata/news/2019-08-30-php-5_6-deprecation/2019-08-30-php-5_6-deprecation.en.txt
+++ /dev/null
@@ -1,69 +0,0 @@
-Title: Deprecation and removal of PHP 5.6
-Author: Brian Evans <grknight@gentoo.org>
-Posted: 2019-08-30
-Revision: 2
-News-Item-Format: 2.0
-Display-If-Installed: dev-lang/php:5.6
-Display-If-Installed: dev-php/haru
-Display-If-Installed: dev-php/magickwand
-Display-If-Installed: dev-php/pecl-bbcode
-Display-If-Installed: dev-php/pecl-cairo
-Display-If-Installed: dev-php/pecl-dbx
-Display-If-Installed: dev-php/pecl-htscanner
-Display-If-Installed: dev-php/pecl-libevent
-Display-If-Installed: dev-php/pecl-memcache
-Display-If-Installed: dev-php/pecl-mongo
-Display-If-Installed: dev-php/pecl-mysqlnd_ms
-Display-If-Installed: dev-php/pecl-mysqlnd_qc
-Display-If-Installed: dev-php/pecl-sphinx
-Display-If-Installed: dev-php/pecl-spl_types
-Display-If-Installed: dev-php/pecl-svn
-Display-If-Installed: dev-php/pecl-xrange
-Display-If-Installed: dev-php/suhosin
-Display-If-Installed: dev-php/xcache
-Display-If-Installed: dev-php/xhprof
-Display-If-Installed: dev-php/pecl-apcu:0
-Display-If-Installed: dev-php/pecl-dbase:0
-Display-If-Installed: dev-php/pecl-http:2
-Display-If-Installed: dev-php/pecl-mailparse:0
-Display-If-Installed: dev-php/pecl-memcached:0
-Display-If-Installed: dev-php/pecl-oauth:0
-Display-If-Installed: dev-php/pecl-propro:0
-Display-If-Installed: dev-php/pecl-ps:0
-Display-If-Installed: dev-php/pecl-raphf:0
-Display-If-Installed: dev-php/pecl-rrd:0
-Display-If-Installed: dev-php/pecl-ssh2:0
-Display-If-Installed: dev-php/pecl-stomp:0
-Display-If-Installed: dev-php/pecl-xdiff:0
-Display-If-Installed: dev-php/pecl-yaml:0
-Display-If-Installed: dev-php/twig[extension]
-Display-If-Installed: dev-php/PEAR-MDB2_Driver_mysql
-Display-If-Installed: media-gfx/exact-image[php]
-Display-If-Installed: sci-geosciences/mapserver[php,php_targets_php5-6]
-Display-If-Installed: www-apps/rutorrent:3.4-r1
-Display-If-Installed: www-server/nginx-unit[php56]
-
-The Gentoo PHP Team is announcing the deprecation and future removal of
-PHP 5.6. As of October 1, 2019, PHP 5.6 will be masked for removal.
-Since some may consider this a critical package, we have decided on a
-longer than normal 90 day removal period.
-
-Other distributions have already or will have moved to PHP 7.2 by the end of
-the year. Currently, we are using a backport repository to keep
-security updates in line with the main releases. However, we feel this
-is the right time to remove this branch as maintenance burden will
-likely only increase.
-
-To that end, the long list of PHP 5 only extensions must accompany its
-removal. Many of which are long ignored by their upstream maintainers
-and have no replacements. Some packages listed here have PHP 5 only
-slots which are included as reminders to upgrade.
-
-Some packages do have replacements:
-dev-php/pecl-memcache can be replaced by dev-php/pecl-memcached with
- some small code modifications
-dev-php/pecl-mongo has been superceded by dev-php/pecl-mongodb
-dev-php/pecl-libevent should be replaced by dev-php/pecl-event
- with code changes
-dev-php/PEAR-MDB2_Driver_mysql should be easily replaced by
- dev-php/PEAR-MDB2_Driver_mysqli with minor configuration changes
diff --git a/metadata/news/2020-12-26-most-stable-hppa-keywords-removed/2020-12-26-most-stable-hppa-keywords-removed.en.txt b/metadata/news/2020-12-26-most-stable-hppa-keywords-removed/2020-12-26-most-stable-hppa-keywords-removed.en.txt
new file mode 100644
index 000000000000..872464a00410
--- /dev/null
+++ b/metadata/news/2020-12-26-most-stable-hppa-keywords-removed/2020-12-26-most-stable-hppa-keywords-removed.en.txt
@@ -0,0 +1,15 @@
+Title: Most stable hppa keywords removed
+Author: Matt Turner <mattst88@gentoo.org>
+Posted: 2020-12-26
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Keyword: hppa
+
+The Gentoo/HPPA team no longer thinks that the time invested in
+package stabilization is warranted for the small number of users on
+HPPA. As a result, we will drop most "hppa" keywords to "~hppa" on
+2020-12-31. Around 850 packages will retain their stable keywords.
+
+Users need not make any changes to their systems—other than perhaps
+adding some entries to their package.accept_keywords file. The
+Gentoo/HPPA team has no plans to remove support for the architecture.
diff --git a/metadata/news/Manifest b/metadata/news/Manifest
index b1c57977367f..46214d5487e2 100644
--- a/metadata/news/Manifest
+++ b/metadata/news/Manifest
@@ -1,23 +1,23 @@
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
-MANIFEST Manifest.files.gz 12077 BLAKE2B 2f3ed2165704c3f21cd4304fe3c7b1c7220549685a7eaa2b3e7c032afad54f4636d2f0b3a9ec4d5d71d15b7b035403e2ef7a90326cff0da0eaf8ffd7e4fac1aa SHA512 f30fcba11723fbc57f0bea029403880a3ba6f50c0d547ae57a3947cb791df5cb0e16dcf31a4810562ece91b1fc646aa82b76a7ef6f7a60e3a0bdd95f0bc0a165
-TIMESTAMP 2020-12-25T22:38:29Z
+MANIFEST Manifest.files.gz 10052 BLAKE2B 99d1a5eb6e8f52a0c03138f80d6ee3214b6fd76a9d85b04118722787d85ffaff446fda6c2cb93a42edc2c2ffeddb59180b86c80ad1652b7b5009e846c8db48ce SHA512 83a8845c703dd8944efcbf6eabc4222f2cb51ef3d1dda9eebbed2536bb5e1e7fa86988cf6e5ac01d1d9918874a8c3b24e2059cd904c57b2f056b8c0fdee7820d
+TIMESTAMP 2021-01-01T20:38:39Z
-----BEGIN PGP SIGNATURE-----
-iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAl/maeVfFIAAAAAALgAo
+iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAl/viE9fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUx
RDZBQkI2M0JGQ0ZCNEJBMDJGREYxQ0VDNTkwRUVBQzkxODkyNTAACgkQ7FkO6skY
-klC40A//UuNv4i4ppuw8Tgr14IlAbOn14WnjFbzjRpel+W4V38VjjatxSExaxgcf
-GOIIqzSkToj7avoi9K6FOZknmPSGBX3TXE1MTKjEfff2pJ8mVa/kdzLamh/qUxa2
-YnIOXnh973NYGXs4J7mlRLc6OCHo4xjLkJshQ0tWXruVQx5I3tQdhFLU23SlgXgn
-iaFOwpbIB9ph7+zFDE5jbDYLCu1ogFaZxZguJ8eSDHMDsAIoWV8EKh2m4Dnv0HmC
-xu2D7dtwj3G3PzdnAqPUG/XxyQVAE1LBUTDO8qRIpMVFfeN4ICpVrlNczUcGzHQI
-ytNATtCFZBbNN2bR2rSYqbIEvh6SScBDv9H8J3bdC78FaLf/rogF6r/1I1nIkmKG
-lhpqWK5VrkZU+W0HhtgA3xbMWuTMKoI1kyH9ttFdQRc3r2mrtVFlkDX8ra87uezz
-GT8r12MIzkZLNlSBC5+7F1+qOoQVwaaZXfpwWbxAQFBFJB+jFD3H8YM/icK4zWld
-GnPukt3fi/E2PhJsGHxvvo0NZv9cQ5KKtaCKC/URuIONngWfFAbd0mKwISx+nHy0
-v+NnGvPFcKF+POJCbMiad1USh/qYdcOCck0B/gERPXJYpg5B9qyESPeR3NunZbZM
-x7HjkJYec1pHFH9cGiKNJBFXBSdILrEW/YrSOd+FvolbR4pom/c=
-=YOiC
+klAn7A/9F+LS8wW7Oiz4f9dopqiK+w2dqFefzBqlmvZFR2FXEM7CrCZhuIl8r50h
+DpliC6flFWCUUmTAhYNduMf7BySjb4aSqqg/cQvH9iV+9knY2Hg7xAgtC6P3bO23
+L5VfzZuObfkQnEs/6yoDuGJzexZNHAB1PzoiN1QQpgAiTM6PZvUwUsFvJz5HQSds
+F75R3u2/hrUEeWHuMSjYrGhRwDLRqsKOVUyw+dcV4nFgnCqSSAr83dLsLQy56kHz
+Bmb5UdgNtVwK96Q1ntS4wstUxYI1YLshsSBM5I/c1Tx/qiL5lOslhn4CsmoC79gU
+0/bHocsKNtLUTbfAexwmxXnXjoiV9Ivb/skvv+CKhtdCSdkYD92MXF1o04Jdw6sd
+RpUDlILm3kVlR84xQwnBeTLOKvAr5WrFqAnFOpFYYeCSSDIFhdMOHqgGxhaip3JE
+hpD7gLOoBIag/pKNzQ/u4dpjT7sf5QRRt1nee1NdPU7pmVbTUf/LxSASZ6SdLnon
+hcFdW6gHEzUpmlLbTGwxujldanMqJc/wfoZALWARxXT0l65lS77pNqRj0hMrPPqi
+ok7vPPxHIZvfFxMN6Yu84v/1ZVz5cGpY8Xg0XOoFQB1yueX3BjXYooGHSnY+8/Vx
+XWGhP/l0Nhh2B8JlwG4/SkjkD1ZrYkZz/uONq6A8PzW+GBFfhd4=
+=OCtm
-----END PGP SIGNATURE-----
diff --git a/metadata/news/Manifest.files.gz b/metadata/news/Manifest.files.gz
index b9ac2e92eaa6..555674a756d4 100644
--- a/metadata/news/Manifest.files.gz
+++ b/metadata/news/Manifest.files.gz
Binary files differ
diff --git a/metadata/news/README b/metadata/news/README
new file mode 100644
index 000000000000..63cbead22366
--- /dev/null
+++ b/metadata/news/README
@@ -0,0 +1,7 @@
+Copyright of Gentoo news items is held by their respective authors
+and translators.
+
+All news items committed after 2018-10-21 are licensed under the
+Creative Commons Attribution-ShareAlike 4.0 International License.
+Visit https://creativecommons.org/licenses/by-sa/4.0/ to view a copy
+of this license.
diff --git a/metadata/news/timestamp.chk b/metadata/news/timestamp.chk
index 698dafaf84e1..3f0759c50d70 100644
--- a/metadata/news/timestamp.chk
+++ b/metadata/news/timestamp.chk
@@ -1 +1 @@
-Fri, 25 Dec 2020 22:38:26 +0000
+Fri, 01 Jan 2021 20:38:36 +0000
diff --git a/metadata/news/timestamp.commit b/metadata/news/timestamp.commit
index 9ef05a3a4fd5..b97dba721917 100644
--- a/metadata/news/timestamp.commit
+++ b/metadata/news/timestamp.commit
@@ -1 +1 @@
-3055337f5458471b69abf209530d9ce13c7ede6c 1601998698 2020-10-06T15:38:18+00:00
+473b7ccfe355bb5572e3cecfd068c6121ed37b6f 1609463388 2021-01-01T01:09:48+00:00