[gentoo-commits] data/gentoo-news:master commit in: 2009-07-12-xorg-74-alpha/, 2011-12-30-bacula-updates/, 2011-08-28-mesa-r600g/, ...

[Ulrich Müller]

commit:     8c82e8e72bf9157172b8a153ac8927c9f06500fd
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Fri May 31 09:40:13 2019 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri May 31 09:40:13 2019 +0000
URL:        https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=8c82e8e7

Remove obsolete news items.

As announced:
https://archives.gentoo.org/gentoo-dev/message/ac6c9e00ca39253b092a38d1759c6fea

Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 .../2007-05-04-paludis-0_24.en.txt                 |  12 ---
 .../2009-01-04-sparc-multilib.en.txt               |  17 ---
 .../2009-04-06-x_server-1_5.en.txt                 |  15 ---
 .../2009-07-12-xorg-74-alpha.en.txt                |  24 -----
 .../2009-10-02-xorg-server-1-6-libxcb-1_4.en.txt   |  15 ---
 2009-10-08-gnome-226/2009-10-08-gnome-226.en.txt   |  19 ----
 .../2009-10-22-default-linux.en.txt                |  29 ------
 .../2010-01-31-eselect-opengl.en.txt               |  16 ---
 .../2010-02-21-mysql-upgrade.en.txt                |  25 -----
 .../2010-02-28-layman-storage-path-change.en.txt   |  41 --------
 .../2010-03-01-mythtv-upgrade.en.txt               |  35 -------
 .../2010-03-23-new-subprofiles.en.txt              |  31 ------
 2010-03-25-python-3_1/2010-03-25-python-3_1.en.txt |  28 -----
 2010-05-02-gnome-228/2010-05-02-gnome-228.en.txt   |  18 ----
 .../2010-10-22-perl-5_12-upgrade-procedure.en.txt  |  27 -----
 .../2010-10-27-hardened-gcc4-info.en.txt           |  20 ----
 .../2010-11-13-hardened-profiles.en.txt            |  51 ---------
 .../2011-02-13-libgphoto2-2_4_10.en.txt            |  14 ---
 2011-02-14-gnome-232/2011-02-14-gnome-232.en.txt   |  17 ---
 .../2011-02-19-ia64-java-removal.en.txt            |  19 ----
 .../2011-04-26-gnustep-new-layout.en.txt           |  20 ----
 2011-04-27-glib-228/2011-04-27-glib-228.en.txt     |  37 -------
 .../2011-05-01-baselayout-update.en.txt            |  29 ------
 2011-08-28-mesa-r600g/2011-08-28-mesa-r600g.en.txt |  26 -----
 2011-10-15-libpng15/2011-10-15-libpng15.en.txt     |  32 ------
 .../2011-11-27-gnome3-unmask.en.txt                |  16 ---
 .../2011-12-06-kde473-kdepim.en.txt                |  29 ------
 .../2011-12-30-bacula-updates.en.txt               |  27 -----
 .../2012-02-14-baselayout-1-deprecation.en.txt     |  30 ------
 .../2012-04-24-libjpeg-turbo-by-default.en.txt     |  19 ----
 .../2012-07-23-upgrading-postfix.en.txt            |  13 ---
 .../2013-02-10-new-13-profiles-server.en.txt       |  41 --------
 .../2013-02-10-new-13-profiles.en.txt              | 116 ---------------------
 .../2013-03-29-udev-upgrade.en.txt                 | 102 ------------------
 ...0-baselayout-1-deprecation-final-warning.en.txt |  32 ------
 .../2013-06-01-mysql-pbxt-dropped.en.txt           |  41 --------
 2013-06-30-cups16/2013-06-30-cups16.en.txt         |  21 ----
 ...8-07-vanilla-sources-stablization-policy.en.txt |  26 -----
 .../2013-09-22-minor-arches-1.en.txt               |  28 -----
 .../2013-09-27-initramfs-required.en.txt           |  29 ------
 .../2013-10-14-grub2-migration.en.txt              |  31 ------
 .../2013-10-24-minor-arches-2.en.txt               |  23 ----
 .../2013-11-07-python-exec-package-move.en.txt     |  46 --------
 2013-11-23-gnome-38/2013-11-23-gnome-38.en.txt     |  23 ----
 44 files changed, 1310 deletions(-)

diff --git a/2007-05-04-paludis-0_24/2007-05-04-paludis-0_24.en.txt b/2007-05-04-paludis-0_24/2007-05-04-paludis-0_24.en.txt
deleted file mode 100644
index d66e774..0000000
--- a/2007-05-04-paludis-0_24/2007-05-04-paludis-0_24.en.txt
+++ /dev/null
@@ -1,12 +0,0 @@
-Title: Changes for Paludis 0.24
-Author: Piotr Jaroszyński <peper@g.o>
-Content-Type: text/plain
-Posted: 2007-05-04
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Installed: <sys-apps/paludis-0.30
-
-As of Paludis 0.24, the use of '*' to match all packages in the Paludis
-configuration files 'use.conf', 'keywords.conf' and 'licenses.conf' is
-deprecated in favour of '*/*'. You should update your configuration
-files after upgrading.

diff --git a/2009-01-04-sparc-multilib/2009-01-04-sparc-multilib.en.txt b/2009-01-04-sparc-multilib/2009-01-04-sparc-multilib.en.txt
deleted file mode 100644
index f3e9bf3..0000000
--- a/2009-01-04-sparc-multilib/2009-01-04-sparc-multilib.en.txt
+++ /dev/null
@@ -1,17 +0,0 @@
-Title: Migrating to the new sparc multilib profile
-Author: Friedrich Oslage <bluebird@g.o>
-Content-Type: text/plain
-Posted: 2009-01-04
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Profile: default/linux/sparc/experimental/multilib
-Display-If-Profile: default/linux/sparc/experimental/multilib/desktop
-Display-If-Profile: default/linux/sparc/experimental/multilib/developer
-Display-If-Profile: default/linux/sparc/experimental/multilib/server
-
-When migrating to the new sparc multilib profile please keep in mind that it is
-still in an experimental state. Also note that you need to follow the migration
-guide [0], otherwise important packages such as gcc or glibc will fail to
-compile and most other packages will be installed incorrectly.
-
-[0] http://sparc.gentoo.org/multilib.xml

diff --git a/2009-04-06-x_server-1_5/2009-04-06-x_server-1_5.en.txt b/2009-04-06-x_server-1_5/2009-04-06-x_server-1_5.en.txt
deleted file mode 100644
index c92df98..0000000
--- a/2009-04-06-x_server-1_5/2009-04-06-x_server-1_5.en.txt
+++ /dev/null
@@ -1,15 +0,0 @@
-Title: Migration to X.org Server 1.5
-Author: Remi Cardona <remi@g.o>
-Author: Christian Faulhammer <fauli@g.o>
-Content-Type: text/plain
-Posted: 2009-04-06
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <x11-base/xorg-server-1.5
-
-A lot of changes regarding device recognition and use by the X server
-have been introduced in the 1.5 update.  As that version is going
-stable on all architectures, users should read the upgrade guide [0]
-before actually updating the package.
-
-[0] http://www.gentoo.org/proj/en/desktop/x/x11/xorg-server-1.5-upgrade-guide.xml

diff --git a/2009-07-12-xorg-74-alpha/2009-07-12-xorg-74-alpha.en.txt b/2009-07-12-xorg-74-alpha/2009-07-12-xorg-74-alpha.en.txt
deleted file mode 100644
index a275ec1..0000000
--- a/2009-07-12-xorg-74-alpha/2009-07-12-xorg-74-alpha.en.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-Title: xorg-x11-7.4 and xorg-server-1.5 kernel support
-Author: Tobias Klausmann <klausman@g.o>
-Content-Type: text/plain
-Posted: 2009-07-12
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: x11-base/xorg-server
-Display-If-Profile: default-linux/alpha
-Display-If-Profile: default/linux/alpha
-
-Recent versions of xorg's X11 require kernel support to access PCI and AGP
-graphic cards. This support has only recently been added to the Linux kernel
-(sys-kernel/vanilla-sources-2.6.30 and sys-kernel/gentoo-sources-2.6.29-r5).
-Thus, you will need to run a recent enough kernel to use recent versions of X11
-on an alpha. If you only start programs on your alpha, but the display is on
-another machine, no upgrade is necessary.
-
-Furthermore, not all graphics card drivers have been updated to work with the
-newer X server API. One example is the glint driver used for Permedia cards. The
-upstream developers have been informed about this, but no fixes are available
-yet, please see https://bugs.freedesktop.org/show_bug.cgi?id=21546
-
-For a general guide to upgrading to Xorg 1.5, see the Gentoo upgrade guide:
-http://www.gentoo.org/proj/en/desktop/x/x11/xorg-server-1.5-upgrade-guide.xml

diff --git a/2009-10-02-xorg-server-1-6-libxcb-1_4/2009-10-02-xorg-server-1-6-libxcb-1_4.en.txt b/2009-10-02-xorg-server-1-6-libxcb-1_4/2009-10-02-xorg-server-1-6-libxcb-1_4.en.txt
deleted file mode 100644
index 886f7f9..0000000
--- a/2009-10-02-xorg-server-1-6-libxcb-1_4/2009-10-02-xorg-server-1-6-libxcb-1_4.en.txt
+++ /dev/null
@@ -1,15 +0,0 @@
-Title: Migration to X.org Server 1.6 and libxcb 1.4
-Author: Remi Cardona <remi@g.o>
-Content-Type: text/plain
-Posted: 2009-10-02
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <x11-base/xorg-server-1.6
-Display-If-Installed: <x11-libs/libxcb-1.4
-
-We're pleased to announce the stabilization of xorg-server-1.6. Users
-are strongly encouraged to read the following two guides before
-upgrading:
-
-http://www.gentoo.org/proj/en/desktop/x/x11/xorg-server-1.6-upgrade-guide.xml
-http://www.gentoo.org/proj/en/desktop/x/x11/libxcb-1.4-upgrade-guide.xml 

diff --git a/2009-10-08-gnome-226/2009-10-08-gnome-226.en.txt b/2009-10-08-gnome-226/2009-10-08-gnome-226.en.txt
deleted file mode 100644
index 065e675..0000000
--- a/2009-10-08-gnome-226/2009-10-08-gnome-226.en.txt
+++ /dev/null
@@ -1,19 +0,0 @@
-Title: Upgrade to GNOME 2.26
-Author: Mart Raudsepp <leio@g.o>
-Content-Type: text/plain
-Posted: 2009-10-08
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <gnome-base/gnome-2.26.0
-Display-If-Installed: <gnome-base/gnome-light-2.26.0
-Display-If-Installed: <gnome-base/gnome-session-2.26.2
-Display-If-Installed: <gnome-base/gnome-menus-2.26.2
-
-We are pleased to announce the stabilization of GNOME-2.26. Users are
-strongly encouraged to read the GNOME 2.26 Upgrade Guide, to avoid any
-possible issues relating to the upgrade, such as Applications menu items
-disappearing, or nautilus constantly restarting when it is configured to
-not handle the desktop.
-
-Please read the Gnome 2.26 Upgrade Guide:
-http://gnome.gentoo.org/howtos/gnome-2.26-upgrade.xml

diff --git a/2009-10-22-default-linux/2009-10-22-default-linux.en.txt b/2009-10-22-default-linux/2009-10-22-default-linux.en.txt
deleted file mode 100644
index 88ca0e0..0000000
--- a/2009-10-22-default-linux/2009-10-22-default-linux.en.txt
+++ /dev/null
@@ -1,29 +0,0 @@
-Title: Using default-linux profile is now obsolete
-Author: Samuli Suominen <ssuominen@g.o>
-Content-Type: text/plain
-Posted: 2009-10-22
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Profile: default-linux/alpha
-Display-If-Profile: default-linux/amd64
-Display-If-Profile: default-linux/arm
-Display-If-Profile: default-linux/ia64
-Display-If-Profile: default-linux/m68k
-Display-If-Profile: default-linux/s390
-Display-If-Profile: default-linux/sh
-Display-If-Profile: default-linux/sparc
-Display-If-Profile: default-linux/x86
-
-The profiles in default-linux/ have been deprecated for six weeks.
-Users using these profiles are expected to migrate to a new profile
-before 2009-12-01, at which point the default-linux/ profiles will be
-removed.  The new profiles contain up to date configurations and were
-adopted because they were easier to maintain.  Users can switch to a
-new profile using eselect:
-
-# eselect profile list
-# eselect profile set <target>
-
-If a machine is not migrated to a new valid profile before the deprecated 
-profiles are removed, emerge will have very limited functionality until 
-the migration is done.

diff --git a/2010-01-31-eselect-opengl/2010-01-31-eselect-opengl.en.txt b/2010-01-31-eselect-opengl/2010-01-31-eselect-opengl.en.txt
deleted file mode 100644
index 469d62a..0000000
--- a/2010-01-31-eselect-opengl/2010-01-31-eselect-opengl.en.txt
+++ /dev/null
@@ -1,16 +0,0 @@
-Title: Removal of libGL.la
-Author: Tomáš Chvátal <scarabeus@g.o>
-Content-Type: text/plain
-Posted: 2010-01-31
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <app-admin/eselect-opengl-1.1.1-r2
-
-Eselect-opengl package now strips the libGL.la file. This file was broken and
-thus we proceeded with its removal. It brings slight inconvenience on you fellow
-users. After emerging the new version =app-admin/eselect-opengl-1.1.1-r2 please
-emerge one more package dev-util/lafilefixer and use it for fixing all various
-compilation issues by running as root:
-# lafilefixer --justfixit
-Note that not-running this command will bring you compilation issues so you
-should really pay attention to this message and act upon it.

diff --git a/2010-02-21-mysql-upgrade/2010-02-21-mysql-upgrade.en.txt b/2010-02-21-mysql-upgrade/2010-02-21-mysql-upgrade.en.txt
deleted file mode 100644
index 493bab4..0000000
--- a/2010-02-21-mysql-upgrade/2010-02-21-mysql-upgrade.en.txt
+++ /dev/null
@@ -1,25 +0,0 @@
-Title: MySQL 5.1 unmasking and upgrade procedures
-Author: Robin H. Johnson <robbat2@g.o>
-Content-Type: text/plain
-Posted: 2010-02-21
-Revision: 5
-News-Item-Format: 1.0
-Display-If-Installed: <dev-db/mysql-5.1
-
-The 5.1 series of MySQL is going to be unmasked at the same time as the release
-of this news item. When upgrading from an older major version (including 5.0),
-you will be required to rebuild everything linked to the libmysqlclient.so.15
-and libmysqlclient_r.so.15.
-
-You can do this by installing app-portage/gentoolkit and running:
-# revdep-rebuild --library libmysqlclient.so.15
-# revdep-rebuild --library libmysqlclient_r.so.15
-
-If you use the Portage 2.2 series, you may also use:
-# emerge @preserved-rebuild
-
-The official upgrade documentation is available here:
-http://dev.mysql.com/doc/refman/5.1/en/upgrading.html
-
-Note that existing databases may need converting as well, again including those
-upgrading from 5.0 to 5.1. Details are in the update documentation.

diff --git a/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt b/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt
deleted file mode 100644
index 5726373..0000000
--- a/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt
+++ /dev/null
@@ -1,41 +0,0 @@
-Title: Layman storage path changed from version 1.3.0 on
-Author: Sebastian Pipping <sping@g.o>
-Content-Type: text/plain
-Posted: 2010-02-28
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Installed: <app-portage/layman-1.3
-
-Layman has been using /usr/local/portage/layman to store
-overlay checkouts from version 1.2.3 on.  As that path
-was violating the concept of keeping portage away from
-/usr/local the default of this storage location moves to
-
-  /var/lib/layman
-
-from version 1.3.0 on.  If you have never touched the file
-/etc/layman/layman.cfg manually before, you may be tempted to let
-tools like etc-update or dispatch-conf blindly accept this new version
-of layman.cfg.
-
-As that would hide all your currently installed overlays from layman
-it's probably not what you want.  Your options are:
-
- A) Moving
-   1. Move your current content to /var/lib/layman.
-   2. Update PORTDIR_OVERLAY in /var/lib/layman/make.conf accordingly.
-   3. Make /etc/make.conf source /var/lib/layman/make.conf.
-   4. Set option "storage" in /etc/layman/layman.cfg
-      to "/var/lib/layman".
-
- B) A symlink
-   Put a symlink to your current storage location at /var/lib/layman
-   before upgrading layman.
-
- C) Configuration
-   Reject the path change for layman.cfg when running tools like
-   etc-update or dispatch-conf.  Be aware with this way you'll have
-   to do it for each layman update again.
-
-PS: This news item is a reaction to users having run into this problem
-(see bug #306233).  Thanks to Volker Hemmann for reporting.

diff --git a/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt b/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt
deleted file mode 100644
index 71bf128..0000000
--- a/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt
+++ /dev/null
@@ -1,35 +0,0 @@
-Title: MythTV 0.22 Upgrade Database Corruption
-Author: Richard Freeman <rich0@g.o>
-Content-Type: text/plain
-Posted: 2010-03-01
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <media-tv/mythtv-0.22
-
-Due to an incompatibility between MythTV 0.21 and the default Gentoo
-MySQL configuration, it is likely that long-time MythTV users will
-have databases with a mixture of locale encodings.  If you upgrade to
-0.22 without following these directions carefully, you could end up
-with a database that contains errors that are extremely difficult to
-fix.
-
-Note that not all mythtv users need to modify their databases, and
-this should only be performed at the time of the upgrade.  The guide
-below contains instructions that can be used to determine if this
-problem pertains to you.
-
-Please see the MythTV Upgrade Guide for instructions:
-
-   http://wiki.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding
-
-Be sure to save a database backup using mysqldump before upgrading.  
-Also, be sure to upgrade any other clients/backends you are using to
-0.22 at the same time.  The upgrade instructions need to be followed 
-once per database - individual client/backend upgrades do not require 
-these steps.
-
-If you do run into problems with your upgrade, there is a forum thread
-where you may be able to find help:
-
-   http://forums.gentoo.org/viewtopic-t-816566-highlight-.html
-

diff --git a/2010-03-23-new-subprofiles/2010-03-23-new-subprofiles.en.txt b/2010-03-23-new-subprofiles/2010-03-23-new-subprofiles.en.txt
deleted file mode 100644
index 550c33d..0000000
--- a/2010-03-23-new-subprofiles/2010-03-23-new-subprofiles.en.txt
+++ /dev/null
@@ -1,31 +0,0 @@
-Title: New desktop subprofiles for GNOME and KDE
-Author: Theo Chatzimichos <tampakrap@g.o>
-Content-Type: text/plain
-Posted: 2010-03-23
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Profile: default/linux/alpha/10.0/desktop
-Display-If-Profile: default/linux/amd64/10.0/desktop
-Display-If-Profile: default/linux/arm/10.0/desktop
-Display-If-Profile: default/linux/hppa/10.0/desktop
-Display-If-Profile: default/linux/ia64/10.0/desktop
-Display-If-Profile: default/linux/m68k/10.0/desktop
-Display-If-Profile: default/linux/powerpc/ppc32/10.0/desktop
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/32bit-userland/desktop
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/64bit-userland/desktop
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/desktop
-Display-If-Profile: default/linux/sh/10.0/desktop
-Display-If-Profile: default/linux/sparc/10.0/desktop
-Display-If-Profile: default/linux/sparc/experimental/multilib/desktop
-Display-If-Profile: default/linux/x86/10.0/desktop
-
-There are two new subprofiles under desktop, one for GNOME and one for
-KDE. Users that have only one of those two DEs may choose the according
-subprofile. Users of other DEs or WMs may stick to the desktop profile.
-
-Attention: KDE or GNOME specific USE flags have been stripped from the
-desktop profile. More specifically:
-GNOME subprofile contains: USE="eds evo gnome gstreamer"
-KDE subprofile contains: USE="kde"
-
-(I'll commit the change on Friday, 26 Mar 2010)

diff --git a/2010-03-25-python-3_1/2010-03-25-python-3_1.en.txt b/2010-03-25-python-3_1/2010-03-25-python-3_1.en.txt
deleted file mode 100644
index 13533ec..0000000
--- a/2010-03-25-python-3_1/2010-03-25-python-3_1.en.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-Title: Python 3.1
-Author: Arfrever Frehtes Taifersar Arahesis <Arfrever@g.o>
-Content-Type: text/plain
-Posted: 2010-03-25
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: =dev-lang/python-3.1*
-
-Python 3 is a new major version of Python and is intentionally incompatible
-with Python 2. Many external modules have not been ported yet to Python 3,
-so Python 2 still needs to be installed. You can benefit from having Python 3
-installed without setting Python 3.1 as main active version of Python.
-Currently you should not set Python 3.1 as main active version of Python.
-When setting it becomes recommended, a separate news item will be created
-to notify users.
-
-Although Python 3.1 should not be set as main active version of Python,
-you should run python-updater after installation of Python 3.1. By default,
-modules that support both Python 2 and Python 3 are installed for both
-the active version of Python 2 and the active version of Python 3 when both
-Python 2 and Python 3 are installed.
-
-It is recommended to use a UTF-8 locale to avoid potential problems. Especially
-C and POSIX locales are discouraged. If locale has not been explicitly set,
-then POSIX locale is used, so you should ensure that locale has been set.
-Problems occurring only with non-UTF-8 locales should be reported directly
-to upstream developers of given packages.
-See http://www.gentoo.org/doc/en/utf-8.xml for more information about UTF-8.

diff --git a/2010-05-02-gnome-228/2010-05-02-gnome-228.en.txt b/2010-05-02-gnome-228/2010-05-02-gnome-228.en.txt
deleted file mode 100644
index 177e160..0000000
--- a/2010-05-02-gnome-228/2010-05-02-gnome-228.en.txt
+++ /dev/null
@@ -1,18 +0,0 @@
-Title: Upgrade to GNOME 2.28
-Author: Pacho Ramos <pacho@g.o>
-Content-Type: text/plain
-Posted: 2010-04-23
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <gnome-base/gnome-2.28.2
-Display-If-Installed: <gnome-base/gnome-light-2.28.1
-Display-If-Installed: <gnome-base/gnome-session-2.28.0
-Display-If-Installed: <gnome-base/gnome-menus-2.28.0.1
-
-We are pleased to announce the stabilization of GNOME-2.28. Users are
-strongly encouraged to read the GNOME 2.28 Upgrade Guide, to avoid any
-possible issues relating to the upgrade, such as Applications menu items
-disappearing, missing icons, or mouse interaction problems.
-
-Please read the Gnome 2.28 Upgrade Guide:
-http://gnome.gentoo.org/howtos/gnome-2.28-upgrade.xml

diff --git a/2010-10-22-perl-5_12-upgrade-procedure/2010-10-22-perl-5_12-upgrade-procedure.en.txt b/2010-10-22-perl-5_12-upgrade-procedure/2010-10-22-perl-5_12-upgrade-procedure.en.txt
deleted file mode 100644
index 0be2ab3..0000000
--- a/2010-10-22-perl-5_12-upgrade-procedure/2010-10-22-perl-5_12-upgrade-procedure.en.txt
+++ /dev/null
@@ -1,27 +0,0 @@
-Title: Perl 5.12 upgrade procedure
-Author: perl-team <perl@g.o>
-Author: Torsten Veller <tove@g.o>
-Content-Type: text/plain
-Posted: 2010-10-22
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <dev-lang/perl-5.12
-
-==> Run `perl-cleaner --all` after upgrading to a new Perl version! <==
-
-"Perl 5.12 is not binary compatible with prior releases of Perl. If
-you have built extensions (i.e. modules that include C code) using an
-earlier version of Perl, you will need to rebuild and reinstall those
-extensions." [1]
-
-In fact, in Gentoo you currently have to rebuild all Perl modules and
-all binaries linking libperl to get into a consistent state again.
-
-perl-cleaner generates a list of broken packages and passes it to your
-package manager to reinstall them. After reinstalling the packages,
-perl-cleaner outputs a list of files the script could not deal with
-(like modules installed not via the package manager).
-
-See `man perl-cleaner` for its options.
-
-[1] http://search.cpan.org/dist/perl-5.12.2/INSTALL#Changes_and_Incompatibilities

diff --git a/2010-10-27-hardened-gcc4-info/2010-10-27-hardened-gcc4-info.en.txt b/2010-10-27-hardened-gcc4-info/2010-10-27-hardened-gcc4-info.en.txt
deleted file mode 100644
index 6ca9522..0000000
--- a/2010-10-27-hardened-gcc4-info/2010-10-27-hardened-gcc4-info.en.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-Title: Info about GCC on Hardened profiles
-Author: Magnus Granberg <zorry@g.o>
-Content-Type: text/plain
-Posted: 2010-10-27
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <sys-devel/gcc-4.4
-Display-If-Profile: hardened/linux
-
-GCC 4.4.4-r2 is now stable in the hardened profiles (on x86 and
-amd64 as of 2010-10-24, other architectures will follow later).
-Starting from this version, SSP support is enabled by default for the
-architectures it is supported on (namely x86, amd64, ppc, ppc64 and
-arm). Previously, GCC 4.3.4 had SSP support but it was not enabled
-by default.
-
-Older GCC versions in the hardened profiles, such as the
-GCC 3.x series will be obsoleted, problems arising on those versions,
-but not applying to GCC 4.4.4-r2 will not be fixed, so please update
-to the new version.

diff --git a/2010-11-13-hardened-profiles/2010-11-13-hardened-profiles.en.txt b/2010-11-13-hardened-profiles/2010-11-13-hardened-profiles.en.txt
deleted file mode 100644
index 98c7378..0000000
--- a/2010-11-13-hardened-profiles/2010-11-13-hardened-profiles.en.txt
+++ /dev/null
@@ -1,51 +0,0 @@
-Title: Restructuring of Hardened profiles
-Author: Anthony G. Basile <blueness@g.o>
-Author: Hardened Team <hardened@g.o>
-Content-Type: text/plain
-Posted: 2010-11-13
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Profile: hardened/linux/ia64/10.0
-Display-If-Profile: hardened/linux/ia64/10.0/server
-Display-If-Profile: hardened/linux/ia64/10.0/desktop
-Display-If-Profile: hardened/linux/ia64/10.0/developer
-Display-If-Profile: hardened/linux/x86/10.0
-Display-If-Profile: hardened/linux/x86/10.0/server
-Display-If-Profile: hardened/linux/x86/10.0/no-nptl
-Display-If-Profile: hardened/linux/x86/10.0/desktop
-Display-If-Profile: hardened/linux/x86/10.0/developer
-Display-If-Profile: hardened/linux/amd64/10.0
-Display-If-Profile: hardened/linux/amd64/10.0/server
-Display-If-Profile: hardened/linux/amd64/10.0/desktop
-Display-If-Profile: hardened/linux/amd64/10.0/no-multilib
-Display-If-Profile: hardened/linux/amd64/10.0/developer
-Display-If-Profile: hardened/linux/powerpc/ppc32/10.0
-Display-If-Profile: hardened/linux/powerpc/ppc32/10.0/server
-Display-If-Profile: hardened/linux/powerpc/ppc32/10.0/desktop
-Display-If-Profile: hardened/linux/powerpc/ppc32/10.0/developer
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/server
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/desktop
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/32bit-userland
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/32bit-userland/server
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/32bit-userland/desktop
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/32bit-userland/developer
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/64bit-userland
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/64bit-userland/server
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/64bit-userland/desktop
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/64bit-userland/developer
-Display-If-Profile: hardened/linux/powerpc/ppc64/10.0/developer
-
-During the next few weeks, all hardened profiles will be restructured to
-remove the version number "/10.0".  For example, if your current profile
-is "hardened/linux/amd64/10.0/no-multilib" your new profile will be
-"hardened/linux/amd64/no-multilib".
-
-We will change the profiles one arch at a time, starting with ia64, and
-proceeding in order with ppc, ppc64, x86 and amd64.  Once your arch has
-been  updated, you will receive a warning when running emerge that your
-profile has been deprecated.  When you do, use "eselect profile list" to
-get a list of the new profiles.  Then, use "eselect profile set <num>"
-to switch to your new profile with corresponding number <num>.
-
-Progress with the restructuring will be tracked in bug #344861.

diff --git a/2011-02-13-libgphoto2-2_4_10/2011-02-13-libgphoto2-2_4_10.en.txt b/2011-02-13-libgphoto2-2_4_10/2011-02-13-libgphoto2-2_4_10.en.txt
deleted file mode 100644
index d599f3a..0000000
--- a/2011-02-13-libgphoto2-2_4_10/2011-02-13-libgphoto2-2_4_10.en.txt
+++ /dev/null
@@ -1,14 +0,0 @@
-Title: Change on CAMERAS in libgphoto2-2.4.10
-Author: Pacho Ramos <pacho@g.o>
-Content-Type: text/plain
-Posted: 2011-02-13
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Installed: <media-libs/libgphoto2-2.4.10
-
-In order to not violate package manager handling, selective cameras 
-build logic has been modified in libgphoto2-2.4.10 to build 'ptp2' by 
-default, nothing if CAMERAS variable is set to an empty value and only 
-the ones specified otherwise.
-
-See http://bugs.gentoo.org/346491 for reference.

diff --git a/2011-02-14-gnome-232/2011-02-14-gnome-232.en.txt b/2011-02-14-gnome-232/2011-02-14-gnome-232.en.txt
deleted file mode 100644
index 47c1216..0000000
--- a/2011-02-14-gnome-232/2011-02-14-gnome-232.en.txt
+++ /dev/null
@@ -1,17 +0,0 @@
-Title: Upgrade to GNOME 2.32
-Author: Pacho Ramos <pacho@g.o>
-Content-Type: text/plain
-Posted: 2011-02-14
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <gnome-base/gnome-2.32.1
-Display-If-Installed: <gnome-base/gnome-light-2.32.1
-Display-If-Installed: <gnome-base/gnome-session-2.32.1
-
-We are pleased to announce the stabilization of GNOME-2.32. Users are
-strongly encouraged to read the GNOME 2.32 Upgrade Guide, to avoid any
-possible issues relating to the upgrade, such as gnome-panel hanging 
-issues, evolution migration problems and others.
-
-Please read the Gnome 2.32 Upgrade Guide:
-http://gnome.gentoo.org/howtos/gnome-2.32-upgrade.xml

diff --git a/2011-02-19-ia64-java-removal/2011-02-19-ia64-java-removal.en.txt b/2011-02-19-ia64-java-removal/2011-02-19-ia64-java-removal.en.txt
deleted file mode 100644
index eb45778..0000000
--- a/2011-02-19-ia64-java-removal/2011-02-19-ia64-java-removal.en.txt
+++ /dev/null
@@ -1,19 +0,0 @@
-Title: Pending Removal of Java support on IA64
-Author: Petteri Räty <betelgeuse@g.o>
-Author: IA64 Arch Team <ia64@g.o>
-Author: Vlastimil Babka <caster@g.o>
-Content-Type: text/plain
-Posted: 2011-02-19
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Keyword: ia64
-Display-If-Installed: dev-java/java-config
-
-Since the IA64 arch team does not have the resources to maintain Java support,
-we have agreed that ia64 keywords will be dropped from Java packages, and the 
-java USE flag masked on IA64, unless more manpower becomes available.
-If you are willing to help with the maintenance, please contact ia64@g.o.
-If there is not enough interest, Java support will be removed during the second
-half of March 2011.
-
-The removal is tracked in bug #345433.

diff --git a/2011-04-26-gnustep-new-layout/2011-04-26-gnustep-new-layout.en.txt b/2011-04-26-gnustep-new-layout/2011-04-26-gnustep-new-layout.en.txt
deleted file mode 100644
index ca24ef6..0000000
--- a/2011-04-26-gnustep-new-layout/2011-04-26-gnustep-new-layout.en.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-Title: GNUstep packages new layout
-Author: Bernard Cafarelli <voyageur@g.o>
-Content-Type: text/plain
-Posted: 2011-04-26
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <gnustep-base/gnustep-make-2.6.0
-
-Traditionally, GNUstep used its own filesystem layout, installing
-everything under /usr/GNUstep. Starting with gnustep-make-2.6.0, the
-default filesystem layout has changed and is now the 'fhs' layout,
-installing files in standard Unix directories.
-
-Following upstream's change, GNUstep packages in Gentoo will now
-also use the new default layout. Your system will switch to it
-after updating gnustep-base/gnustep-make to >=2.6.0.
-
-This change means that you have to re-emerge all installed packages
-depending on GNUstep to move them to the new layout. You can use
-gnustep-base/gnustep-updater for this step

diff --git a/2011-04-27-glib-228/2011-04-27-glib-228.en.txt b/2011-04-27-glib-228/2011-04-27-glib-228.en.txt
deleted file mode 100644
index 823413d..0000000
--- a/2011-04-27-glib-228/2011-04-27-glib-228.en.txt
+++ /dev/null
@@ -1,37 +0,0 @@
-Title: Upgrade to GLIB 2.28
-Author: The Gentoo Freedesktop Maintainers <freedesktop-bugs@g.o>
-Content-Type: text/plain
-Posted: 2011-04-27
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <dev-libs/glib-2.28
-
-The method for setting default applications for specific URI types
-(https://, mailto://, etc.) changed in dev-libs/glib-2.28 and newer.
-If you previously set them in GConf using the Configuration Editor,
-they will now be ignored.
-
-If you use GNOME, you must upgrade gnome-session and
-gnome-control-center and set your default browser/mail-client again.
-
-If you don't use GNOME, you should ensure that the file
-~/.local/share/applications/mimeapps.list has the following content:
-
-[Added Associations]
-x-scheme-handler/http=$browser_name.desktop;
-x-scheme-handler/https=$browser_name.desktop;
-x-scheme-handler/mailto=$mailclient_name.desktop;
-
-Replace $browser_name.desktop and $mailclient_name.desktop with the
-appropriate file from /usr/share/applications that can handle
-http/https/mailto URIs.
-
-The system-wide version of the file is often at
-/usr/share/applications/defaults.list instead.
-
-Please make sure that your browsers and mail clients have been upgraded
-to the latest stable versions before doing all this.
-
-More information about using defaults.list and mimeapps.list is at:
-
-http://www.freedesktop.org/wiki/Specifications/mime-actions-spec

diff --git a/2011-05-01-baselayout-update/2011-05-01-baselayout-update.en.txt b/2011-05-01-baselayout-update/2011-05-01-baselayout-update.en.txt
deleted file mode 100644
index d4b7689..0000000
--- a/2011-05-01-baselayout-update/2011-05-01-baselayout-update.en.txt
+++ /dev/null
@@ -1,29 +0,0 @@
-Title: Baselayout update
-Author: Christian Faulhammer <fauli@g.o>
-Author: William Hubbs <williamh@g.o>
-Content-Type: text/plain
-Posted: 2011-05-01
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <sys-apps/baselayout-2
-
-The baselayout package provides files which all systems must have in
-order to function properly. You are currently using version 1.x, which
-has several issues. The most significant of these is that the included
-init scripts are written entirely in bash, which makes them slow and
-not very flexible.
-
-On 2011/05/08, you will see an update for sys-apps/baselayout to
-2.x and a new package, sys-apps/openrc. It is recommended that you
-perform this update as soon as possible.
-
-Please note, after these packages are emerged, it is
-__Absolutely_Critical__ that you immediately update your configuration
-files with dispatch-conf, etc-update or a similar tool then follow the
-steps in the migration guide located at the following URL.
-http://www.gentoo.org/doc/en/openrc-migration.xml
-
-FAILURE TO FOLLOW ALL OF THESE STEPS WILL RESULT IN AN UNBOOTABLE
-SYSTEM! IF THIS SHOULD HAPPEN, YOU WILL NEED TO BOOT FROM A LIVE CD OR
-DVD, MOUNT YOUR ROOT FILE SYSTEM, CHROOT INTO THAT ENVIRONMENT AND
-FOLLOW THE ABOVE STEPS!

diff --git a/2011-08-28-mesa-r600g/2011-08-28-mesa-r600g.en.txt b/2011-08-28-mesa-r600g/2011-08-28-mesa-r600g.en.txt
deleted file mode 100644
index 110f330..0000000
--- a/2011-08-28-mesa-r600g/2011-08-28-mesa-r600g.en.txt
+++ /dev/null
@@ -1,26 +0,0 @@
-Title: Mesa r600 driver now defaults to gallium
-Author: Chí-Thanh Christopher Nguyễn <chithanh@g.o>
-Content-Type: text/plain
-Posted: 2011-08-28
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <media-libs/mesa-7.12
-
-This news item is relevant to you only if you have a Radeon graphics
-chipset and use the free/open source driver.
-
-The r600 driver that provides 3D acceleration for Radeon HD 2400 and
-later cards comes in the "classic" and "gallium" variants. The gallium
-driver is based on the new Gallium3D infrastructure and was chosen as
-the default driver for media-libs/mesa-7.11.
-
-Existing users will not be switched automatically. To switch to the
-r600 gallium driver, use the following command:
-
-    eselect mesa set r600 gallium
-
-Gallium3D requires kernel modesetting (KMS). If your system is not yet
-configured for KMS, consult the X Server Configuration HOWTO for
-instructions prior to switching:
-
-    http://www.gentoo.org/doc/en/xorg-config.xml

diff --git a/2011-10-15-libpng15/2011-10-15-libpng15.en.txt b/2011-10-15-libpng15/2011-10-15-libpng15.en.txt
deleted file mode 100644
index d5c3f27..0000000
--- a/2011-10-15-libpng15/2011-10-15-libpng15.en.txt
+++ /dev/null
@@ -1,32 +0,0 @@
-Title: Upgrade to libpng15
-Author: Samuli Suominen <ssuominen@g.o>
-Content-Type: text/plain
-Posted: 2011-10-15
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <media-libs/libpng-1.5
-
-After upgrading from libpng14 to libpng15 it's important that you rebuild
-cairo and gdk-pixbuf as soon as possible if they are installed.
-
-Then you can proceed with rebuilding the rest of the software against the new
-library:
-
-# revdep-rebuild --library libpng14.so.14 -- --keep-going
-
-Note: It might be necessary to run the previous command more than once.
-
-If you find packages not building with the message "ld: cannot find -lpng14",
-they are likely caused by broken libtool archives (.la) in your system.
-
-You can identify those files with following one-liner:
-
-# find /usr/ -name '*.la' -exec grep png14 {} +
-
-Once you have identified the broken files, you can either delete them,
-edit them in place and replace png14 with png15, or re-emerge the packages
-they belong to.
-
-More information and help is available at the following forum post:
-
-http://forums.gentoo.org/viewtopic-t-894950.html

diff --git a/2011-11-27-gnome3-unmask/2011-11-27-gnome3-unmask.en.txt b/2011-11-27-gnome3-unmask/2011-11-27-gnome3-unmask.en.txt
deleted file mode 100644
index 7077a66..0000000
--- a/2011-11-27-gnome3-unmask/2011-11-27-gnome3-unmask.en.txt
+++ /dev/null
@@ -1,16 +0,0 @@
-Title: Unmasking of and Upgrade to GNOME 3.2
-Author: Nirbheek Chauhan <nirbheek@g.o>
-Content-Type: text/plain
-Posted: 2011-11-26
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <gnome-base/gnome-session-3.2
-
-We are pleased to announce the addition to tree and unmasking of GNOME-3.2.
-Users are strongly encouraged to read the GNOME 3.2 Guide. GNOME 3 has
-a massively changed interface and requires working 3D drivers for use, however
-there is a fallback mode which is very similar to GNOME 2 and does not require
-3D acceleration.
-
-Please read the Gnome 3.2 Guide:
-http://gnome.gentoo.org/howtos/gnome-3.2-upgrade.xml

diff --git a/2011-12-06-kde473-kdepim/2011-12-06-kde473-kdepim.en.txt b/2011-12-06-kde473-kdepim/2011-12-06-kde473-kdepim.en.txt
deleted file mode 100644
index 2565795..0000000
--- a/2011-12-06-kde473-kdepim/2011-12-06-kde473-kdepim.en.txt
+++ /dev/null
@@ -1,29 +0,0 @@
-Title: Stabilization of KDE 4.7.3 including KDEPIM
-Author: Andreas K. Huettel <dilfridge@g.o>
-Content-Type: text/plain
-Posted: 2011-12-06
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <kde-base/libkdepim-4.5
-Display-If-Installed: <kde-base/blogilo-4.5
-Display-If-Installed: <kde-base/kabcclient-4.5
-Display-If-Installed: <kde-base/kdepim-strigi-analyzer-4.5
-Display-If-Installed: <kde-base/konsolekalendar-4.5
-Display-If-Installed: <kde-base/libkleo-4.5
-Display-If-Installed: <kde-base/libkpgp-4.5
-
-We are pleased to announce the upcoming stabilization of KDE 4.7.3. 
-In general the upgrade of KDE from 4.6.5 to 4.7.3 should be unproblematic.
-However, if you are using the KDEPIM application suite (i.e., akregator,
-blogilo, kmail, knode, kontact, korganizer, and others) where the stable
-version so far was 4.4.11.1, please be aware of the following:
-
-The stable upgrade from KDEPIM 4.4.11.1 to KDEPIM 4.7.3 is a MAJOR upgrade 
-with potential for major breakage. Therefore we will *try* to keep 
-and support the old, so-far stable KDEPIM 4.4.11.1 as long as possible. 
-If you *dont* want to upgrade your KDEPIM yet but keep the old version, 
-please download the following file and add it into your 
-/etc/portage/package.mask:
-http://www.gentoo.org/proj/en/desktop/kde/kdepim-4.7-mask.txt
-If you decide to upgrade, please have a look at the upgrade guide first:
-http://wiki.gentoo.org/wiki/KDEPIM-4.7_upgrade

diff --git a/2011-12-30-bacula-updates/2011-12-30-bacula-updates.en.txt b/2011-12-30-bacula-updates/2011-12-30-bacula-updates.en.txt
deleted file mode 100644
index 269dfa9..0000000
--- a/2011-12-30-bacula-updates/2011-12-30-bacula-updates.en.txt
+++ /dev/null
@@ -1,27 +0,0 @@
-Title: Bacula-5.2.3 Upgrade
-Author: Thomas Beierlein <tomjbe@g.o>
-Content-Type: text/plain
-Posted: 2011-12-30
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <app-backup/bacula-5.2.0
-
-The 5.2.x release series of Bacula uses a new database catalog format.
-If you're upgrading from a 3.x.x or 5.0.x release, you must upgrade your
-bacula catalog database.
-
-Please read the manual chapter for how to upgrade your database (see
-http://www.bacula.org/5.2.x-manuals/en/main/main/Installing_Bacula.html).
-You can find database upgrade scripts in /usr/libexec/bacula/(updatedb/).
-
-It is strongly recommended that you save a copy of your existing database
-before upgrading. For details how to do it please look into your database
-documentation.
-
-The simplest way to upgrade the database:
-
-1. Stop Bacula from running (at least the director and storage daemons).
-2. Save a copy of your existing database.
-3. Emerge the new version of Bacula.
-4. Run the appropriate upgrade script from /usr/libexec/bacula/updatedb/. 
-5. Start the new Bacula.

diff --git a/2012-02-14-baselayout-1-deprecation/2012-02-14-baselayout-1-deprecation.en.txt b/2012-02-14-baselayout-1-deprecation/2012-02-14-baselayout-1-deprecation.en.txt
deleted file mode 100644
index d5f671c..0000000
--- a/2012-02-14-baselayout-1-deprecation/2012-02-14-baselayout-1-deprecation.en.txt
+++ /dev/null
@@ -1,30 +0,0 @@
-Title: baselayout-1.x deprecation
-Author: William Hubbs <williamh@g.o>
-Content-Type: text/plain
-Posted: 2012-02-14
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <sys-apps/baselayout-2
-
-On 28 Jun 2011, baselayout-2.x and OpenRC were first marked stable on
-all supported architectures in Gentoo Linux.
-
-This was the point at which we stopped working on issues in baselayout-1
-and began encouraging users to upgrade to baselayout-2 and OpenRC.
-
-Although we are not supporting baselayout-1, we are supporting migration
-from baselayout-1 to OpenRC and baselayout-2.
-
-According to Gentoo policy, the support for migration from baselayout-1
-to baselayout-2 ends one year after baselayout-2 and OpenRC became
-stable. That date will be 28 Jun 2012.
-
-This news item is to inform you that you must migrate your system
-to baselayout-2 and OpenRC before 28 Jun 2012. Starting on this date, we
-will no longer support this migration, and you may need to re-install
-any systems which are still running baselayout-1.
-
-For questions about how to migrate your system, see the OpenRC migration
-guide [1].
-
-[1] http://www.gentoo.org/doc/en/openrc-migration.xml

diff --git a/2012-04-24-libjpeg-turbo-by-default/2012-04-24-libjpeg-turbo-by-default.en.txt b/2012-04-24-libjpeg-turbo-by-default/2012-04-24-libjpeg-turbo-by-default.en.txt
deleted file mode 100644
index 512b32f..0000000
--- a/2012-04-24-libjpeg-turbo-by-default/2012-04-24-libjpeg-turbo-by-default.en.txt
+++ /dev/null
@@ -1,19 +0,0 @@
-Title: The default JPEG implementation
-Author: Samuli Suominen <ssuominen@g.o>
-Content-Type: text/plain
-Posted: 2012-04-24
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: =media-libs/jpeg-8*
-
-libjpeg-turbo is a derivative of libjpeg that uses MMX, SSE, SSE2,
-and NEON SIMD instructions to accelerate baseline JPEG
-compression/decompression by about 2-4x on amd64, arm and x86
-platforms. It is based on libjpeg/SIMD but has numerous enhancements.
-
-All users are recommended to migrate:
-
-# emerge --deselect media-libs/jpeg
-# emerge --oneshot media-libs/libjpeg-turbo
-
-media-libs/jpeg:0 will be left in tree as a fallback implementation.

diff --git a/2012-07-23-upgrading-postfix/2012-07-23-upgrading-postfix.en.txt b/2012-07-23-upgrading-postfix/2012-07-23-upgrading-postfix.en.txt
deleted file mode 100644
index f9cb0e4..0000000
--- a/2012-07-23-upgrading-postfix/2012-07-23-upgrading-postfix.en.txt
+++ /dev/null
@@ -1,13 +0,0 @@
-Title: Upgrading to postfix-2.9
-Author: Eray Aslan <eras@g.o>
-Content-Type: text/plain
-Posted: 2012-07-23
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <mail-mta/postfix-2.9
-
-Daemons for >=mail-mta/postfix-2.9 are installed under
-/usr/libexec/postfix.  Please do not forget to adjust your main.cf by
-running etc-update/dispatch-conf or similar and accepting the new
-daemon_directory setting.  Otherwise, postfix will not be able to find
-the binaries it is looking for.

diff --git a/2013-02-10-new-13-profiles-server/2013-02-10-new-13-profiles-server.en.txt b/2013-02-10-new-13-profiles-server/2013-02-10-new-13-profiles-server.en.txt
deleted file mode 100644
index 999f73c..0000000
--- a/2013-02-10-new-13-profiles-server/2013-02-10-new-13-profiles-server.en.txt
+++ /dev/null
@@ -1,41 +0,0 @@
-Title: New 13.0 profiles and deprecation of 10.0 profiles
-Author: Andreas K. Huettel <dilfridge@g.o>
-Content-Type: text/plain
-Posted: 2013-02-10
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Profile: default/linux/alpha/10.0/server
-Display-If-Profile: default/linux/amd64/10.0/server
-Display-If-Profile: default/linux/arm/10.0/server
-Display-If-Profile: default/linux/arm/10.0/armv4/server
-Display-If-Profile: default/linux/arm/10.0/armv4t/server
-Display-If-Profile: default/linux/arm/10.0/armv5te/server
-Display-If-Profile: default/linux/arm/10.0/armv6j/server
-Display-If-Profile: default/linux/arm/10.0/armv7a/server
-Display-If-Profile: default/linux/hppa/10.0/server
-Display-If-Profile: default/linux/ia64/10.0/server
-Display-If-Profile: default/linux/m68k/10.0/server
-Display-If-Profile: default/linux/powerpc/ppc32/10.0/server
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/32bit-userland/server
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/64bit-userland/server
-Display-If-Profile: default/linux/s390/10.0/server
-Display-If-Profile: default/linux/s390/10.0/server/s390x
-Display-If-Profile: default/linux/sh/10.0/server
-Display-If-Profile: default/linux/sparc/10.0/server
-Display-If-Profile: default/linux/x86/10.0/server
-
-We have generated a new set of profiles for Gentoo installation. These are now
-called 13.0 instead of 10.0. Everyone should upgrade as soon as possible (but
-please make sure sys-apps/portage is updated to current stable *before* you
-switch profile).
-This brings (nearly) no user-visible changes. Some new files have been added
-to the profile directories that make it possible for the developers to do more
-fine-grained use flag masking (see PMS-5 for the details), and this formally
-requires a new profile tree with EAPI=5.
-In the course of this change, the "server" profiles will be removed; they do
-not exist in the 13.0 tree anymore. You should migrate to the corresponding
-parent profile. This may change the default value of some use-flags. The
-specific setting in "server" was 
-  USE="-perl -python snmp truetype xml"
-You may want to check the setting of these flags after switching profile, but
-otherwise nothing changes.

diff --git a/2013-02-10-new-13-profiles/2013-02-10-new-13-profiles.en.txt b/2013-02-10-new-13-profiles/2013-02-10-new-13-profiles.en.txt
deleted file mode 100644
index 63aca0c..0000000
--- a/2013-02-10-new-13-profiles/2013-02-10-new-13-profiles.en.txt
+++ /dev/null
@@ -1,116 +0,0 @@
-Title: New 13.0 profiles and deprecation of 10.0 profiles
-Author: Andreas K. Huettel <dilfridge@g.o>
-Content-Type: text/plain
-Posted: 2013-02-10
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Profile: default/linux/alpha/10.0
-Display-If-Profile: default/linux/alpha/10.0/desktop
-Display-If-Profile: default/linux/alpha/10.0/desktop/gnome
-Display-If-Profile: default/linux/alpha/10.0/desktop/kde
-Display-If-Profile: default/linux/alpha/10.0/developer
-Display-If-Profile: default/linux/amd64/10.0
-Display-If-Profile: default/linux/amd64/10.0/selinux
-Display-If-Profile: default/linux/amd64/10.0/desktop
-Display-If-Profile: default/linux/amd64/10.0/desktop/gnome
-Display-If-Profile: default/linux/amd64/10.0/desktop/kde
-Display-If-Profile: default/linux/amd64/10.0/developer
-Display-If-Profile: default/linux/amd64/10.0/no-multilib
-Display-If-Profile: default/linux/amd64/10.0/x32
-Display-If-Profile: default/linux/arm/10.0
-Display-If-Profile: default/linux/arm/10.0/desktop
-Display-If-Profile: default/linux/arm/10.0/desktop/gnome
-Display-If-Profile: default/linux/arm/10.0/desktop/kde
-Display-If-Profile: default/linux/arm/10.0/developer
-Display-If-Profile: default/linux/arm/10.0/armv4
-Display-If-Profile: default/linux/arm/10.0/armv4/desktop
-Display-If-Profile: default/linux/arm/10.0/armv4/desktop/gnome
-Display-If-Profile: default/linux/arm/10.0/armv4/desktop/kde
-Display-If-Profile: default/linux/arm/10.0/armv4/developer
-Display-If-Profile: default/linux/arm/10.0/armv4t
-Display-If-Profile: default/linux/arm/10.0/armv4t/desktop
-Display-If-Profile: default/linux/arm/10.0/armv4t/desktop/gnome
-Display-If-Profile: default/linux/arm/10.0/armv4t/desktop/kde
-Display-If-Profile: default/linux/arm/10.0/armv4t/developer
-Display-If-Profile: default/linux/arm/10.0/armv5te
-Display-If-Profile: default/linux/arm/10.0/armv5te/desktop
-Display-If-Profile: default/linux/arm/10.0/armv5te/desktop/gnome
-Display-If-Profile: default/linux/arm/10.0/armv5te/desktop/kde
-Display-If-Profile: default/linux/arm/10.0/armv5te/developer
-Display-If-Profile: default/linux/arm/10.0/armv6j
-Display-If-Profile: default/linux/arm/10.0/armv6j/desktop
-Display-If-Profile: default/linux/arm/10.0/armv6j/desktop/gnome
-Display-If-Profile: default/linux/arm/10.0/armv6j/desktop/kde
-Display-If-Profile: default/linux/arm/10.0/armv6j/developer
-Display-If-Profile: default/linux/arm/10.0/armv7a
-Display-If-Profile: default/linux/arm/10.0/armv7a/desktop
-Display-If-Profile: default/linux/arm/10.0/armv7a/desktop/gnome
-Display-If-Profile: default/linux/arm/10.0/armv7a/desktop/kde
-Display-If-Profile: default/linux/arm/10.0/armv7a/developer
-Display-If-Profile: default/linux/hppa/10.0
-Display-If-Profile: default/linux/hppa/10.0/desktop
-Display-If-Profile: default/linux/hppa/10.0/developer
-Display-If-Profile: default/linux/ia64/10.0
-Display-If-Profile: default/linux/ia64/10.0/desktop
-Display-If-Profile: default/linux/ia64/10.0/desktop/gnome
-Display-If-Profile: default/linux/ia64/10.0/desktop/kde
-Display-If-Profile: default/linux/ia64/10.0/developer
-Display-If-Profile: default/linux/m68k/10.0
-Display-If-Profile: default/linux/m68k/10.0/desktop
-Display-If-Profile: default/linux/m68k/10.0/desktop/gnome
-Display-If-Profile: default/linux/m68k/10.0/desktop/kde
-Display-If-Profile: default/linux/m68k/10.0/developer
-Display-If-Profile: default/linux/mips/10.0
-Display-If-Profile: default/linux/mips/10.0/n32
-Display-If-Profile: default/linux/mips/10.0/n64
-Display-If-Profile: default/linux/mips/10.0/multilib
-Display-If-Profile: default/linux/mips/10.0/multilib/n32
-Display-If-Profile: default/linux/mips/10.0/multilib/n64
-Display-If-Profile: default/linux/mips/10.0/mipsel
-Display-If-Profile: default/linux/mips/10.0/mipsel/n32
-Display-If-Profile: default/linux/mips/10.0/mipsel/n64
-Display-If-Profile: default/linux/mips/10.0/mipsel/multilib
-Display-If-Profile: default/linux/mips/10.0/mipsel/multilib/n32
-Display-If-Profile: default/linux/mips/10.0/mipsel/multilib/n64
-Display-If-Profile: default/linux/powerpc/ppc32/10.0
-Display-If-Profile: default/linux/powerpc/ppc32/10.0/desktop
-Display-If-Profile: default/linux/powerpc/ppc32/10.0/desktop/gnome
-Display-If-Profile: default/linux/powerpc/ppc32/10.0/desktop/kde
-Display-If-Profile: default/linux/powerpc/ppc32/10.0/developer
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/32bit-userland
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/32bit-userland/desktop
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/32bit-userland/desktop/gnome
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/32bit-userland/desktop/kde
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/32bit-userland/developer
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/64bit-userland
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/64bit-userland/desktop
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/64bit-userland/desktop/gnome
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/64bit-userland/desktop/kde
-Display-If-Profile: default/linux/powerpc/ppc64/10.0/64bit-userland/developer
-Display-If-Profile: default/linux/s390/10.0
-Display-If-Profile: default/linux/s390/10.0/s390x
-Display-If-Profile: default/linux/sh/10.0
-Display-If-Profile: default/linux/sh/10.0/desktop
-Display-If-Profile: default/linux/sh/10.0/desktop/gnome
-Display-If-Profile: default/linux/sh/10.0/desktop/kde
-Display-If-Profile: default/linux/sh/10.0/developer
-Display-If-Profile: default/linux/sparc/10.0
-Display-If-Profile: default/linux/sparc/10.0/desktop
-Display-If-Profile: default/linux/sparc/10.0/desktop/gnome
-Display-If-Profile: default/linux/sparc/10.0/desktop/kde
-Display-If-Profile: default/linux/sparc/10.0/developer
-Display-If-Profile: default/linux/x86/10.0
-Display-If-Profile: default/linux/x86/10.0/selinux
-Display-If-Profile: default/linux/x86/10.0/desktop
-Display-If-Profile: default/linux/x86/10.0/desktop/gnome
-Display-If-Profile: default/linux/x86/10.0/desktop/kde
-Display-If-Profile: default/linux/x86/10.0/developer
-
-We have generated a new set of profiles for Gentoo installation. These are now 
-called 13.0 instead of 10.0. Everyone should upgrade as soon as possible (but 
-please make sure sys-apps/portage is updated to current stable *before* you
-switch profile).
-This brings (nearly) no user-visible changes. Some new files have been added
-to the profile directories that make it possible for the developers to do more 
-fine-grained use flag masking (see PMS-5 for the details), and this formally 
-requires a new profile tree with EAPI=5.

diff --git a/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt b/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt
deleted file mode 100644
index 2816d06..0000000
--- a/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt
+++ /dev/null
@@ -1,102 +0,0 @@
-Title: Upgrading udev to version >=200
-Author: Samuli Suominen <ssuominen@g.o>
-Content-Type: text/plain
-Posted: 2013-03-29
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Installed: <sys-fs/udev-201
-
-This replaces the earlier news item about the udev 197 upgrade and
-describes the predictable network interface names in more detail.
-
-If you skip anything in this news item, your system will not be
-bootable, or your networking will be down, or both.
-
-Pay attention also to every message printed by emerge of sys-fs/udev
-and sys-fs/udev-init-scripts as this news item may not be complete.
-
-1. udev-postmount init script:
-
-Remove the udev-postmount init script from your runlevels.
-
-2. devtmpfs support:
-
-You need at least version 2.6.32 of the kernel for devtmpfs
-functionality. Once you have this, make sure CONFIG_DEVTMPFS=y is set
-in the kernel configuration. See the gentoo udev guide for the option in
-make menuconfig [1].
-
-If you have a line for /dev in /etc/fstab, make sure it is configured
-for file system type devtmpfs (not tmpfs or any other type). Also, you
-can remove this line if you prefer, since devtmpfs is mounted
-automatically.
-
-3. Old interface naming rules:
-
-If the system still has old network interface renaming rules in
-/etc/udev/rules.d, like 70-persistent-net.rules, those will need
-to be either modified or removed.
-
-If you choose to modify them, you must use free namespace (like net*
-or internet*) instead of kernel namespace (like eth* or wlan*)
-because in-place renaming has been deprecated, see small
-documentation of it if you like[2].
-
-The file 70-persistent-net.rules, like the 70-persistent-cd.rules
-should be removed, so if you modify, rename the file also to something
-else like 70-my-network.rules to silence the deprecation warning coming
-from the end of the sys-fs/udev emerge.
-
-This is the old format with reserved namespace:
-
-SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="eth0"
-SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="yy:yy:yy:yy:yy:yy", NAME="eth1"
-
-This is the new format with free namespace:
-
-SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="net0"
-SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="yy:yy:yy:yy:yy:yy", NAME="net1"
-
-4. predictable network interface names:
-
-If /etc/udev/rules.d/80-net-name-slot.rules is an empty file or a
-symlink to /dev/null, the new names will be disabled and the kernel will
-do all the interface naming, and the resulting names may vary by kernel
-configuration, hardware configuration and kernel version.
-
-Also, the forementioned old 70-persistent-net.rules might interfere with
-the new predictable interface names.
-
-You can get attributes of your network interfaces using a command like
-the following (replace eth0 with the name of the appropriate interface):
-
-# udevadm test-builtin net_id /sys/class/net/eth0 2> /dev/null
-
-You can copy /lib/udev/rules.d/80-net-name-slot.rules to
-/etc/udev/rules.d and specify the attributes and in which order
-they will be used for naming. See upstream wiki[3] for detailed list
-of options.
-
-You can prepare the system for the new names before booting for example
-by renaming /etc/init.d/net.* symlinks, editing /etc/conf.d/net, etc.
-
-The feature can also be completely disabled using net.ifnames=0 on the
-kernel command line.
-
-If you only have one interface card, you don't necessarily have much
-use for this feature as the name almost always stays at eth0, you can
-easily disable it using forementioned methods.
-
-This feature can also replace the functionality of sys-apps/biosdevname,
-but you can still keep using it if you want.
-
-In a normal new installation there are no files in /etc/udev/rules.d
-and if you haven't edited any files you have in there, you should most
-likely backup and delete them all if they don't belong to any packages.
-
-The official wiki has a dedicated page for udev upgrade notes[4].
-
-[1] http://www.gentoo.org/doc/en/udev-guide.xml
-[2] http://www.kernel.org/doc/htmldocs/device-drivers/API-device-rename.html
-[3] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
-[4] http://wiki.gentoo.org/wiki/Udev/upgrade

diff --git a/2013-04-10-baselayout-1-deprecation-final-warning/2013-04-10-baselayout-1-deprecation-final-warning.en.txt b/2013-04-10-baselayout-1-deprecation-final-warning/2013-04-10-baselayout-1-deprecation-final-warning.en.txt
deleted file mode 100644
index 331d36f..0000000
--- a/2013-04-10-baselayout-1-deprecation-final-warning/2013-04-10-baselayout-1-deprecation-final-warning.en.txt
+++ /dev/null
@@ -1,32 +0,0 @@
-Title: baselayout-1.x deprecation final warning
-Author: William Hubbs <williamh@g.o>
-Content-Type: text/plain
-Posted: 2013-04-10
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <sys-apps/baselayout-2
-
-WARNING! THIS NEWS ITEM REQUIRES IMMEDIATE ATTENTION!
-
-On 28 Jun 2011, baselayout-2.x and OpenRC were first marked stable on
-all supported architectures in Gentoo Linux.
-
-Although we no longer support baselayout-1.x, we have continued support
-for migration from baselayout-1.x to baselayout-2.x and OpenRC.
-
-According to Gentoo policy, the support for migration was slated to end
-on 28 Jun 2012, a year after OpenRC was first marked stable.
-
-This is your final warning. openrc-0.11.8 will be the final release of
-OpenRC to support migration from baselayout-1.x.
-
-If you do not upgrade your system to baselayout-2.x and openrc-0.11.8
-before openrc-0.11.8 leaves the tree, you will have to perform the
-migration manually when you upgrade or you will be left with an
-unbootable system. Manual migration is not officially supported, and
-could include fixing things with a live cd or re-installing your system.
-
-For questions about how to migrate your system, see the OpenRC migration
-guide [1].
-
-[1] http://www.gentoo.org/doc/en/openrc-migration.xml

diff --git a/2013-06-01-mysql-pbxt-dropped/2013-06-01-mysql-pbxt-dropped.en.txt b/2013-06-01-mysql-pbxt-dropped/2013-06-01-mysql-pbxt-dropped.en.txt
deleted file mode 100644
index 1f7293a..0000000
--- a/2013-06-01-mysql-pbxt-dropped/2013-06-01-mysql-pbxt-dropped.en.txt
+++ /dev/null
@@ -1,41 +0,0 @@
-Title: PBXT now unsupported in MySQL/MariaDB
-Author: Robin H. Johnson <robbat2@g.o>
-Content-Type: text/plain
-Posted: 2013-06-01
-Revision: 4
-News-Item-Format: 1.0
-Display-If-Installed: dev-db/mysql
-Display-If-Installed: dev-db/mysql-cluster
-Display-If-Installed: dev-db/mariadb
-Display-If-Installed: dev-db/mariadb-galera
-Display-If-Installed: dev-db/percona-server
-Display-If-Installed: dev-db/google-mysql
-
-The PBXT/PrimeBase engine is unsupported upstream in MySQL & MariaDB for some
-time now [1]. It is no longer built in the upstream MariaDB 5.5 binaries[2][3]
-and if it is enabled in a source build, it fails many tests [4].
-
-In light of this, the MySQL team has decided to mask it in
-profiles/base/package.use.mask for all relevant packages.
->=dev-db/mysql-5.5 pbxt
->=dev-db/mariadb-5.5 pbxt
->=dev-db/mysql-cluster-5.5 pbxt # overlay
->=dev-db/mariadb-galera-5.5 pbxt # overlay
->=dev-db/percona-server-5.5 pbxt # overlay
->=dev-db/google-mysql-5.5 pbxt # overlay
-
-All users who have data stored in PBXT-backed tables MUST convert the tables
-to another format BEFORE upgrading to MySQL/MariaDB 5.5, as the tables will
-become inaccessible otherwise.
-
-We will continue to allow it to be built in the 5.0/5.1 series, to make the
-above data migration easy, but we strongly encourage all users to move their
-data out of the PBXT engine.
-
-If you need to check for PBXT tables easily, look in your MySQL/MariaDB
-datadir for any files with a .xt extension.
-
-1. https://lists.launchpad.net/pbxt-discuss/msg00134.html
-2. http://www.bytebot.net/blog/archives/2012/05/25/mariadb-5-5-has-deprecated-pbxt
-3. https://kb.askmonty.org/en/about-pbxt/
-4. https://bugs.gentoo.org/show_bug.cgi?id=471616#c1

diff --git a/2013-06-30-cups16/2013-06-30-cups16.en.txt b/2013-06-30-cups16/2013-06-30-cups16.en.txt
deleted file mode 100644
index ba72857..0000000
--- a/2013-06-30-cups16/2013-06-30-cups16.en.txt
+++ /dev/null
@@ -1,21 +0,0 @@
-Title: Printer browsing in net-print/cups-1.6
-Author: Andreas K. Huettel <dilfridge@g.o>
-Content-Type: text/plain
-Posted: 2013-06-30
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <=net-print/cups-1.6.2-r5
-
-net-print/cups-1.6 no longer supports automatic remote printers or
-implicit classes via the CUPS, LDAP, or SLP protocols, i.e. "network
-browsing".
-
-The browsing functionality can be restored by running cups-browsed
-from net-print/cups-filters as a separate daemon (just add its init
-script to your default runlevel). By default cups-browsed uses the
-net-print/cups-1.5 browse protocol, but it can also utilize zeroconf
-(if the zeroconf use flag is set). See /etc/cups/cups-browsed.conf
-for configuration.
-
-Of course, directly specifying the location of your printers in
-the cups interface works as well.

diff --git a/2013-08-07-vanilla-sources-stablization-policy/2013-08-07-vanilla-sources-stablization-policy.en.txt b/2013-08-07-vanilla-sources-stablization-policy/2013-08-07-vanilla-sources-stablization-policy.en.txt
deleted file mode 100644
index 75158ec..0000000
--- a/2013-08-07-vanilla-sources-stablization-policy/2013-08-07-vanilla-sources-stablization-policy.en.txt
+++ /dev/null
@@ -1,26 +0,0 @@
-Title: vanilla-sources stabilization policy
-Author: Mike Pagano <mpagano@g.o>
-Content-Type: text/plain
-Posted: 2013-08-07
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: sys-kernel/vanilla-sources
-
-The Gentoo Kernel Team will no longer be providing stable
-vanilla-sources kernels. All currently stabilized vanilla-sources
-versions will be dropped to ~arch. The Arch teams, via normal requests
-of the Kernel Team, will continue to stabilize gentoo-sources kernels
-upon request. This decision is based on the facts that upstream is now
-releasing approximately 1-2 vanilla-sources kernels a week. Arch teams,
-understandably, are unable to keep up with this rate of release.  As
-most vanilla releases contain security fixes, the user who only runs
-stable vanilla-sources will consistently be behind and potentially at
-risk.  For the latest "upstream kernel unpatched by Gentoo", we
-recommend users add 'sys-kernel/vanilla-sources' to their
-package.accept_keywords file. gentoo-sources will continue to be a
-tested and supported version for Gentoo users.
-
-
-Note: This news item only applies to gentoo-sources and vanilla-sources.
-Other kernels currently maintained in portage have their own policies
-and procedures in place today.

diff --git a/2013-09-22-minor-arches-1/2013-09-22-minor-arches-1.en.txt b/2013-09-22-minor-arches-1/2013-09-22-minor-arches-1.en.txt
deleted file mode 100644
index c6fc3ac..0000000
--- a/2013-09-22-minor-arches-1/2013-09-22-minor-arches-1.en.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-Title: m68k, s390, sh are dropping stable keywords                                                                                                                                     
-Author: Andreas K. Huettel <dilfridge@g.o>
-Content-Type: text/plain
-Posted: 2013-09-22
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Keyword: m68k
-Display-If-Keyword: s390
-Display-If-Keyword: sh
-
-Following discussion [1] and a vote by the Gentoo Council [2,3], 
-m68k, s390, and sh will drop all stable keywords and become 
-unstable/testing only arches. The main reason for this is that 
-these arch teams visibly lack manpower, resulting in undesirable
-delays.
-
-In a week, the ACCEPT_KEYWORDS variable in the respective profiles
-will be switched to automatically include ~arch packages. Systems
-running stable before will update to current unstable/testing then.
-Afterwards m68k, s390, and sh keywords on all ebuilds will be
-changed to ~m68k, ~s390, and ~sh.
-
-No steps are required from users, however you should be aware
-of the upcoming changes.
-
-[1] http://thread.gmane.org/gmane.linux.gentoo.project/2975/focus=2984
-[2] http://www.gentoo.org/proj/en/council/meeting-logs/20130917.txt
-[3] http://www.gentoo.org/proj/en/council/meeting-logs/20130917-summary.txt

diff --git a/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt b/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt
deleted file mode 100644
index 4f382a7..0000000
--- a/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt
+++ /dev/null
@@ -1,29 +0,0 @@
-Title: Separate /usr on Linux requires initramfs
-Author: William Hubbs <williamh@g.o>
-Content-Type: text/plain
-Posted: 2013-09-27
-Revision: 1
-News-Item-Format: 1.0
-
-Linux systems which have / and /usr on separate file systems but do not
-use an initramfs will not be supported starting on 01-Nov-2013.
-
-If you have / and /usr on separate file systems and you are not
-currently using an initramfs, you must set one up before this date.
-Otherwise, at some point on or after this date, upgrading packages
-will make your system unbootable.
-
-For more information on setting up an initramfs, see this URL:
-
-https://wiki.gentoo.org/wiki/Initramfs/HOWTO
-
-Due to many upstream changes, properly supporting Linux systems that
-have /usr missing at boot time has become increasingly difficult.
-Despite all our efforts, it already breaks in some exotic
-configurations, and this trend is likely to grow worse.
-
-For more information on the upstream changes and why using an initramfs
-is the cleanest route forward, see the following URLs:
-
-http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
-https://blog.flameeyes.eu/2013/01/the-boot-process

diff --git a/2013-10-14-grub2-migration/2013-10-14-grub2-migration.en.txt b/2013-10-14-grub2-migration/2013-10-14-grub2-migration.en.txt
deleted file mode 100644
index d932346..0000000
--- a/2013-10-14-grub2-migration/2013-10-14-grub2-migration.en.txt
+++ /dev/null
@@ -1,31 +0,0 @@
-Title: GRUB2 migration
-Author: Mike Gilbert <floppym@g.o>
-Content-Type: text/plain
-Posted: 2013-10-14
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <sys-boot/grub-1
-
-A newer version of GRUB (sys-boot/grub) is now stable. There are now
-two available slots:
-
-sys-boot/grub:0 - Known as "GRUB Legacy"
-sys-boot/grub:2 - Known as "GRUB2"
-
-GRUB2 uses a different configuration format, and requires a manual
-migration before your system will actually use it. A guide [1] is
-available on the gentoo.org website, and the Gentoo wiki [2][3] has
-additional information.
-
-If you would prefer not to migrate at this time, you do not need to
-take any action: GRUB Legacy will remain functional in /boot. To
-prevent any associated files (documentation) from being removed, add
-sys-boot/grub:0 to your world file. For example:
-
-emerge --noreplace sys-boot/grub:0
-
-References:
-
-[1] http://www.gentoo.org/doc/en/grub2-migration.xml
-[2] https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
-[3] https://wiki.gentoo.org/wiki/GRUB2

diff --git a/2013-10-24-minor-arches-2/2013-10-24-minor-arches-2.en.txt b/2013-10-24-minor-arches-2/2013-10-24-minor-arches-2.en.txt
deleted file mode 100644
index 4f2e0a7..0000000
--- a/2013-10-24-minor-arches-2/2013-10-24-minor-arches-2.en.txt
+++ /dev/null
@@ -1,23 +0,0 @@
-Title: alpha, ia64: maintainers may remove stable versions
-Author: Andreas K. Huettel <dilfridge@g.o>
-Content-Type: text/plain
-Posted: 2013-10-24
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Keyword: alpha
-Display-If-Keyword: ia64
-
-Following discussion [1] and a vote by the Gentoo Council [2,3], 
-on alpha and ia64 package maintainers are allowed to remove
-the last stable version of a package under certain circumstances
-(basically when it is outdated and the stablerequest for a newer
-version on alpha or ia64 has been pending for a while; for the 
-details, see [2,3]).
-
-You should be aware that this may occasionally cause broken
-dependencies and/or require keywording of packages for stable 
-users. Then again, things may work out fine just as well.
-
-[1] http://thread.gmane.org/gmane.linux.gentoo.project/2975/focus=2984
-[2] http://www.gentoo.org/proj/en/council/meeting-logs/20130917.txt
-[3] http://www.gentoo.org/proj/en/council/meeting-logs/20130917-summary.txt

diff --git a/2013-11-07-python-exec-package-move/2013-11-07-python-exec-package-move.en.txt b/2013-11-07-python-exec-package-move/2013-11-07-python-exec-package-move.en.txt
deleted file mode 100644
index 3e5536f..0000000
--- a/2013-11-07-python-exec-package-move/2013-11-07-python-exec-package-move.en.txt
+++ /dev/null
@@ -1,46 +0,0 @@
-Title: python-exec package move
-Author: Michał Górny <mgorny@g.o>
-Content-Type: text/plain
-Posted: 2013-11-07
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: dev-python/python-exec
-
-Due to the recent issues which caused dev-python/python-exec:0 to be
-removed prematurely [1], we had to perform an urgent package move.
-Since we could not use the automatic updates support in portage, users
-will notice two python-exec packages and possibly blockers.
-
-Currently, dev-lang/python-exec is the real package that contains
-python-exec and that will be used in the future. dev-python/python-exec
-is a virtual package that is kept for compatibility with dependencies
-in already-installed packages.
-
-In the most favorable scenario, the package will be upgraded correctly
-on your next world update if you use the '--deep' (-D) and '--update'
-(-u) options. If you don't want to perform a complete world update
-or if it fails for you, you may as well manually upgrade
-dev-python/python-exec:
-
-  emerge -1 dev-python/python-exec
-
-This will cause portage to update both python-exec packages and resolve
-the blockers properly.
-
-Please note that if you have applied any kind of package-specific
-modifications to dev-python/python-exec (such as applying keywords
-through 'package.accept_keywords'), you will need to copy them to
-dev-lang/python-exec as well.
-
-If you have applied keywords to dev-python/python-exec in order
-to unmask Python 3.3 on a stable system, please consider removing
-the keywords and reading our wiki page that explains how to properly
-unmask USE flags [2].
-
-We apologize for all the inconveniences. If you have any more issues
-with python-exec, please do not hesitate to contact as at #gentoo-python
-IRC channel (@freenode) or the gentoo-python@l.g.o mailing
-list.
-
-[1]:https://bugs.gentoo.org/show_bug.cgi?id=489440
-[2]:https://wiki.gentoo.org/wiki/Unmasking_non-stable_Python_implementations

diff --git a/2013-11-23-gnome-38/2013-11-23-gnome-38.en.txt b/2013-11-23-gnome-38/2013-11-23-gnome-38.en.txt
deleted file mode 100644
index 11773fc..0000000
--- a/2013-11-23-gnome-38/2013-11-23-gnome-38.en.txt
+++ /dev/null
@@ -1,23 +0,0 @@
-Title: Upgrade to GNOME 3.8
-Author: Pacho Ramos <pacho@g.o>
-Content-Type: text/plain
-Posted: 2013-11-23
-Revision: 1
-News-Item-Format: 1.0
-Display-If-Installed: <gnome-base/gnome-3.8
-Display-If-Installed: <gnome-base/gnome-light-3.8
-Display-If-Installed: <gnome-base/gnome-session-3.8
-Display-If-Installed: <gnome-base/gdm-3.8
-
-We are pleased to announce the stabilization of GNOME 3.8. Users are
-strongly encouraged to read the GNOME 3.8 Upgrade Guide to avoid any
-possible issues relating to the upgrade. The guide will also show you
-how to migrate to systemd as it is the only supported setup now,
-suggesting you how to avoid blockers and problems trying to let you
-have a smoother update.
-
-Additionally, it will inform you about important changes regarding
-configuration and troubleshooting.
-
-Please read the Gnome 3.8 Upgrade Guide:
-http://wiki.gentoo.org/wiki/GNOME/3.8-upgrade-guide