diff options
Diffstat (limited to 'gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news')
154 files changed, 3424 insertions, 0 deletions
diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2007-05-04-paludis-0.24/2007-05-04-paludis-0.24.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2007-05-04-paludis-0.24/2007-05-04-paludis-0.24.en.txt new file mode 100644 index 0000000..d66e774 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2007-05-04-paludis-0.24/2007-05-04-paludis-0.24.en.txt @@ -0,0 +1,12 @@ +Title: Changes for Paludis 0.24 +Author: Piotr Jaroszyński <peper@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2007-05-04-paludis-0.24/2007-05-04-paludis-0.24.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2007-05-04-paludis-0.24/2007-05-04-paludis-0.24.en.txt.asc new file mode 100644 index 0000000..41dbbf5 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2007-05-04-paludis-0.24/2007-05-04-paludis-0.24.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.13 (GNU/Linux) + +iEYEABECAAYFAkrtoE4ACgkQcxLzpIGCsLRC+gCfX+cj8qmRgKb+CoLwUjF/siY4 +sk0An1WTVHg6Vm6pFAKTbxsKfspMPJbc +=OYhI +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-01-04-sparc-multilib/2009-01-04-sparc-multilib.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-01-04-sparc-multilib/2009-01-04-sparc-multilib.en.txt new file mode 100644 index 0000000..f3e9bf3 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-01-04-sparc-multilib/2009-01-04-sparc-multilib.en.txt @@ -0,0 +1,17 @@ +Title: Migrating to the new sparc multilib profile +Author: Friedrich Oslage <bluebird@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-tetex/2009-04-06-tetex.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-tetex/2009-04-06-tetex.en.txt new file mode 100644 index 0000000..9546708 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-tetex/2009-04-06-tetex.en.txt @@ -0,0 +1,14 @@ +Title: Migration from teTeX to TeXLive +Author: Christian Faulhammer <fauli@gentoo.org> +Author: Ulrich Müller <ulm@gentoo.org> +Author: Alexis Ballier <aballier@gentoo.org> +Content-Type: text/plain +Posted: 2009-04-06 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: app-text/tetex + +teTeX is obsolete and has been unsupported upstream since May of 2006. +All users who still have teTeX installed should uninstall it and install +TeXLive using the upgrade guide accessible at the following URL: + http://www.gentoo.org/proj/en/tex/texlive-migration-guide.xml diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-tetex/2009-04-06-tetex.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-tetex/2009-04-06-tetex.en.txt.asc new file mode 100644 index 0000000..c77ce0b --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-tetex/2009-04-06-tetex.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.10 (GNU/Linux) + +iEYEABECAAYFAknZCiEACgkQNQqtfCuFnePkzACeMTjE+7PH6QoUP7aOk/cLZJ57 +h5IAn3zBOKY+NGt9sCSfC21o+idT/JwB +=seDb +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-x_server-1_5/2009-04-06-x_server-1_5.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-x_server-1_5/2009-04-06-x_server-1_5.en.txt new file mode 100644 index 0000000..c92df98 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-x_server-1_5/2009-04-06-x_server-1_5.en.txt @@ -0,0 +1,15 @@ +Title: Migration to X.org Server 1.5 +Author: Remi Cardona <remi@gentoo.org> +Author: Christian Faulhammer <fauli@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-x_server-1_5/2009-04-06-x_server-1_5.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-x_server-1_5/2009-04-06-x_server-1_5.en.txt.asc new file mode 100644 index 0000000..014e822 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-06-x_server-1_5/2009-04-06-x_server-1_5.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.10 (GNU/Linux) + +iEYEABECAAYFAknZCjcACgkQNQqtfCuFneOlvgCfWpXJs3RzMfAlWXu8srSGZis0 +DK0An3quxyXSWNeOkK+LIrAq9CVSR7LY +=MRuL +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-18-java-config-wrapper-0.16/2009-04-18-java-config-wrapper-0.16.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-18-java-config-wrapper-0.16/2009-04-18-java-config-wrapper-0.16.en.txt new file mode 100644 index 0000000..d4c0bbb --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-18-java-config-wrapper-0.16/2009-04-18-java-config-wrapper-0.16.en.txt @@ -0,0 +1,30 @@ +Title: Generation 1 Java Setup Deprecated +Author: Petteri Räty <betelgeuse@gentoo.org> +Content-Type: text/plain +Posted: 2009-04-18 +Revision: 2 +News-Item-Format: 1.0 +Display-If-Installed: >=dev-java/java-config-wrapper-0.16 + +For a long time the Java team required a 1.4 JDK to be +installed in order for old java ebuilds to work. All these +ebuilds are now gone from the main tree so the requirement +to have a 1.4 JDK installed has been lifted. + +In order to remove things left over by the generation 1 +setup please run java-check-environment and follow the +instructions. + +If you want to remove 1.4 JDKs, you should use emerge --depclean. +Depending on what you have installed you might not need a +1.4 JDK any more. To see if you still need a 1.4 JDK use: + +emerge -av --depclean virtual/jdk:1.4 + +If you don't need virtual/jdk:1.4 any more then you can remove the +individual JDKs. First get the list of installed JDKs with +eselect and then remove those that are not needed any longer with +depclean, for example: + +eselect java-vm list +emerge -av --depclean sun-jdk:1.4 diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-18-java-config-wrapper-0.16/2009-04-18-java-config-wrapper-0.16.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-18-java-config-wrapper-0.16/2009-04-18-java-config-wrapper-0.16.en.txt.asc new file mode 100644 index 0000000..9d68e30 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-04-18-java-config-wrapper-0.16/2009-04-18-java-config-wrapper-0.16.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.11 (GNU/Linux) + +iEYEABECAAYFAknrh1kACgkQcxLzpIGCsLSp9wCfR0yUo1zI3+KHN2WSLF0AcoI8 +Zd0An2KU2KSCU6wx2rSNVJLK9ZZMizeM +=QQ2/ +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-07-12-xorg-74-alpha/2009-07-12-xorg-74-alpha.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-07-12-xorg-74-alpha/2009-07-12-xorg-74-alpha.en.txt new file mode 100644 index 0000000..a275ec1 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-07-12-xorg-74-alpha/2009-07-12-xorg-74-alpha.en.txt @@ -0,0 +1,24 @@ +Title: xorg-x11-7.4 and xorg-server-1.5 kernel support +Author: Tobias Klausmann <klausman@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-07-12-xorg-74-alpha/2009-07-12-xorg-74-alpha.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-07-12-xorg-74-alpha/2009-07-12-xorg-74-alpha.en.txt.asc new file mode 100644 index 0000000..e8d0a4f --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-07-12-xorg-74-alpha/2009-07-12-xorg-74-alpha.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.11 (GNU/Linux) + +iEYEABECAAYFAkp9VOIACgkQA+4Doc5dVOgX5gCgjYJ8wbxQ2jjVg9phPTcj7Ndd +qc4Aniw7wmu6c+mVt2+LPCGksT5nic5Y +=w6WG +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-09-27-qt_use_changes/2009-09-27-qt_use_changes.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-09-27-qt_use_changes/2009-09-27-qt_use_changes.en.txt new file mode 100644 index 0000000..815b2f0 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-09-27-qt_use_changes/2009-09-27-qt_use_changes.en.txt @@ -0,0 +1,25 @@ +Title: Qt 4.5.2 default USE flag changes +Author: Alex Alexander <wired@gentoo.org> +Content-Type: text/plain +Posted: 2009-09-27 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: <x11-libs/qt-core-4.5.2 + +Qt version 4.5.2 has significant changes in the USE flags enabled by +default. + +When upgrading, make sure you check and re-enable any USE flags you +need. + +Depending on your system and installed packages, you might hit an issue +where Portage is getting confused by this USE flag change, trying to mix +old 4.5.1 ebuilds with new 4.5.2 ones, resulting in blocks. + +If this happens to you, please add the offending USE flags (usually +'qt3support' and 'dbus') in your USE= or switch to a desktop profile +(eselect profile list). Check this post [0] for more details on this +issue. + +[0] http://www.linuxized.com/p192 + diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-09-27-qt_use_changes/2009-09-27-qt_use_changes.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-09-27-qt_use_changes/2009-09-27-qt_use_changes.en.txt.asc new file mode 100644 index 0000000..22737f1 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-09-27-qt_use_changes/2009-09-27-qt_use_changes.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.11 (GNU/Linux) + +iEYEABECAAYFAkq/QDAACgkQCtniI/gSTSdKwACcDDoo1mIu6Itsav2lolM0F4GC +YXEAn1warrBxrvKsSFTrAi+Yl4NMpYGX +=Vlu0 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-02-xorg-server-1-6-libxcb-1.4/2009-10-02-xorg-server-1-6-libxcb-1.4.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-02-xorg-server-1-6-libxcb-1.4/2009-10-02-xorg-server-1-6-libxcb-1.4.en.txt new file mode 100644 index 0000000..886f7f9 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-02-xorg-server-1-6-libxcb-1.4/2009-10-02-xorg-server-1-6-libxcb-1.4.en.txt @@ -0,0 +1,15 @@ +Title: Migration to X.org Server 1.6 and libxcb 1.4 +Author: Remi Cardona <remi@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-02-xorg-server-1-6-libxcb-1.4/2009-10-02-xorg-server-1-6-libxcb-1.4.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-02-xorg-server-1-6-libxcb-1.4/2009-10-02-xorg-server-1-6-libxcb-1.4.en.txt.asc new file mode 100644 index 0000000..ea46797 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-02-xorg-server-1-6-libxcb-1.4/2009-10-02-xorg-server-1-6-libxcb-1.4.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.11 (GNU/Linux) + +iEYEABECAAYFAkrJCScACgkQfUU/I5AasIqG0gCg95ypoQN3rAav8p9cZEuip0zi +XI0AoPchWCd3XDgUqTuvFcqXGSEHmsD/ +=Irzu +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-08-gnome-226/2009-10-08-gnome-226.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-08-gnome-226/2009-10-08-gnome-226.en.txt new file mode 100644 index 0000000..065e675 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-08-gnome-226/2009-10-08-gnome-226.en.txt @@ -0,0 +1,19 @@ +Title: Upgrade to GNOME 2.26 +Author: Mart Raudsepp <leio@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-08-gnome-226/2009-10-08-gnome-226.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-08-gnome-226/2009-10-08-gnome-226.en.txt.asc new file mode 100644 index 0000000..55ddd7b --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-08-gnome-226/2009-10-08-gnome-226.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.8 (GNU/Linux) + +iEYEABECAAYFAkrNWBwACgkQkeYb6olFHJe1HQCdGTvIGUfqjjCKxBIvzVMznf01 +pmQAoNy2QrUBhlUAMlOj5BOUtdVWnXAp +=e110 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-22-default-linux/2009-10-22-default-linux.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-22-default-linux/2009-10-22-default-linux.en.txt new file mode 100644 index 0000000..88ca0e0 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-22-default-linux/2009-10-22-default-linux.en.txt @@ -0,0 +1,29 @@ +Title: Using default-linux profile is now obsolete +Author: Samuli Suominen <ssuominen@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-22-default-linux/2009-10-22-default-linux.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-22-default-linux/2009-10-22-default-linux.en.txt.asc new file mode 100644 index 0000000..aa104f5 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2009-10-22-default-linux/2009-10-22-default-linux.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.13 (GNU/Linux) + +iEYEABECAAYFAkrgpMUACgkQjqGN5W0RyKKZHQCgjLkeRRFmCRdHSvtxaIjt7oui +H+4AniOcDXUIyNQD3E6U5SR9LAkufmk6 +=6h9h +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-01-31-eselect-opengl/2010-01-31-eselect-opengl.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-01-31-eselect-opengl/2010-01-31-eselect-opengl.en.txt new file mode 100644 index 0000000..469d62a --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-01-31-eselect-opengl/2010-01-31-eselect-opengl.en.txt @@ -0,0 +1,16 @@ +Title: Removal of libGL.la +Author: Tomáš Chvátal <scarabeus@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-01-31-eselect-opengl/2010-01-31-eselect-opengl.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-01-31-eselect-opengl/2010-01-31-eselect-opengl.en.txt.asc new file mode 100644 index 0000000..a422587 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-01-31-eselect-opengl/2010-01-31-eselect-opengl.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.14 (GNU/Linux) + +iEYEABECAAYFAkuP06oACgkQjqGN5W0RyKJM9wCeMmgGiOcpG8p6BcLIBLO2s7Mn +PtAAmwQOcpPwi8bD0BYVVb1YPCeKH2hJ +=Ca4S +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-21-mysql-upgrade/2010-02-21-mysql-upgrade.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-21-mysql-upgrade/2010-02-21-mysql-upgrade.en.txt new file mode 100644 index 0000000..493bab4 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-21-mysql-upgrade/2010-02-21-mysql-upgrade.en.txt @@ -0,0 +1,25 @@ +Title: MySQL 5.1 unmasking and upgrade procedures +Author: Robin H. Johnson <robbat2@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-21-mysql-upgrade/2010-02-21-mysql-upgrade.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-21-mysql-upgrade/2010-02-21-mysql-upgrade.en.txt.asc new file mode 100644 index 0000000..5a7907f --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-21-mysql-upgrade/2010-02-21-mysql-upgrade.en.txt.asc @@ -0,0 +1,11 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.14 (GNU/Linux) + +iQEcBAABAgAGBQJLhcdhAAoJEAb1tEFm2PSbthsH/RGzbLrUB7ntcat34WjqH6KS +4c+5pCvUWzkgvdfFJ36N9P7BOO1M65ObU2mS6b65nXIWt88Jii76HPZvBN+93MIQ +utvQn0Isbc2/g7CYFQZTgPxckCouV5PPicow57Qtz1K48wAIRhxZOVGh3cn0XGnB +wAgUwaP84msVdVvGdjV91OZWo+rwqOV0NuSqOhODifzUNdpbdWFcaqq8gFG68dtv +fxZpwvzkcbrTN9QAQdN3ZuLKoB4VuRa0/LVrainE7RpGC35DfthcdF/nGhTrNsPh +8vy8LLAreAhuEdrs0N8c8Mwwda4kYK1+Eqo57GLkMH9nPIDX96OyCzwx1MYI20c= +=yeaI +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt new file mode 100644 index 0000000..5726373 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt @@ -0,0 +1,41 @@ +Title: Layman storage path changed from version 1.3.0 on +Author: Sebastian Pipping <sping@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt.asc new file mode 100644 index 0000000..fbbc34c --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.14 (GNU/Linux) + +iEYEABECAAYFAkuOvSAACgkQsAvGakAaFgDdGQCgjQyWt7Kwyh1oz7rxjQPQwOhZ +NjUAoJyuoTYVBDiHNGWs8oUO9N23DTDD +=xNpZ +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt new file mode 100644 index 0000000..71bf128 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt @@ -0,0 +1,35 @@ +Title: MythTV 0.22 Upgrade Database Corruption +Author: Richard Freeman <rich0@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt.asc new file mode 100644 index 0000000..bbd1eb6 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.14 (GNU/Linux) + +iEYEABECAAYFAkuL40EACgkQG4/rWKZmVWkOnwCgvK30dQq5EPyM8iIaOG+zVZ/O +u+AAn3M3eKhP3VUZN5pAEZoOPX4CiuZc +=cxr8 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-23-new-subprofiles/2010-03-23-new-subprofiles.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-23-new-subprofiles/2010-03-23-new-subprofiles.en.txt new file mode 100644 index 0000000..550c33d --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-23-new-subprofiles/2010-03-23-new-subprofiles.en.txt @@ -0,0 +1,31 @@ +Title: New desktop subprofiles for GNOME and KDE +Author: Theo Chatzimichos <tampakrap@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-23-new-subprofiles/2010-03-23-new-subprofiles.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-23-new-subprofiles/2010-03-23-new-subprofiles.en.txt.asc new file mode 100644 index 0000000..27b3e91 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-23-new-subprofiles/2010-03-23-new-subprofiles.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.14 (GNU/Linux) + +iEYEABECAAYFAkuozkIACgkQjDdoMVfcAHj2wACggGPTFK+Mjso7voU543VcfK0k +e6gAoMWlSU+lI2R/8/X+wC87YmCinnwW +=EbUf +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-25-python-3.1/2010-03-25-python-3.1.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-25-python-3.1/2010-03-25-python-3.1.en.txt new file mode 100644 index 0000000..13533ec --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-25-python-3.1/2010-03-25-python-3.1.en.txt @@ -0,0 +1,28 @@ +Title: Python 3.1 +Author: Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-25-python-3.1/2010-03-25-python-3.1.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-25-python-3.1/2010-03-25-python-3.1.en.txt.asc new file mode 100644 index 0000000..c910489 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-03-25-python-3.1/2010-03-25-python-3.1.en.txt.asc @@ -0,0 +1,17 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.15 (GNU/Linux) + +iQIcBAABAgAGBQJLq9kmAAoJEFtpjAED8H0Yu/0QAMnsuG64BTJ10p7vFEafqNhu +fkKTuvxOHw2dCJ1BClaIpDgJXxB0mf+/g6FoGJXrKEXANe5MUYrvLVxFDsayHxQH +SWKyu8MQD80BMGNJBLUNdTPInGqOMWBkTSzAN4KOEldc3pjfaxNLTS7it0nxQR6u +LcatSnOZbS0Isy6ZE7BwLURQtKer4EEr+iBS8jupDx0YZ7YIJArhM0Xxtnyc66ic +Y8oje1srUR2Qo8Phu+gmD1Qyx+27P3Q8vMjFGUi4YHD6clT3f0bmwwbDMLkowyIh +JlMqz9qFumGffMqTC4j1vNn8icvy8y4Rs315SMtJ82+H8MsR1KpWO9C66ZTQKBqp +ym2979PXOTIoInKuHnBwwf6Se5aGxqZK2KEKBi0jcjZIrrlNmAmxSGZrZH+9t5db +3Sj1BnZXHUvn1egrbdXSEyfWwheU2ekYfWagp0QFzoEZQNlvaoBEMUno9u8qobYO +mXx/SEiggBftXFvdDPOVfLQyG6KQIIj/I74OLttUvzI33/G2T8VCzSs/VJQ7D7Us +WKuQjZDwQ932w9fxvMSAXiZ3q6bAc4DsLQUPq515fRqkyYG1wAvMA9DaBGx6ykIh +Sr0pZKsugxV6W4GoM/D48fIxMn30Of/lsbs9bxh+wf0jgGuJO9mhshz6ifRzVnhJ +SCdOcQp4CFOIpUaCl1s/ +=BedG +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-05-02-gnome-228/2010-05-02-gnome-228.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-05-02-gnome-228/2010-05-02-gnome-228.en.txt new file mode 100644 index 0000000..177e160 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-05-02-gnome-228/2010-05-02-gnome-228.en.txt @@ -0,0 +1,18 @@ +Title: Upgrade to GNOME 2.28 +Author: Pacho Ramos <pacho@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-05-02-gnome-228/2010-05-02-gnome-228.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-05-02-gnome-228/2010-05-02-gnome-228.en.txt.asc new file mode 100644 index 0000000..69e2705 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-05-02-gnome-228/2010-05-02-gnome-228.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.14 (GNU/Linux) + +iEYEABECAAYFAkvdgwsACgkQCaWpQKGI+9R+2QCeOdXAtmfm2U0atYWvcbWpwLuA +1JkAnjXChfLI9ex9/M4i2h7nWYSjv8bE +=3EwM +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-22-perl-5.12-upgrade-procedure/2010-10-22-perl-5.12-upgrade-procedure.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-22-perl-5.12-upgrade-procedure/2010-10-22-perl-5.12-upgrade-procedure.en.txt new file mode 100644 index 0000000..0be2ab3 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-22-perl-5.12-upgrade-procedure/2010-10-22-perl-5.12-upgrade-procedure.en.txt @@ -0,0 +1,27 @@ +Title: Perl 5.12 upgrade procedure +Author: perl-team <perl@gentoo.org> +Author: Torsten Veller <tove@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-22-perl-5.12-upgrade-procedure/2010-10-22-perl-5.12-upgrade-procedure.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-22-perl-5.12-upgrade-procedure/2010-10-22-perl-5.12-upgrade-procedure.en.txt.asc new file mode 100644 index 0000000..dab8d61 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-22-perl-5.12-upgrade-procedure/2010-10-22-perl-5.12-upgrade-procedure.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.16 (GNU/Linux) + +iEYEABEDAAYFAkzBvtAACgkQu8cU0ZxnzZbfGgCfdoVC9zHTWTLyIAd5bro3KfRX +WCMAn0Nnmwu6OtdwjXo1LCNIhTJQGYPR +=7NH5 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-27-hardened-gcc4-info/2010-10-27-hardened-gcc4-info.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-27-hardened-gcc4-info/2010-10-27-hardened-gcc4-info.en.txt new file mode 100644 index 0000000..6ca9522 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-27-hardened-gcc4-info/2010-10-27-hardened-gcc4-info.en.txt @@ -0,0 +1,20 @@ +Title: Info about GCC on Hardened profiles +Author: Magnus Granberg <zorry@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-27-hardened-gcc4-info/2010-10-27-hardened-gcc4-info.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-27-hardened-gcc4-info/2010-10-27-hardened-gcc4-info.en.txt.asc new file mode 100644 index 0000000..de29fae --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-10-27-hardened-gcc4-info/2010-10-27-hardened-gcc4-info.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.16 (GNU/Linux) + +iEYEABECAAYFAkzIfYoACgkQe6JQqv15gH+78wCeOAb9Zcrc0tkdwZ+jDHptV0tY +EIwAnAzAulXlRTi9jMD/qtFuP9G152Es +=clyW +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-11-13-hardened-profiles/2010-11-13-hardened-profiles.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-11-13-hardened-profiles/2010-11-13-hardened-profiles.en.txt new file mode 100644 index 0000000..98c7378 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-11-13-hardened-profiles/2010-11-13-hardened-profiles.en.txt @@ -0,0 +1,51 @@ +Title: Restructuring of Hardened profiles +Author: Anthony G. Basile <blueness@gentoo.org> +Author: Hardened Team <hardened@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-11-13-hardened-profiles/2010-11-13-hardened-profiles.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-11-13-hardened-profiles/2010-11-13-hardened-profiles.en.txt.asc new file mode 100644 index 0000000..2cc1c32 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2010-11-13-hardened-profiles/2010-11-13-hardened-profiles.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.16 (GNU/Linux) + +iEYEABECAAYFAkzd0sIACgkQl5yvQNBFVTWYtACeK1qkaZV+A54CzEptE0Cx6jfS ++mQAni5jgmmZyXjE+2Np6KrSaU96AhJg +=597m +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-13-libgphoto2-2.4.10/2011-02-13-libgphoto2-2.4.10.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-13-libgphoto2-2.4.10/2011-02-13-libgphoto2-2.4.10.en.txt new file mode 100644 index 0000000..d599f3a --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-13-libgphoto2-2.4.10/2011-02-13-libgphoto2-2.4.10.en.txt @@ -0,0 +1,14 @@ +Title: Change on CAMERAS in libgphoto2-2.4.10 +Author: Pacho Ramos <pacho@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-13-libgphoto2-2.4.10/2011-02-13-libgphoto2-2.4.10.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-13-libgphoto2-2.4.10/2011-02-13-libgphoto2-2.4.10.en.txt.asc new file mode 100644 index 0000000..d720f35 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-13-libgphoto2-2.4.10/2011-02-13-libgphoto2-2.4.10.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.16 (GNU/Linux) + +iEYEABECAAYFAk1cKuUACgkQCaWpQKGI+9QUbgCfazP4Oi9uPb+hel+TF4gB5+2n +FQIAn2lRnik8RyvyuunDYHEI000/lPH6 +=rC6K +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-14-gnome-232/2011-02-14-gnome-232.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-14-gnome-232/2011-02-14-gnome-232.en.txt new file mode 100644 index 0000000..47c1216 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-14-gnome-232/2011-02-14-gnome-232.en.txt @@ -0,0 +1,17 @@ +Title: Upgrade to GNOME 2.32 +Author: Pacho Ramos <pacho@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-14-gnome-232/2011-02-14-gnome-232.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-14-gnome-232/2011-02-14-gnome-232.en.txt.asc new file mode 100644 index 0000000..75a4374 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-14-gnome-232/2011-02-14-gnome-232.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.16 (GNU/Linux) + +iEYEABECAAYFAk1eT8AACgkQCaWpQKGI+9RljgCeKZVOkFezzGVM0Ecm0+vfOthi +PDsAoIgDcqNGfpVjWWOx0InjpHIl6rNE +=27Uh +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-19-ia64-java-removal/2011-02-19-ia64-java-removal.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-19-ia64-java-removal/2011-02-19-ia64-java-removal.en.txt new file mode 100644 index 0000000..eb45778 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-19-ia64-java-removal/2011-02-19-ia64-java-removal.en.txt @@ -0,0 +1,19 @@ +Title: Pending Removal of Java support on IA64 +Author: Petteri Räty <betelgeuse@gentoo.org> +Author: IA64 Arch Team <ia64@gentoo.org> +Author: Vlastimil Babka <caster@gentoo.org> +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@gentoo.org. +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-19-ia64-java-removal/2011-02-19-ia64-java-removal.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-19-ia64-java-removal/2011-02-19-ia64-java-removal.en.txt.asc new file mode 100644 index 0000000..e101716 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-02-19-ia64-java-removal/2011-02-19-ia64-java-removal.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.17 (GNU/Linux) + +iEYEABECAAYFAk1gDJQACgkQtbrAj05h3oTUwQCdFs0d8GKacr0N1YgjYItjq2rd +ETEAoJOdsWyC3FOeCab4qqOWzXwdyAaF +=Voef +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-26-gnustep-new-layout/2011-04-26-gnustep-new-layout.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-26-gnustep-new-layout/2011-04-26-gnustep-new-layout.en.txt new file mode 100644 index 0000000..ca24ef6 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-26-gnustep-new-layout/2011-04-26-gnustep-new-layout.en.txt @@ -0,0 +1,20 @@ +Title: GNUstep packages new layout +Author: Bernard Cafarelli <voyageur@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-26-gnustep-new-layout/2011-04-26-gnustep-new-layout.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-26-gnustep-new-layout/2011-04-26-gnustep-new-layout.en.txt.asc new file mode 100644 index 0000000..a0ea322 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-26-gnustep-new-layout/2011-04-26-gnustep-new-layout.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.17 (GNU/Linux) + +iEYEABECAAYFAk22aOQACgkQDhqwQZQ3nG1KBACgxlCsdp4ZqbrNpqaqlr4+dtwy +4XMAoPdOdaZjx8WrcIAgsmpAcY7jX+yn +=k9ts +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-27-glib-228/2011-04-27-glib-228.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-27-glib-228/2011-04-27-glib-228.en.txt new file mode 100644 index 0000000..823413d --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-27-glib-228/2011-04-27-glib-228.en.txt @@ -0,0 +1,37 @@ +Title: Upgrade to GLIB 2.28 +Author: The Gentoo Freedesktop Maintainers <freedesktop-bugs@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-27-glib-228/2011-04-27-glib-228.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-27-glib-228/2011-04-27-glib-228.en.txt.asc new file mode 100644 index 0000000..09d3807 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-04-27-glib-228/2011-04-27-glib-228.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.17 (GNU/Linux) + +iF4EABEIAAYFAk24GZUACgkQXkR9YqOcLPGctQD+PNPuMTfAVuGohxvERLACizzd +C1tDzUulrtJB6sougLUA/ilqcRP8fQYpa2NMlPjIi27ZYTXIvMcxD3MOi/04wnh3 +=pv0a +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-05-01-baselayout-update/2011-05-01-baselayout-update.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-05-01-baselayout-update/2011-05-01-baselayout-update.en.txt new file mode 100644 index 0000000..d4b7689 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-05-01-baselayout-update/2011-05-01-baselayout-update.en.txt @@ -0,0 +1,29 @@ +Title: Baselayout update +Author: Christian Faulhammer <fauli@gentoo.org> +Author: William Hubbs <williamh@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-05-01-baselayout-update/2011-05-01-baselayout-update.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-05-01-baselayout-update/2011-05-01-baselayout-update.en.txt.asc new file mode 100644 index 0000000..2d26fed --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-05-01-baselayout-update/2011-05-01-baselayout-update.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.17 (GNU/Linux) + +iEYEABECAAYFAk29qS4ACgkQblQW9DDEZTirrwCfckYo58Afhu72Nq+/IuRMy0J6 +vz4An3WBBCPZPV2ViEoszjssk54sOuke +=ZZvG +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-08-28-mesa-r600g/2011-08-28-mesa-r600g.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-08-28-mesa-r600g/2011-08-28-mesa-r600g.en.txt new file mode 100644 index 0000000..110f330 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-08-28-mesa-r600g/2011-08-28-mesa-r600g.en.txt @@ -0,0 +1,26 @@ +Title: Mesa r600 driver now defaults to gallium +Author: Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-08-28-mesa-r600g/2011-08-28-mesa-r600g.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-08-28-mesa-r600g/2011-08-28-mesa-r600g.en.txt.asc new file mode 100644 index 0000000..4db04f6 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-08-28-mesa-r600g/2011-08-28-mesa-r600g.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.17 (GNU/Linux) + +iEYEABECAAYFAk5aqBAACgkQ+gvH2voEPRDumwCeMZU6+GY8ZMDbLE0h3wREQ1Ct +HXkAmwS2j0l8KMg6hgOs1lK7/OlREpep +=4flS +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-10-15-libpng15/2011-10-15-libpng15.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-10-15-libpng15/2011-10-15-libpng15.en.txt new file mode 100644 index 0000000..d5c3f27 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-10-15-libpng15/2011-10-15-libpng15.en.txt @@ -0,0 +1,32 @@ +Title: Upgrade to libpng15 +Author: Samuli Suominen <ssuominen@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-10-15-libpng15/2011-10-15-libpng15.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-10-15-libpng15/2011-10-15-libpng15.en.txt.asc new file mode 100644 index 0000000..43e149c --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-10-15-libpng15/2011-10-15-libpng15.en.txt.asc @@ -0,0 +1,11 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.18 (GNU/Linux) + +iQEcBAABAgAGBQJOmb86AAoJEEdUh39IaPFNvlUH/0h02Ya8pAc8GlFt1pxFCSEd +Hqdu8Fx8eVtIjAo9/9mumUl4Syor9awVpfhbh2fo6WQG1BK8Dflo4jQwzLekidge +lHJYzB5dkscho8+PlWBCXNQQB8V0o+3L7h23K4M+rXJJGKfDZOIX1R3+XlffYaQY +T3lki4vr0WE3oA2D8R3BZGKTtMEvm4Rqm+oFZBQo7rmueLHlCXiUjFX3SeydA8ha +t+I69rx3bgqA3hpcnINS5VUKgDJP/x8YjVEook7JnUHif5Al4CWJ8vT9GmDEh/HD +n9TKFRLMDY73TMAPiqSQCdt3L7ZkBlhVYaQIvWdUl7SjO7lIJsw62MaM3f0qxL0= +=Hapc +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-11-27-gnome3-unmask/2011-11-27-gnome3-unmask.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-11-27-gnome3-unmask/2011-11-27-gnome3-unmask.en.txt new file mode 100644 index 0000000..7077a66 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-11-27-gnome3-unmask/2011-11-27-gnome3-unmask.en.txt @@ -0,0 +1,16 @@ +Title: Unmasking of and Upgrade to GNOME 3.2 +Author: Nirbheek Chauhan <nirbheek@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-06-kde473-kdepim/2011-12-06-kde473-kdepim.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-06-kde473-kdepim/2011-12-06-kde473-kdepim.en.txt new file mode 100644 index 0000000..2565795 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-06-kde473-kdepim/2011-12-06-kde473-kdepim.en.txt @@ -0,0 +1,29 @@ +Title: Stabilization of KDE 4.7.3 including KDEPIM +Author: Andreas K. Huettel <dilfridge@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-06-kde473-kdepim/2011-12-06-kde473-kdepim.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-06-kde473-kdepim/2011-12-06-kde473-kdepim.en.txt.asc new file mode 100644 index 0000000..91d9084 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-06-kde473-kdepim/2011-12-06-kde473-kdepim.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.17 (GNU/Linux) + +iEYEABECAAYFAk7eomEACgkQ3ao2Zwy3NWoqyQCdGpnoHNJkA2B9b0X+SrB/LM09 +VJgAn2qyL0wgbeLvuchXwdUcauD1PqLG +=9Nxz +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-30-bacula-updates/2011-12-30-bacula-updates.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-30-bacula-updates/2011-12-30-bacula-updates.en.txt new file mode 100644 index 0000000..269dfa9 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-30-bacula-updates/2011-12-30-bacula-updates.en.txt @@ -0,0 +1,27 @@ +Title: Bacula-5.2.3 Upgrade +Author: Thomas Beierlein <tomjbe@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-30-bacula-updates/2011-12-30-bacula-updates.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-30-bacula-updates/2011-12-30-bacula-updates.en.txt.asc new file mode 100644 index 0000000..d0ee088 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2011-12-30-bacula-updates/2011-12-30-bacula-updates.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.17 (GNU/Linux) + +iEYEABECAAYFAk8Blp4ACgkQQe4uqXYgU9W9dACfSLfOG5hslRDESU/GHpIjK6Mh +Ik4An3XlqvvXhotd/GLUgFwnKrYulM8T +=2shN +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-02-14-baselayout-1-deprecation/2012-02-14-baselayout-1-deprecation.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-02-14-baselayout-1-deprecation/2012-02-14-baselayout-1-deprecation.en.txt new file mode 100644 index 0000000..d5f671c --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-02-14-baselayout-1-deprecation/2012-02-14-baselayout-1-deprecation.en.txt @@ -0,0 +1,30 @@ +Title: baselayout-1.x deprecation +Author: William Hubbs <williamh@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-02-14-baselayout-1-deprecation/2012-02-14-baselayout-1-deprecation.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-02-14-baselayout-1-deprecation/2012-02-14-baselayout-1-deprecation.en.txt.asc new file mode 100644 index 0000000..fc65e78 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-02-14-baselayout-1-deprecation/2012-02-14-baselayout-1-deprecation.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.17 (GNU/Linux) + +iEYEABECAAYFAk85qogACgkQblQW9DDEZTh6ZwCgmx7TZK37O8llvFULSKacne9K +CVUAnjin57OjSiVqfBSD2DIlzjzIYZll +=EzBo +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-04-24-libjpeg-turbo-by-default/2012-04-24-libjpeg-turbo-by-default.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-04-24-libjpeg-turbo-by-default/2012-04-24-libjpeg-turbo-by-default.en.txt new file mode 100644 index 0000000..512b32f --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-04-24-libjpeg-turbo-by-default/2012-04-24-libjpeg-turbo-by-default.en.txt @@ -0,0 +1,19 @@ +Title: The default JPEG implementation +Author: Samuli Suominen <ssuominen@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-04-24-libjpeg-turbo-by-default/2012-04-24-libjpeg-turbo-by-default.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-04-24-libjpeg-turbo-by-default/2012-04-24-libjpeg-turbo-by-default.en.txt.asc new file mode 100644 index 0000000..22ceb1e --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-04-24-libjpeg-turbo-by-default/2012-04-24-libjpeg-turbo-by-default.en.txt.asc @@ -0,0 +1,11 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.19 (GNU/Linux) + +iQEbBAABAgAGBQJPltPcAAoJEEdUh39IaPFNc1wH9imsiRDmxp629KBQpxQ7aj+o +U6IxzLLDKWciNFa+NNlqPB6/YT6R1j4ikjR4KdQU/WPkuDms6EWhLbkvZ001dJVB +/yaVmP+SLlbd7mMwGUtv7P/1Iz1/YKIzddjUEQS3Lh7T0WMuP9tnGncP7lsjICcb +5mFF3hg+97rl9oNwPdIe5KmiNWH47JPbg+BjHAyR10LKE9ZGKMg7/yXIwD0/3xyY +37mq52FTyEs6KEsiN6vCQfEdUjfbxkdV+uTbCLlCyGORd6kYTARAjXQ++qfZbGTh +C7HI5nyoccafMGAUlMMPO7j3/jt1OJ6u6hO9TLrg1RXHNLq4HRrq+IxYbULe9w== +=Wzu7 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-07-23-upgrading-postfix/2012-07-23-upgrading-postfix.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-07-23-upgrading-postfix/2012-07-23-upgrading-postfix.en.txt new file mode 100644 index 0000000..f9cb0e4 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-07-23-upgrading-postfix/2012-07-23-upgrading-postfix.en.txt @@ -0,0 +1,13 @@ +Title: Upgrading to postfix-2.9 +Author: Eray Aslan <eras@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-07-23-upgrading-postfix/2012-07-23-upgrading-postfix.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-07-23-upgrading-postfix/2012-07-23-upgrading-postfix.en.txt.asc new file mode 100644 index 0000000..ad76a8b --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2012-07-23-upgrading-postfix/2012-07-23-upgrading-postfix.en.txt.asc @@ -0,0 +1,17 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.19 (GNU/Linux) + +iQIcBAABCAAGBQJQDWUdAAoJEHfx8XVYajsf5eMP/jkGOtKa1NUq9s60O0KnklMs +nZOlN2mCMc9ZKP6fXtNUMYE8pskB/VBOYtfqr9BFROMZPGaIf1VoZ0C11xswGmqZ +z61W7xY/4AT5RWtq2405onQ0mO82AVZP8A8cNZH1+ISLPRTayVwdsCgU1ANeORL0 +n9C7nP8IrRZShGHupf7jWAyBZQ8rbhlct2awu63GxREq5ifswOY50jzlyK9iTfyH +TdiuhLfrFQb/SZYWSrXRBrDpLZARLk6ZWGDJ+tYSQ10lB6E9ELaxUwC/v98ds2d1 +oQfqqasq1/H2FoZ54bUY7iwnXtohgKxmwEOU6tjtqcJiyTBNXD2ZXYkJKo5e3P3n +yAvls+1lURhJB7X3gyD1B6x2a1N4stQvxcWx4yzXf04IrYLAgeOmQdKDQ5AkPKkW +T9Lr7uLFGbeHYS1wNAXqfHpIvS9Rod+oOLtCBdR65chrw6J5imBx6KV/2cmC6Qka +2hpAT0IYvcvC11pS6armeGeWA7kR1lesPjflxpjRyTumP1vd183NZU8jq7C7c5ua +nGB79VCo9GarkrHStOdEt/R2bAE6Kforx4TeqOVIqlnInFE7TY6LCeuZlXfO5I+6 +nargDJ+cBlyuSTUOQM0MvQMBCIYKXHjKfZIpRqFGb7Hw0Gide5lGTZS2KV4TnJCw +UXYXR52bF2QqSzNskicz +=tW4I +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles-server/2013-02-10-new-13-profiles-server.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles-server/2013-02-10-new-13-profiles-server.en.txt new file mode 100644 index 0000000..999f73c --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles-server/2013-02-10-new-13-profiles-server.en.txt @@ -0,0 +1,41 @@ +Title: New 13.0 profiles and deprecation of 10.0 profiles +Author: Andreas K. Huettel <dilfridge@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles-server/2013-02-10-new-13-profiles-server.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles-server/2013-02-10-new-13-profiles-server.en.txt.asc new file mode 100644 index 0000000..5918844 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles-server/2013-02-10-new-13-profiles-server.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.19 (GNU/Linux) + +iEYEABECAAYFAlEYCxgACgkQ3ao2Zwy3NWoD1QCfTcD675ieLYh4j17Bvl4z3oM2 +Ty8AniisMcIwn/wqgT8H82Va5O/zjwgd +=+fiB +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles/2013-02-10-new-13-profiles.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles/2013-02-10-new-13-profiles.en.txt new file mode 100644 index 0000000..63aca0c --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles/2013-02-10-new-13-profiles.en.txt @@ -0,0 +1,116 @@ +Title: New 13.0 profiles and deprecation of 10.0 profiles +Author: Andreas K. Huettel <dilfridge@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles/2013-02-10-new-13-profiles.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles/2013-02-10-new-13-profiles.en.txt.asc new file mode 100644 index 0000000..0a950a1 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-02-10-new-13-profiles/2013-02-10-new-13-profiles.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.19 (GNU/Linux) + +iEYEABECAAYFAlEYCvsACgkQ3ao2Zwy3NWorsgCaA2lhzK6vdHa+SFtd92EWqiXs +A/MAoKMchhhqhC9HZUXb9xWhq8sh5TBN +=sBhY +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt new file mode 100644 index 0000000..2816d06 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt @@ -0,0 +1,102 @@ +Title: Upgrading udev to version >=200 +Author: Samuli Suominen <ssuominen@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt.asc new file mode 100644 index 0000000..d2edaa6 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt.asc @@ -0,0 +1,11 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.19 (GNU/Linux) + +iQEcBAABAgAGBQJRWGlJAAoJEEdUh39IaPFNDCgIAKF6HMthMqbM8EiFk+0MGRGi +83HOlEve6rOqYUQVg8ziSQXD4S8EqgvPIBBh8SWnKq4wfsr5ARpooyFMFXPTLiW6 +na4SJeDwPUkMSG9wUObnAen6xsY5GRpJ5XE3FLvCYnsH7kxzcPw2Ys1XE6plXUfN +hmH5jIAV5P9dmkcaIfYXYIpECy3oUH+dwhMfKoSYSy4rs2XSuOdRgaTeQ3pL1kdR +SdYkLa+MLQuR3937CosIUFdekKRfIiiC4ysxnF1EemSl//Adr95H01YfPKRm11qm +Q4AqfLSrGJYJH+uS0qLSxnwptTqtKm6S3Gdw1Dcfas4OAxn+vXc/rqlZD6M5qZE= +=lqMR +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-04-10-baselayout-1-deprecation-final-warning/2013-04-10-baselayout-1-deprecation-final-warning.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-04-10-baselayout-1-deprecation-final-warning/2013-04-10-baselayout-1-deprecation-final-warning.en.txt new file mode 100644 index 0000000..331d36f --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-04-10-baselayout-1-deprecation-final-warning/2013-04-10-baselayout-1-deprecation-final-warning.en.txt @@ -0,0 +1,32 @@ +Title: baselayout-1.x deprecation final warning +Author: William Hubbs <williamh@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-04-10-baselayout-1-deprecation-final-warning/2013-04-10-baselayout-1-deprecation-final-warning.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-04-10-baselayout-1-deprecation-final-warning/2013-04-10-baselayout-1-deprecation-final-warning.en.txt.asc new file mode 100644 index 0000000..35d96de --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-04-10-baselayout-1-deprecation-final-warning/2013-04-10-baselayout-1-deprecation-final-warning.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.19 (GNU/Linux) + +iEYEABECAAYFAlFl1FgACgkQblQW9DDEZTiiNgCghjfUOZMgWNMEXUHC6cGfW9JL +9HcAn2INJT3R6Mqoge7ofSSo1uub3HX8 +=GANE +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-01-mysql-pbxt-dropped/2013-06-01-mysql-pbxt-dropped.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-01-mysql-pbxt-dropped/2013-06-01-mysql-pbxt-dropped.en.txt new file mode 100644 index 0000000..1f7293a --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-01-mysql-pbxt-dropped/2013-06-01-mysql-pbxt-dropped.en.txt @@ -0,0 +1,41 @@ +Title: PBXT now unsupported in MySQL/MariaDB +Author: Robin H. Johnson <robbat2@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-01-mysql-pbxt-dropped/2013-06-01-mysql-pbxt-dropped.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-01-mysql-pbxt-dropped/2013-06-01-mysql-pbxt-dropped.en.txt.asc new file mode 100644 index 0000000..f8335a3 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-01-mysql-pbxt-dropped/2013-06-01-mysql-pbxt-dropped.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0 + +iQJ8BAABCgBmBQJV9cJNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMDlCNDQ4NjEyNDI4NjA5REVEMDI3MzIy +MjBDRDFDNUJERUVEMDIwAAoJECIM0cW97tAgz6IQAPV2aSEUcOFY1OhfMJ+pTr+J +Q88MZAiPafCX2yXhCZb08MwQ+DtVaDE9xfNUoSbXFUmxUP5snCd61eMvY0ptHS+E +T5/GinrmtAe9wqzaWfVlWEMW4gzVmBjfqpfIKVgex/PkXZbXtZug4P8XOcXNVavD +3di7WBa/Vaqcrmz9yGOAt5mojUufTz0gARo4rgu+sMJUNYBO+JeGxjcXSqy0dMas +y5QT2PSLnr2Sx1vU3lTctcbiN/PN9PPeEBpKeTh40dOgXrCvhnGNSKh4noREC/tR +Gvp8OeXFbiA635o5SbFtdijD9nRK8clsj8zuNYfPvWQ9u+5qGXME8yYAOgefqO8B +6lipVkbxDuX3FfO280CZMgsxOQ0N+FRWXD8LZcf4trvWdCfnwSvcIuoSwKXobWND +cg03wjJA8HFXbjqkoqIbZWf7Uxp/RRv4xhaNdL1oYTTwSLiWyJjXUje80ymLFzbD +d9TFhAib6IAPi9u+JQphE4fh/JSwM7hGqWTyDTwrKxDVDXWo3CLZ/GsgGtdTdEcA +j3mxgUhpihlxkZ7hYQQCvdwlr61zj0F8wGVvLAXzdELzwQFzrsx+JkGmSF6h7PhR +EZgaWZcKfQTSnBT5rDlul+no2wnLwxWGcRKwrtDeMlJ3xRcrgo/ojhSL4XwVz7Hc +mtAeEFd1VzjjA/q8H5Tm +=EMHo +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-30-cups16/2013-06-30-cups16.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-30-cups16/2013-06-30-cups16.en.txt new file mode 100644 index 0000000..ba72857 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-30-cups16/2013-06-30-cups16.en.txt @@ -0,0 +1,21 @@ +Title: Printer browsing in net-print/cups-1.6 +Author: Andreas K. Huettel <dilfridge@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-30-cups16/2013-06-30-cups16.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-30-cups16/2013-06-30-cups16.en.txt.asc new file mode 100644 index 0000000..3ad2386 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-06-30-cups16/2013-06-30-cups16.en.txt.asc @@ -0,0 +1,17 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.19 (GNU/Linux) + +iQIcBAABCgAGBQJR0CggAAoJEJS/30SErRQv+RcP/2huylbV/5l5BaVuoS6Yy2za +8+DcVeFqKxk6OxSEzJx/yrnjWhHlSJxJ4BjXqB5EtwmWjeq4njqzYOUH2BZpeXNv +IprD/Qc16TXVB1YYMlXrbgriLdBzUABW62Y4JO9AJ10kz2h5ze913veTVC7aN5w3 +FCvQ3N206BzjTPij+10HCPnOkCbTDkLbObi8IHVEB3LmUUcLsu6qOPkBA2xFuUlr +87f1LgazwhYZdDxZS0/kStdLUKioW4xkSXLzzWKP1QVjBABTvIVfgVgkEWE0UA5S +998+NGwNfAbEwM/gIQroiXraNCFS1fVc5/8SG0AbfpD53990itJjrM9C63XgTzbS +aYihy1+nU4MGJIy8kzSXGkp5VKOTO+5k+bqIZ3vf5Ou09sMbVvIf/eYMwzCwG4oi +T355hp5XJe18d9WhDr1Ebe/8Z6gTgM2lQ49/ORN6lKYhU98WjINbeEpcU0auNLJ/ +M9Ww6RfgiuTWd3r7Wia8H8coGqSCne5cC9rknxNATgievFobS1tVyns/mFj/FjzW +DuYcCtzvZvh+TUrlrApiWgQep6RDO7+oLhlmYy6ZJkmwzBDuuWnAzLEtxPgJg0nF +DmvwkL16t/uC1TnMZ5Np4rfo7pEYlCNnUZ6dNxF8yThGto6uAKcQOTUC8AbFW1Oq +pzhzSpiHtNnoQAolWbIn +=4eE2 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-08-07-vanilla-sources-stablization-policy/2013-08-07-vanilla-sources-stablization-policy.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-08-07-vanilla-sources-stablization-policy/2013-08-07-vanilla-sources-stablization-policy.en.txt new file mode 100644 index 0000000..75158ec --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-08-07-vanilla-sources-stablization-policy/2013-08-07-vanilla-sources-stablization-policy.en.txt @@ -0,0 +1,26 @@ +Title: vanilla-sources stabilization policy +Author: Mike Pagano <mpagano@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-08-07-vanilla-sources-stablization-policy/2013-08-07-vanilla-sources-stablization-policy.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-08-07-vanilla-sources-stablization-policy/2013-08-07-vanilla-sources-stablization-policy.en.txt.asc new file mode 100644 index 0000000..15d4273 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-08-07-vanilla-sources-stablization-policy/2013-08-07-vanilla-sources-stablization-policy.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.20 (GNU/Linux) + +iEYEABEIAAYFAlIC3doACgkQPDPGULV25OPdCQCgkpul7iG1gHDz/3g2Moiyzf1e +7RcAoMSXVGgEojsUoeQxA4UZXGaTcs/o +=I2Cp +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-22-minor-arches-1/2013-09-22-minor-arches-1.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-22-minor-arches-1/2013-09-22-minor-arches-1.en.txt new file mode 100644 index 0000000..c6fc3ac --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-22-minor-arches-1/2013-09-22-minor-arches-1.en.txt @@ -0,0 +1,28 @@ +Title: m68k, s390, sh are dropping stable keywords +Author: Andreas K. Huettel <dilfridge@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-22-minor-arches-1/2013-09-22-minor-arches-1.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-22-minor-arches-1/2013-09-22-minor-arches-1.en.txt.asc new file mode 100644 index 0000000..6ab5d8c --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-22-minor-arches-1/2013-09-22-minor-arches-1.en.txt.asc @@ -0,0 +1,17 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.20 (GNU/Linux) + +iQIcBAABCgAGBQJSPqvGAAoJEJS/30SErRQvafkQAIRw7BNXe+/W0f3x57V/tWTq +59e17+HvKOIlhGAUZZUWYKcpZBy6pRCU1AW6U/rYBmHv1b2DQDylgR0ZS4kTv/nr +mcSmusINpbPRzfeJxsoy5SgZQpmIfUdfScAhgMQKybNBHGk/SrA3M1bYG1wSOwyY +0xoGfzcPHYVVmEY502U+pzgj6HQatdCkGv70dr/Rvy0AfkCydazCl8G7mbOs/qYY +Q6xB34zuwOgQDdMqGy+eEv8yzjuq3aR5oY2J0ylq7O0/ZDlZmr1sMF8M34WufG+0 +7JLjgc12ONo71TWRz+MwesK66yGXYReO01XySWhwYAOMzvbmBUQ8Bj2IZGri45DY +nMmg4gl1URjBzUkmbE72EspQb06HNzmPz0p5sw2qcWoi4aR2WJl20w6OYD3EYU/2 +4gjnX6T1DejDe7R4ht+5P+uoF9xUG0EZf9c2N00gU/CjiVHMJRI3MEWdvS90dVC5 +u2MUa8DD7LlgejsK3NMGmknCooL1HMiF7bG4osV1AvYCLDyUwa4Z+qmPYuCVHoeW +H+KBocLN6aSvoSYPuMte+b+yKM1rJYabdv2dVI6OXalDuWZvL1wZaQGeS05X4zBI +Brs2Z99M374VRiO67MdHcQwcEDqGhSrn/boC8rzRDaO3rgbqYjynaEcqbdfnk0up +0uSdI4dWKim6VRVkkudx +=5FmL +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt new file mode 100644 index 0000000..4f382a7 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt @@ -0,0 +1,29 @@ +Title: Separate /usr on Linux requires initramfs +Author: William Hubbs <williamh@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt.asc new file mode 100644 index 0000000..91b4564 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.20 (GNU/Linux) + +iEYEABECAAYFAlJE6s0ACgkQblQW9DDEZTh/NwCgnCgm1TzkYvnFjDHCshEizug7 +F9oAnRRaHINrygIfRkCFEAmZrxiWYaFL +=U3tK +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-14-grub2-migration/2013-10-14-grub2-migration.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-14-grub2-migration/2013-10-14-grub2-migration.en.txt new file mode 100644 index 0000000..d932346 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-14-grub2-migration/2013-10-14-grub2-migration.en.txt @@ -0,0 +1,31 @@ +Title: GRUB2 migration +Author: Mike Gilbert <floppym@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-14-grub2-migration/2013-10-14-grub2-migration.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-14-grub2-migration/2013-10-14-grub2-migration.en.txt.asc new file mode 100644 index 0000000..883bf5b --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-14-grub2-migration/2013-10-14-grub2-migration.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.22 (GNU/Linux) + +iF4EABEIAAYFAlJbNhAACgkQC77qH+pIQ6Q+8gD/e8WyG0T0N/9EmpwoC3apW3Ts +XpYq1n/LtYToVcZn5IUBAJjd/GPUj/gaFzuyk9Kfy87GJd4ZQLL9Leaf0jfkpzac +=heha +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-24-minor-arches-2/2013-10-24-minor-arches-2.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-24-minor-arches-2/2013-10-24-minor-arches-2.en.txt new file mode 100644 index 0000000..4f2e0a7 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-24-minor-arches-2/2013-10-24-minor-arches-2.en.txt @@ -0,0 +1,23 @@ +Title: alpha, ia64: maintainers may remove stable versions +Author: Andreas K. Huettel <dilfridge@gentoo.org> +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-24-minor-arches-2/2013-10-24-minor-arches-2.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-24-minor-arches-2/2013-10-24-minor-arches-2.en.txt.asc new file mode 100644 index 0000000..a1dc20e --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-10-24-minor-arches-2/2013-10-24-minor-arches-2.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.22 (GNU/Linux) + +iQJ8BAABCgBmBQJSaZFnXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwNzlCRDk4QzA4RENBRkYzQUEwRjQzMDlF +QkU2QTMzNkJFMTkwMzlDAAoJEOvmoza+GQOcBmMQAK6ZEvAc7jD9uqeFqFU+h2/Q +2FWSrRPTCLF7fhl8DQ5K/Irh9ti0TWxfSg+zgHzCP3b/ZRx4nZIFakKZ9WhxDbVH +qGXxL4LPp54izSQ5O6dK3b010v88rwKrQaWtI+alIOoiQy5L1lOLiGhgrv7eHVtz +TF7IEewQeXGySAmTW4xbmMERswsT50amUkvV9Ri2PIGdrBReZ6paO4aCGCkSBHef +MMVP0tM/3VfOaGfzBB/Eh4X0AOrd6wqe3kLIohZdo7pp+RH3aXPo69aLF1vXbi6v +PUWR9BkVaUnXyyoXAnPnT/NudGaptVp/jgVxsEicsWcxM5r9b2rDs5qC9LWFZm3B +p8P9SHv/mr/dz432tEG8Ik6gwel29sDqVeiepBqTY6aoHYutNdFEim7C20YHyJdq +YIOwbAzD/ECLyIGnjM2tnJVadCE8+vJym0FqldU6JvrrdLlxR23ushPBKmcASD5E +iXqsAyPM0+dqmFgz0KHiSp7nvmDxp64y4X8Rh+45FPoUcyior/gk399gwgqrd0jT +VAbM6SYYylqVq6T3GGefT0RtuUCr8SMpTLJQzdamKfn7+ckvg4IKhSFD45F5gIOk +YQbW4jWWlg8bmr0QC5Sb/cKCewLZlFXnImuSWJ4eLicDAXNHTI6VT3tz7sThQyIg +e3Yx76hV7gdSTQdM0umm +=lwoK +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-07-python-exec-package-move/2013-11-07-python-exec-package-move.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-07-python-exec-package-move/2013-11-07-python-exec-package-move.en.txt new file mode 100644 index 0000000..3e5536f --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-07-python-exec-package-move/2013-11-07-python-exec-package-move.en.txt @@ -0,0 +1,46 @@ +Title: python-exec package move +Author: Michał Górny <mgorny@gentoo.org> +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@lists.gentoo.org 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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-07-python-exec-package-move/2013-11-07-python-exec-package-move.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-07-python-exec-package-move/2013-11-07-python-exec-package-move.en.txt.asc new file mode 100644 index 0000000..8393678 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-07-python-exec-package-move/2013-11-07-python-exec-package-move.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.22 (GNU/Linux) + +iQJ8BAABCgBmBQJSfAuoXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC +MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZObdwP/2Yf2Lamrmwv2C/isim+j332 +TNJ/FjAdlP29Qbw0QBZ1+uXUGKIPpH1kLlPfK4qoxIdCh7vBEfqkQ0JCqXpqIjp8 +HleTguEc0eygn+ddg8k8Hj9s0EzrLTSpzP6GNyfvGVvESmaUoGig8xmaTH+Z6tGd +iHPpN1sFE4vh2sJmg0IO0nLNrMa0kf+enCAZOFpDTPFbS7lFu4xRqcFCI0FsdM7P +833iHwUDJ2tEWuZ3ajtSryJChQfE80RElxSKucMfXwhO6bYqjH2D/+Oy5UNs0zEE +bNHzWdKYMYxjyLd3vOQa9GIZ8YB83CN9JLnI5zcub67yagVWEM71g2Ll325V29dP +8shj5tmlHuwRXp+RMXSnifRh5EUt9rqg8Um1VuX1bt8XQ/RWZbAcprrWPafZnkOK +BPfzQ4qpFmP9GsdImHLYR1oqVBlNIVCImp2I2ToKDv+MgIXp3u55j8CsDARGoVNK +Pthf0HEqU/nW5z0GMQY0xOAhOPeED3YK2RMvwyei07WqbtRcEO2D/52oqq/8HKWb +4iyBf4YMMhdZjefUaVx2eBHTxxS4vV7h91gdcNml9yAsoYm3QowOwmUwafBv4Wj2 +5ijyaGQPO6dRA2N1+5lUYYaW9yqhFhRuNiNRHu7DqN8YrfwLm1NrTex3evcYBJve +USFV+7XtVAZYa+MBrk4d +=uG6F +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-23-gnome-38/2013-11-23-gnome-38.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-23-gnome-38/2013-11-23-gnome-38.en.txt new file mode 100644 index 0000000..11773fc --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-23-gnome-38/2013-11-23-gnome-38.en.txt @@ -0,0 +1,23 @@ +Title: Upgrade to GNOME 3.8 +Author: Pacho Ramos <pacho@gentoo.org> +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 diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-23-gnome-38/2013-11-23-gnome-38.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-23-gnome-38/2013-11-23-gnome-38.en.txt.asc new file mode 100644 index 0000000..3408f46 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2013-11-23-gnome-38/2013-11-23-gnome-38.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.22 (GNU/Linux) + +iEYEABECAAYFAlKQ8koACgkQCaWpQKGI+9T3MwCeLbN+r15EIbIZtgyv/S5eqyql +p0oAn0Yp/dLpxCAsJemLdn04uLMk7c9H +=eu02 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-02-25-udev-upgrade/2014-02-25-udev-upgrade.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-02-25-udev-upgrade/2014-02-25-udev-upgrade.en.txt new file mode 100644 index 0000000..9c37eee --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-02-25-udev-upgrade/2014-02-25-udev-upgrade.en.txt @@ -0,0 +1,28 @@ +Title: Upgrade to >=sys-fs/udev-210 +Author: Samuli Suominen <ssuominen@gentoo.org> +Content-Type: text/plain +Posted: 2014-02-25 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: <sys-fs/udev-210 + +The options CONFIG_FHANDLE and CONFIG_NET are now required in the kernel. +You will be warned of them if they are missing while you upgrade to +>=sys-fs/udev-210 by the package manager. +See the package's README at /usr/share/doc/udev-210/ for more optional +kernel options. + +The most reliable way of disabling the new network interface scheme is still +the kernel parameter "net.ifnames=0" since overriding the +80-net-name-slot.rules in /etc/udev/rules.d/ no longer works since upstream +renamed the file to /lib/udev/rules.d/80-net-setup-link.rules +The actual configuration is at /lib/systemd/network/99-default.link, which +you can override in /etc/systemd/network/ +So, to clarify, you can override the new .rules file or the .link file in /etc +but using the kernel parameter is the most consistent way. + +Since both the systemd-udevd executable and the network configuration is stored +at /lib/systemd, using a too wide INSTALL_MASK would be a mistake. + +[1] https://wiki.gentoo.org/wiki/Udev/upgrade#udev_208_to_210 +[2] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-02-25-udev-upgrade/2014-02-25-udev-upgrade.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-02-25-udev-upgrade/2014-02-25-udev-upgrade.en.txt.asc new file mode 100644 index 0000000..54ee677 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-02-25-udev-upgrade/2014-02-25-udev-upgrade.en.txt.asc @@ -0,0 +1,11 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.22 (GNU/Linux) + +iQEcBAABAgAGBQJTDJ5YAAoJEEdUh39IaPFNymYIAIeiKmL5teMiMgyqGJ7JkuYW +1libbWb3m0GAfTBxfKxnc6hQdRGTnZMVesGlHfrG08MnzcDz77aH60ZLFcPa4STx +xC4xIOdVEWOIl1di3yxqyJqwO0891jlIUTD+utkMMLF+qHAYP2Spf0vSwoTOLen5 +MM+fjxYReEHY0y8f5i0ylYMFG0H2jqHluw0SAimWRs5/gRRYGll71YrHPX2jrSpU +0ZF1X+b39azVElnuywLPXXh/LKO+ZsWN6b6mdO4Pxi+ieyKoHS0AxUf6SXhmXSQE +Sek39Z2Rto3Sq5ajDvIB5P4t1mshovDWkz6fTmRGrW/0iwlDa6wlRGOnJjI8g/s= +=rvgu +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-12-profile-eapi-5/2014-03-12-profile-eapi-5.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-12-profile-eapi-5/2014-03-12-profile-eapi-5.en.txt new file mode 100644 index 0000000..08a8ae6 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-12-profile-eapi-5/2014-03-12-profile-eapi-5.en.txt @@ -0,0 +1,47 @@ +Title: Profile EAPI 5 requirement +Author: Zero_Chaos <zerochaos@gentoo.org> +Content-Type: text/plain +Posted: 2014-03-02 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: <sys-apps/portage-2.2.0_alpha130 + +The Gentoo Council has decided that the entire profile tree will be +updated to require EAPI=5 support. + +http://www.gentoo.org/proj/en/council/meeting-logs/20140114.txt + +For all non-deprecated profiles this requirement has already been in +place for over one year. If you have updated your system at any point +during 2013, and followed the instructions in the profile deprecation +warnings (which cannot really easily be overlooked), and are running an +up-to-date portage version, there is absolutely nothing that you need +to do now. + +If you are running an installation that has not been updated for more +than a year, the portage tree you have just updated to may be +incompatible with your portage version, and the profile you are using +may be gone. + +It is still possible to upgrade, following these simple steps: + +1.) Do not panic. +2.) Download a portage snapshot from + http://dev.gentoo.org/~zerochaos/snapshots +3.) Unpack the snapshot to ~/tmp +4.) If you are not already, become root +5.) # rsync --recursive --links --safe-links --perms --times --force \ + --whole-file --delete --stats --human-readable \ + --exclude=/distfiles --exclude=/local --exclude=/packages \ + --verbose --progress --omit-dir-times /tmp/portage /usr/portage +6.) # chown portage.portage -R /usr/portage +6.) If needed, set your profile to a modern one (typically named 13.0) +7.) # eselect profile list +8.) # eselect profile set <desired profile> +9.) emerge --update --oneshot portage + +Now that you have a modern copy of portage, you can go back to updating +your system as usual. Please update your system at LEAST twice a year +to avoid issues like this in the future. + +Thanks for flying Gentoo. diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-12-profile-eapi-5/2014-03-12-profile-eapi-5.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-12-profile-eapi-5/2014-03-12-profile-eapi-5.en.txt.asc new file mode 100644 index 0000000..3aa3194 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-12-profile-eapi-5/2014-03-12-profile-eapi-5.en.txt.asc @@ -0,0 +1,11 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.22 (GNU/Linux) + +iQEcBAABAgAGBQJTIAi6AAoJEEdUh39IaPFNZF8H/2jXXz8gz/8Vn71tlbvjeunO +yCM5/eG3798OyOrOIdainwKxRsrEf2S1UpzDmNHdel9mLMSBt4kPzfbuFbP3t85K +vv0e6DvsJooopc1jetFSugvoXpdSo8FKzV50DjNR3fcKAEQ0CPk6KjG+3kiM53Wq +gVVjmzfqkKAnHPw69Yl5zlo663u1NiB7lGdoQ47T8xEG3WagQwMTOSTu+LD7SMTc +fgoIfwXOmXOB2rRtxMGNY4wU9IZuiVnad8v/Ljfjd9eYVHg+c5rKd2i0qltIS8+E +M1KI24xYnROKXdTtOJyFZeStTperZTuS1zWHLZX/9oQIWdTSBdzuCdWh6GwL9PY= +=2eGK +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-16-ruby-1.8-removal/2014-03-16-ruby-1.8-removal.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-16-ruby-1.8-removal/2014-03-16-ruby-1.8-removal.en.txt new file mode 100644 index 0000000..b377f2d --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-16-ruby-1.8-removal/2014-03-16-ruby-1.8-removal.en.txt @@ -0,0 +1,26 @@ +Title: Ruby 1.8 removal; Ruby 1.9/2.0 default +Author: Manuel Rüger <mrueg@gentoo.org> +Content-Type: text/plain +Posted: 2014-03-16 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: dev-lang/ruby + +Ruby MRI 1.8 has been retired by upstream in June 2013.[1] +We remove Ruby MRI 1.8 support from the tree now. In parallel Ruby MRI 2.0 +support will be activated in base profile's RUBY_TARGETS variable by default +in conjunction with Ruby MRI 1.9. + +If your currently eselected Ruby interpreter is ruby18, our recommendation is +to change it to ruby19. At the moment Ruby MRI 1.9 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 1.9 via: + + eselect ruby set ruby19 + +[1] https://www.ruby-lang.org/en/news/2013/06/30/we-retire-1-8-7/ diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-16-ruby-1.8-removal/2014-03-16-ruby-1.8-removal.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-16-ruby-1.8-removal/2014-03-16-ruby-1.8-removal.en.txt.asc new file mode 100644 index 0000000..3977b14 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-03-16-ruby-1.8-removal/2014-03-16-ruby-1.8-removal.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.22 (GNU/Linux) + +iQJ8BAABCgBmBQJTJO1IXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4MDA1RERERkM0ODM2QkE4MEY3NzY0N0M1 +OEZCQTM2QzhEOUQ2MzVDAAoJEFj7o2yNnWNcfWwP/2fBtO1qxBWkxCNf3f5jB7zk +fcicNKHbGd9GLR/PpD9AoOmVl4RZOZp5f/t8iyg7UGXmw+pSV3cJUARlcBIbVdIs +f4OxCUEbfhGR8CJHZnA9Xp0XefMJe8G0ZcJWaMPLNI1HYNeIvjdL1kqKmQYbuIzQ +wd87wfYn9ggVpPub2Hv8HjbxndiAOGbOYuLIjmj8Le8uXxyqbkraxvGBdQrLXqGx +5ib9e1bi9Ae2Hu3axEgc5umepFMCiUMIkqpH2DTDf4cQAJT4bTQIALstRsWge/4U +OC7b5Eu7dIcNRUgnw1IRx53DWKvWMU+pDu+l3+2gBQKxgCt0NB9tW3RjjsholbGU +JbyUxw17L7UpE1yt+buV61Fd1RhvHFJB5xUBzcVuYTlUEKoxKhxmG5swkmr7lyr6 +8TDHJRQOUY92zWKKwZkPFQlf7s5PZAGPY3NJfrNO/bhjUN+PgJRifbX2IzCrsiSJ +v8XR/OCGxyW5jglCnqA5iMduBbXRbH2SCsMoI2tXLWIqbaqPRZKSJfkcXizvGD60 +4lUtF0T0pUc68TWGV/i/p3nUc4q/P0UtHheGd/zgNXZGsP4MkimwOB9owZb2LXtO +o08W8WDZvuoGndBjGpcMELxculK4Q5s6tS0bceC9OwRRT4kobKfHYnz+FO8/N/Hj +YhaL5zin25OO2R7wu3gp +=iXP2 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-03-upower-loses-hibernate-suspend-to-systemd/2014-06-03-upower-loses-hibernate-suspend-to-systemd.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-03-upower-loses-hibernate-suspend-to-systemd/2014-06-03-upower-loses-hibernate-suspend-to-systemd.en.txt new file mode 100644 index 0000000..135dc69 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-03-upower-loses-hibernate-suspend-to-systemd/2014-06-03-upower-loses-hibernate-suspend-to-systemd.en.txt @@ -0,0 +1,30 @@ +Title: UPower loses hibernate / suspend to systemd +Author: Samuli Suominen <ssuominen@gentoo.org> +Content-Type: text/plain +Posted: 2014-06-03 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: <sys-power/upower-0.99.0 + +UPower discontinued hibernate and suspend support in favor of systemd. +Because of this, we have created a compability package at +sys-power/upower-pm-utils which will give you the old UPower with +sys-power/pm-utils support back. +Some desktops have integrated the sys-power/pm-utils support directly +to their code, like Xfce, and as a result, they work also with the new +UPower as expected. + +All non-systemd users are recommended to choose between: + +# emerge --oneshot --noreplace 'sys-power/upower-pm-utils' + +or + +# emerge --oneshot --noreplace '>=sys-power/upower-0.99.0' + +However, all systemd users are recommended to stay with sys-power/upower. + +A small tip for GNOME _and_ systemd users, only 3.12 and newer support 0.99, +so if you see the package manager pulling in sys-power/upower-pm-utils +while using old GNOME, like 2.32 or 3.10, you _can_ prevent it by adding +a package.mask entry for >=sys-power/upower-0.99 diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-03-upower-loses-hibernate-suspend-to-systemd/2014-06-03-upower-loses-hibernate-suspend-to-systemd.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-03-upower-loses-hibernate-suspend-to-systemd/2014-06-03-upower-loses-hibernate-suspend-to-systemd.en.txt.asc new file mode 100644 index 0000000..e3f89a4 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-03-upower-loses-hibernate-suspend-to-systemd/2014-06-03-upower-loses-hibernate-suspend-to-systemd.en.txt.asc @@ -0,0 +1,11 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.22 (GNU/Linux) + +iQEcBAABAgAGBQJTuqsdAAoJEEdUh39IaPFNrvsH/j8Kx76syqf6YzfunxIxz4Hx +P6YzJKa1YtyBAQuXVGh5Jl+qKUEcXQnVw5Vkd53Gd2ts9gpvwOchYbAUr5tbt0sL +/4tbCUlH4nSFo70tjLsmt3VDjyoUXUwarnqZONEVbPsqZm7kU3qJKmpyhtkDYla5 +WvaWSgP66/FvQIl2cgzL+tA4OshH7iMdaBwNkxhH08H5ropm/MmsicF503PJEZFJ +v8Gf1JkBhKjGQKPA+vZANOZBbwFbCxnA93zlGWZ+DL/hcAwhheE53mFZY7Jrc06K +YS7GbFUDrmAxGujc4tL7KhWdBl/8wmLQNQsGJ+38I4/eQVBaPX8UFusXvmnJ1N8= +=9lHA +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt new file mode 100644 index 0000000..926f6ff --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt @@ -0,0 +1,36 @@ +Title: GCC 4.8.3 defaults to -fstack-protector +Author: Ryan Hill <rhill@gentoo.org> +Content-Type: text/plain +Posted: 2014-06-15 +Revision: 2 +News-Item-Format: 1.0 +Display-If-Installed: >=sys-devel/gcc-4.8.3 +Display-If-Keyword: amd64 +Display-If-Keyword: arm +Display-If-Keyword: mips +Display-If-Keyword: ppc +Display-If-Keyword: ppc64 +Display-If-Keyword: x86 +Display-If-Keyword: amd64-fbsd +Display-If-Keyword: x86-fbsd + +Beginning with GCC 4.8.3, Stack Smashing Protection (SSP) will be +enabled by default. The 4.8 series will enable -fstack-protector +while 4.9 and later enable -fstack-protector-strong. + +SSP is a security feature that attempts to mitigate stack-based buffer +overflows by placing a canary value on the stack after the function +return pointer and checking for that value before the function returns. +If a buffer overflow occurs and the canary value is overwritten, the +program aborts. + +There is a small performance cost to these features. They can be +disabled with -fno-stack-protector. + +For more information these options, refer to the GCC Manual, or the +following articles. + +http://en.wikipedia.org/wiki/Buffer_overflow_protection +http://en.wikipedia.org/wiki/Stack_buffer_overflow +https://securityblog.redhat.com/tag/stack-protector +http://www.outflux.net/blog/archives/2014/01/27/fstack-protector-strong diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt.asc new file mode 100644 index 0000000..bed3050 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt.asc @@ -0,0 +1,11 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0 + +iQEcBAABCgAGBQJUBl+UAAoJEO04vUmVeoRj6hkIAI0Tv7xCf50nQFaNjYn0eRFd +kQcvU6P3Xg/uHREyZLH2L6TbVTvcBQZxZWq0sn73444sPisXVzdK6pYft4KoLm6j +X2Gmo6Ca9LA7KIdZ/agyjE6HqEz1X49glr0b76OUe9JieTymFnUXW11fz8dzK8T9 +7954uLelZ31snP1hIFHO/1hpQpXXJRjM1SQi1gJYJjOCHsFuz+wy4zpllY9mt8xx +lgExVHtslUOQxY22+TScbvPSWAu0u28ItXd8/XsQwmQJYCGZAl5Cqq7NcI1dZmM9 +ho8n/qGrT0VLITDyk4Rn4gynogA1VfnuqLk9QZqZzG5COi4FCZZ/9s7z5q20EiM= +=7Pue +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6.en.txt new file mode 100644 index 0000000..11ce7a0 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6.en.txt @@ -0,0 +1,27 @@ +Title: dhcpcd >= 6.4.2 changes defaults for IPv6 +Author: William Hubbs <williamh@gentoo.org> +Content-Type: text/plain +Posted: 2014-07-17 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: <=net-misc/dhcpcd-6.4.2 + +dhcpcd-6.4.2 and newer supports IPv6 stable private addresses when using +IPv6 stateless address autoconfiguration (SLAAC) as described in +RFC-7217 [1]. The configuration file shipped with dhcpcd activates this +feature by default, because it means that a machine cannot be tracked +across multiple networks since its address will no longer be based on +the hardware address of the interface. + +I received a report in testing that IPv6 connectivity was lost due +to this change [2]. If you are concerned about losing IPv6 connectivity, +temporarily comment out the line in dhcpcd.conf that says +"slaac private" until you can adjust to the new configuration. + +See the references below for why the upstream default is to use stable +private instead of hardware-based addresses. + +[1] http://tools.ietf.org/html/rfc7217 +[2] https://bugs.gentoo.org/show_bug.cgi?id=514198 +[3] http://tools.ietf.org/html/draft-ietf-6man-default-iids-00 +[4] http://mail-index.netbsd.org/tech-net/2014/06/04/msg004572.html diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6.en.txt.asc new file mode 100644 index 0000000..ec8af63 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6/2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iEYEABECAAYFAlPGk4MACgkQblQW9DDEZTiegQCffP0J23W1bUekr3CWpz9vkjDB +u84An2AH3TlneRgOp5UMCuYZQ7Izcd+W +=owFf +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-08-20-mysql_5_5_upgrade_procedures/2014-08-20-mysql_5_5_upgrade_procedures.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-08-20-mysql_5_5_upgrade_procedures/2014-08-20-mysql_5_5_upgrade_procedures.en.txt new file mode 100644 index 0000000..f0feef1 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-08-20-mysql_5_5_upgrade_procedures/2014-08-20-mysql_5_5_upgrade_procedures.en.txt @@ -0,0 +1,31 @@ +Title: MySQL 5.5 upgrade procedures +Author: Brian Evans <grknight@gentoo.org> +Content-Type: text/plain +Posted: 2014-08-20 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: <dev-db/mysql-5.5 + +MySQL 5.5 is now stable across all arches. The upgrade process +will require you to rebuild everything linked to +libmysqlclient.so.16 and libmysqlclient_r.so.16. + +This may be done for you by portage with 'emerge @preserved-rebuild'. + +A small number of libraries may not be automatically rebuilt against +the new MySQL libraries using preserved-rebuild. If you have +difficulties with packages not finding the new libraries, install +app-portage/gentoolkit and run: +# revdep-rebuild --library libmysqlclient.so.16 +# revdep-rebuild --library libmysqlclient_r.so.16 + +The official upgrade documentation is available here: +http://dev.mysql.com/doc/refman/5.5/en/upgrading.html + +Please be sure to review the upgrade document for any possible actions +necessary before and after the upgrade. This includes running +mysql_upgrade after the upgrade completion. + +Due to security flaws, MySQL 5.1 will be hard masked in 30 days after +this news item is posted. It will remain masked in the tree for +3 months before removal. diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-08-20-mysql_5_5_upgrade_procedures/2014-08-20-mysql_5_5_upgrade_procedures.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-08-20-mysql_5_5_upgrade_procedures/2014-08-20-mysql_5_5_upgrade_procedures.en.txt.asc new file mode 100644 index 0000000..2b9101b --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-08-20-mysql_5_5_upgrade_procedures/2014-08-20-mysql_5_5_upgrade_procedures.en.txt.asc @@ -0,0 +1,11 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iQEcBAABAgAGBQJT8/LyAAoJEE4V4vFnx44dYWQIAK/pwDO0rYQeIMu44DqSSqRb +FklJNY3Y2B0Chphsu/nIXSeKOmUaxRITh+DM4IJXjtFTafxQHjr3ST/76sEBSDkk +8avnkYSTahAAz2qyWauXv5f+e/AUqaPlvxWB2iy0e6Fs3GGbeglcoMRRs2kW1upY +7rAgdUI6ptB6lv5k9H6bs5HtgDUkdc6nawZhqLUJQFslmDofogSBXfchb8WUgiUR +9HRLYnjp78Qa+8OD5jmrZnNEhy1Wp48nlgrwYGfyj51DAVb69Mchi335traeencW +v9QHo+2Zm67gMeMY/xrIHg20tXjgTUx303KOj7l4sQA1PJX6miFeX8djuIlcFwk= +=JDNo +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-04-restructuring_of_mips_profiles/2014-10-04-restructuring_of_mips_profiles.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-04-restructuring_of_mips_profiles/2014-10-04-restructuring_of_mips_profiles.en.txt new file mode 100644 index 0000000..081d8a7 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-04-restructuring_of_mips_profiles/2014-10-04-restructuring_of_mips_profiles.en.txt @@ -0,0 +1,51 @@ +Title: Restructuring of mips profiles +Author: Anthony G. Basile <blueness@gentoo.org> +Content-Type: text/plain +Posted: 2014-10-04 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Keyword: mips +Display-If-Installed: sys-libs/glibc + +To accomodate the new multilib approach in Gentoo, the mips profiles will be +changing on Oct 11, 2014. The new profile structure will be as follows: + + [1] default/linux/mips/13.0/o32 + [2] default/linux/mips/13.0/n32 + [3] default/linux/mips/13.0/n64 + [4] default/linux/mips/13.0/multilib/o32 + [5] default/linux/mips/13.0/multilib/n32 + [6] default/linux/mips/13.0/multilib/n64 + [7] default/linux/mips/13.0/mipsel/o32 + [8] default/linux/mips/13.0/mipsel/n32 + [9] default/linux/mips/13.0/mipsel/n64 + [10] default/linux/mips/13.0/mipsel/multilib/o32 + [11] default/linux/mips/13.0/mipsel/multilib/n32 + [12] default/linux/mips/13.0/mipsel/multilib/n64 + [13] hardened/linux/musl/mips + [14] hardened/linux/musl/mips/mipsel + [15] default/linux/uclibc/mips + [16] hardened/linux/uclibc/mips + [17] default/linux/uclibc/mips/mipsel + [18] hardened/linux/uclibc/mips/mipsel + +There are a few points to note about the change: + +1) Only the glibc profiles (1-12) are affected. The embedded system profiles +(13-18) will not change. + +2) The glibc profiles will now explicitly state the ABIs. In the case of +non-multilib systems (1-3, 7-9) the stated ABI will be the only ABI available, +while in the case of multilib systems (4-6, 10-12) the stated ABI will be the +default ABI, and the others will be available by setting ABI_MIPS in make.conf. + +3) Profiles 1 and 7 are strictly 32-bit userland, but can run under either a +32-bit or 64-bit kernel. They will have CHOST = mips-unknown-linux-gnu and +mipsel-unknown-linux-gnu, respectively. All the other glibc profiles (2-6, 8-12) +are 64-bits userland and will have CHOST = mips64-unknown-linux-gnu or +mips64el-unknown-linux-gnu. + +4) Only users of profiles 1 and 7 need to change their profiles sym links using +`eselect profile`. However, all users should be aware of the CHOST value on +their system to ensure it remains unchanged after the profile updates. + diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-04-restructuring_of_mips_profiles/2014-10-04-restructuring_of_mips_profiles.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-04-restructuring_of_mips_profiles/2014-10-04-restructuring_of_mips_profiles.en.txt.asc new file mode 100644 index 0000000..1de6055 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-04-restructuring_of_mips_profiles/2014-10-04-restructuring_of_mips_profiles.en.txt.asc @@ -0,0 +1,17 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iQIcBAABCAAGBQJUMDhvAAoJEJOE+m71LUu69k8QAIJl00UECVN324GTJJRWoZ2X +F8adQxmSXMo8hwP6pe58cyJRRZGaIDjQu8y84WdRK07DcBXkXYVlTrdxARwIscqJ +8SAsNt3hVgKQNCS2vQaLnjHXtZhzPC+WJL6571SCbmQGyUDxVm9hu13R5UpwHFRI +ZB6HKV2X23lsW6PxNHcKoVu/YQoUzcFstFly0RvUrrNkluuzyoDcn288b7S9Y/eY +0I2ocNdH9B/YkW6LzYU5lO/womX0CorsTBpyIVBfiTSj9whsMgak4kl9fkygjRRY +0ULZ112gxVCcLLaQWgto1qczfo5BYaBVh3Q5jwW/m20aVwotRyynjyzLcVUeZpfP +YB5Sz5fG4bqNLWsKKd1kpJNI8j6NzSmA8jqTSSYlfWrYK2A6Gu7HnIaWPRFc6CkO +hCZA6gFn08HiB/WeGbPfKw+qXn1GX0yMTH1g2VWBY5P3AYd0JjLMim99B7QDBHij +KsChFUPILMEF2igc6bB9CfaN3hGXm8hbrvihxOHJG43aq1nqpdQz57uZBmjBNyi7 +yuCI3EzbvENicH82zE1+XRpYv3gL1+tLC6WRqzHrpDtisdyOj0DLsLjS+44k01at +8TMtHyafp0taBSicTBZJKczeE3tGnvM8OPwSDaWd5u1q4WQle9ERLrf6QJduyG5n +QRs5fsGMjtYxjMbHEUo1 +=eyit +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-mythtv-schedulesdirect-change/2014-10-22-mythtv-schedulesdirect-change.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-mythtv-schedulesdirect-change/2014-10-22-mythtv-schedulesdirect-change.en.txt new file mode 100644 index 0000000..a6ecb82 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-mythtv-schedulesdirect-change/2014-10-22-mythtv-schedulesdirect-change.en.txt @@ -0,0 +1,18 @@ +Title: MythTV SchedulesDirect Change +Author: Richard Freeman <rich0@gentoo.org> +Content-Type: text/plain +Posted: 2014-10-20 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: <media-tv/mythtv-0.27.4 + +Many MythTV users use the SchedulesDirect service as a source of program +data. If you use this service you will need to take action or you will +lose access to scheduling data on Nov 1st 2014. If you do not use this +service, no action is required. + +If you use the SchedulesDirect service, you must either upgrade to +media-tv/mythtv-0.27.4, or you must follow one of the workarounds found +at: http://www.mythtv.org/wiki/Schedules_Direct_URL_Change + +The link above also provides additional information about the change.
\ No newline at end of file diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-mythtv-schedulesdirect-change/2014-10-22-mythtv-schedulesdirect-change.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-mythtv-schedulesdirect-change/2014-10-22-mythtv-schedulesdirect-change.en.txt.asc new file mode 100644 index 0000000..0f8ef10 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-mythtv-schedulesdirect-change/2014-10-22-mythtv-schedulesdirect-change.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iF4EABEIAAYFAlRDyP8ACgkQCMFw3lXsEjp9sQD/ZDro5iyKMeqH5fZyr3VD0MVH +EmLWN0rHzORWcLtghf0A/0bxUqf74UvCEbEMcQaijO2kxjYDSiSC4DVc22EifaCm +=vb3J +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-upgrading-to-musl-1_1_5/2014-10-22-upgrading-to-musl-1_1_5.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-upgrading-to-musl-1_1_5/2014-10-22-upgrading-to-musl-1_1_5.en.txt new file mode 100644 index 0000000..77372bd --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-upgrading-to-musl-1_1_5/2014-10-22-upgrading-to-musl-1_1_5.en.txt @@ -0,0 +1,57 @@ +Title: Upgrading to musl 1.1.5 +Author: Anthony G. Basile <blueness@gentoo.org> +Content-Type: text/plain +Posted: 2014-10-22 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: sys-libs/musl + +Versions 1.1.4 and above of musl provide Native Language Support (nls). Up +till now, Gentoo musl stages have used GNU gettext to provide nls via libintl.so +and linked applications against it. Beginning with musl-1.1.5 we are switching +to nls provided by musl. Since musl is experimental, you are better off starting +with a new stage3 dated later than 2014-10-20. However, if you wish to upgrade +an existing system, you can proceed as follows: + +1. Remove any references to -lintl from /etc/portage/package.env and +/etc/portage/env/*. If you did not modify these from the original stage3 +then you can just do `rm -rf /etc/portage/package.env /etc/portage/env` + +2. Update your system, except for musl: + + emerge --exclude musl -uvNDq world + +3. Remove the libintl header belonging to gettext: + + rm -f /usr/include/libintl.h + +4. Now you can update musl without a file collision: + + emerge -1q =sys-libs/musl-1.1.5 + +5. We need to turn USE=nls off in gettext: + + echo "=sys-devel/gettext-0.19.3" >> /etc/portage/package.accept_keywords + echo "sys-devel/gettext -nls" >> /etc/portage/package.use + emerge -1 gettext + +6. Rebuild any packages that might be linking against libintl.so: + + USE=-nls emerge -uvDNq world + +7. The previous step probably missed some executables, so find them all: + + for i in /bin/* /sbin/ /usr/bin/* /usr/sbin/* ; do + readelf -d $i 2>&1 | grep -q libintl.so && echo $i + done + +You can identify what packages these belong to uing `equery b <exe>` Rebuild +those packages. + +8. At this point you can remove /usr/lib/libintl.so*. To be safe, check that +all your coreutils utilities (like mv, cp, ls, etc.) really aren't linking +against libintl.so as described in the previous step and then mv that library +out of the dynamic linker's search path. + +9. While not strictly necessary, you can rebuild your entire system to make +sure everything links nicely against the new libc.so: emerge -evq world diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-upgrading-to-musl-1_1_5/2014-10-22-upgrading-to-musl-1_1_5.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-upgrading-to-musl-1_1_5/2014-10-22-upgrading-to-musl-1_1_5.en.txt.asc new file mode 100644 index 0000000..f6b6ead --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-22-upgrading-to-musl-1_1_5/2014-10-22-upgrading-to-musl-1_1_5.en.txt.asc @@ -0,0 +1,17 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iQIcBAABCAAGBQJUSC5tAAoJEJOE+m71LUu6nowP/3NwBCvL6JZ6Kgel4qRsPL9b +fGZ8jlwK22XUv23GZ0M2QpEqov7CzBuCwiIboghdIsZfspEEmYqiwSM3fwDJBtLS +I8kGuK16eSDTiW2Nzbm67OMBHZiyg6sigbUPI18hxzQB2TBmk/X26GCJUo3BsZwS +htWwWphQnT6kWH9InurGdz6XJ5bnVy49ZNEXOf5ixGB/KECYX2hsox/xLiwSkWo7 +bw8CoKI+hzmMYsTC5XUqr9Yex27SEkYiR/FTL2Gu3A0WxyGmySI0k6ZSxD+i+81a +IbuesjEwXCD4M27UtJpP6dAwjWzVr0hztgsg7Hcx1YVrMYxwkaWfrBAZgcHZDv+F +5lYoM+V8uMbkKINWStD5iOC3oCwnIq9wa3dJ18gDJhbFmDwdaEtyHWoFUbpPLMOz +VBXyltxFBTZ/D3R2IT4ygDgOHm5xXT7JIhtk2mC8d0v0CUnIpsoCwe5iMyrOce9N +D/a/b3ip91Yttl0bfmWk7Couv6o67trwG8+hv7QYsSdJVfcLdDy8V2jUb3KZdI4F +iE78TZxlLBUUMdB6nChEKL3qa63+c2eYLSjjYxnJ+OaI43IndTEl05I/z0M+JS+D +3c15dKJpSX10EudmIJIoh8Q/YQpvV9/Cq0gC3iFngbKyvC+cCUpm+M0wU4zFYhFV +fCOtboRffXp8xiXQ4A76 +=Axqr +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt new file mode 100644 index 0000000..d074dbe --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt @@ -0,0 +1,50 @@ +Title: GCC 4.7 Introduced the New C++11 ABI +Author: Anthony G. Basile <blueness@gentoo.org> +Content-Type: text/plain +Posted: 2014-10-26 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: >=sys-devel/gcc-4.7.0 +Display-If-Keyword: amd64 +Display-If-Keyword: arm +Display-If-Keyword: mips +Display-If-Keyword: ppc +Display-If-Keyword: ppc64 +Display-If-Keyword: x86 +Display-If-Keyword: amd64-fbsd +Display-If-Keyword: x86-fbsd + +GCC 4.7 introduced the new experimental 2011 ISO C++ standard [1], along with +its GNU variant. This new standard is not the default in gcc-4.7, 4.8 or 4.9, +the default is still gnu++98, but it can be enabled by passing -std=c++11 or +-std=gnu++11 to CXXFLAGS. + +Users that wish to try C++11 should exercise caution because it is not +ABI-compatible with C++98. Nor is C++11 code compiled with gcc-4.7 guaranteed +to be ABI-compatible with C++11 compiled with 4.8, or vice versa [2]. Thus +linking C++98 and C++11, or C++11 compiled with different versions of gcc, is +likely to cause breakage. For packages which are self-contained or do not link +against any libraries written in C++, there is no problem. However, switching +to C++11 and then building packages which link against any of the numerous +libraries in an incompatible ABI can lead to a broken system. + +This is a precautionary news item and the typical user need not do anything. +However, as C++11 gains in popularity and the number of packages using it +increases, it is important that users understand these issues [3]. + +For an ABI compliance checker, and more information about C++ ABIs, see [4]. + +Ref. + +[1] http://www.stroustrup.com/C++11FAQ.html + +[2] Upstream GCC does not support ABI-compatibility between gcc-4.x and 4.y for +any x != y . See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61758. Even +having different versions of gcc installed simultaneously may lead to problems, +especially if the older version of gcc is active. An example is +https://bugs.gentoo.org/show_bug.cgi?id=513386. + +[3] Note that some packages like www-client/chromium and net-libs/webkit-gtk +are already using C++11 features. + +[4] http://ispras.linuxbase.org/index.php/ABI_compliance_checker diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt.asc new file mode 100644 index 0000000..71d65d7 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt.asc @@ -0,0 +1,17 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iQIcBAABCAAGBQJUTNsSAAoJEJOE+m71LUu6mZYQAIyerv/ypTJBGehr3sNtxJug +aAgrFG6AF+y35/beaxFl2R4EhRPRKzUY5RTunrPd1o5QUay+lkzlhkyiZY2R/nQs +p3K7HzoBg2onW8wYtDNKAuPXu/r5lPMlF4WM10l/jyK63nbbVSqKooF8VFEh1M0C +FDqyF52biY2dDTWsVuqTle7SO/synCIGj5IvTM3pvfcID4vVIrYk8YNGljuFlirW +RnViqygIR+u4J36J5KAjJYpxE7e61Gtz/gP/q6eWIG9LnOUiq+gHSgcA+6rlxi4V +PKBx7Fgabs8wbrLEZ12wjMhEN/SDVwtWREfZfz/OMGqd1nkY5z3SxGZ760iGgZuJ +Jk9IyxZ2b1rRxtzF+BGsIEAluxb3VDWO5XX88nloxcWaWx9wYZbkT8eVoz1DnNKV +5AQSaQPtMJQq1HwsviZ3W4JPiotdsE8ERjQi6s2X0ekPubhidG/jqW7hRaobOrPH +SvHjTNjZiMDP9rwbLnWSur+/VZKgLQVHhhAX8fSHgmekPwBEjXRA1rCNNtLkYwh7 +z2LAP5+8v8eJAFw/U15emLWNKJKyzJMA1oq7f5NfYD6aWasBveBdbdP7AHJ1kHp4 +wh0JhAF0O7Ir7d2SNgsKHnNMANHcBaSykmkzydWbBycTAcvtAOIe24mYDEds5AGb +ZvMKkPqa774AzuTXV3xX +=JFZ/ +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-07-udev-upgrade/2014-11-07-udev-upgrade.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-07-udev-upgrade/2014-11-07-udev-upgrade.en.txt new file mode 100644 index 0000000..c146609 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-07-udev-upgrade/2014-11-07-udev-upgrade.en.txt @@ -0,0 +1,16 @@ +Title: Upgrade to udev >= 217 or eudev >= 2.1 +Author: Samuli Suominen <ssuominen@gentoo.org> +Content-Type: text/plain +Posted: 2014-11-07 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: <sys-fs/udev-217 +Display-If-Installed: <sys-fs/eudev-2.1 + +sys-fs/udev-217 and sys-fs/eudev-2.1 no longer provide a userspace +firmware loader. If you require firmware loading support, you must use +kernel 3.7 or greater with CONFIG_FW_LOADER_USER_HELPER=n. No action is +required if none of your kernel modules need firmware. See [1] for more +information on the upgrade. + +[1] https://wiki.gentoo.org/wiki/Udev/upgrade#udev_216_to_217 diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-07-udev-upgrade/2014-11-07-udev-upgrade.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-07-udev-upgrade/2014-11-07-udev-upgrade.en.txt.asc new file mode 100644 index 0000000..406f9a5 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-07-udev-upgrade/2014-11-07-udev-upgrade.en.txt.asc @@ -0,0 +1,11 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iQEcBAABAgAGBQJUXLahAAoJEEdUh39IaPFNouQH/15VC3GjxIaDFleBrYlXPM1b +71RIDAQVgiGfMB2SvIEPyRZ7YxOXCbRnAXr09IkziDYxZcIVRwj+HOjMNoBRt/26 +3MTpZjB6hp1qScwZBCjahJGi/BQ+w564oxS/gpnSAMZIsX5+68YzwniJ5Jpgz8Gy +aY6SMODD0P8h7DHuzPgScR+A29eS9bdOUCRPuzl3MLFzZo4htdY2LNDQKF1mNmAz +NJeINjc6uxBffDjA8nl+s5hjgi/P8wuE51DI6HE8EIjGkV/2hn6uUcMUVFCw2gnZ +j7t7m21fUSRfsY9Iv0ucHDlMlpwZAUJbQJtc4P+xqZrS/aQNBuhalJNDQ32OlTY= +=SL12 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-11-kgcc64-sparc-removal/2014-11-11-kgcc64-sparc-removal.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-11-kgcc64-sparc-removal/2014-11-11-kgcc64-sparc-removal.en.txt new file mode 100644 index 0000000..635c865 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-11-kgcc64-sparc-removal/2014-11-11-kgcc64-sparc-removal.en.txt @@ -0,0 +1,16 @@ +Title: sys-devel/kgcc64 removal on sparc +Author: Raúl Porcel <armin76@gentoo.org> +Content-Type: text/plain +Posted: 2014-11-11 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Profile: default/linux/sparc + +sys-devel/kgcc64 is going to be removed from the sparc system package set +since the normal sys-devel/gcc can, since version 4.4, build 64bit kernels. + +Until now, you had to use CONFIG_CROSS_COMPILE="sparc64-unknown-linux-gnu-" +in your kernel config, but with sys-devel/kgcc64 going away, you need to +remove that option from your kernel configuration. + + diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-11-kgcc64-sparc-removal/2014-11-11-kgcc64-sparc-removal.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-11-kgcc64-sparc-removal/2014-11-11-kgcc64-sparc-removal.en.txt.asc new file mode 100644 index 0000000..f6ee267 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-11-kgcc64-sparc-removal/2014-11-11-kgcc64-sparc-removal.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iEYEABECAAYFAlRp3CUACgkQuQc30/atMkBWegCfUeS9rme6u7HxiWNZkUGWoPpv +HB0AoIm7Du6w0Xluoap/pl5iv0IXF5YI +=fGH0 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt new file mode 100644 index 0000000..f63ca77 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt @@ -0,0 +1,51 @@ +Title: bash-completion-2.1-r90 +Author: Michał Górny <mgorny@gentoo.org> +Content-Type: text/plain +Posted: 2014-11-25 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: >=app-shells/bash-completion-2.1-r90 + +Starting with app-shells/bash-completion-2.1-r90, the framework used to +enable and manage completions in Gentoo is finally changing in order to +properly follow upstream design. This has some important implications +for our users. + +Firstly, the install location for completions changes to follow upstream +default. The completions enabled before the upgrade will continue to +work but you may no longer be able to enable or disable completions +installed prior to the upgrade. To solve this issue, the packages +installing completions need to rebuilt. The following command can be +used to automatically rebuild all the relevant packages: + +$ find /usr/share/bash-completion -maxdepth 1 -type f \ + '!' -name 'bash_completion' -exec emerge -1v {} + + +Secondly, the autoloading support introduced upstream removes the +penalties involved with enabling a great number of completions. This +allowed us to switch to an opt-out model where all completions installed +after the upgrade are enabled by default. Specific completions can be +disabled using 'eselect bashcomp disable ...' + +The model change implies that all current selections done using 'eselect +bashcomp' can not be properly migrated and will be disregarded when +the relevant completion files are built against the new bash-completion +version. After rebuilding all the packages providing completion files, +you may want to remove the symlinks that were used to configure +the previous framework using the following command: + +$ find /etc/bash_completion.d -type l -delete + +Thirdly, we have solved the issue causing bash-completion support to be +enabled by default on login shells only. If you needed to explicitly +source 'bash_completion' script in bashrc, you can safely remove that +code now since system-wide bashrc takes care of loading it. + +Lastly, we would like to explain that USE=bash-completion is being +removed from packages for the completions will be installed +unconditionally now. However, this will result in some implicit +dependencies being removed. Most specifically, users wishing to use +bash-completion will have to request app-shells/bash-completion +explicitly, e.g.: + +$ emerge -n app-shells/bash-completion diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt.asc new file mode 100644 index 0000000..ed9cc4f --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iQJ8BAABCgBmBQJUc7wdXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC +MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOVSgQAIr354YAxhE2gRS/fyG0r0WD +5wipNaYU1tgcNmN1GFhasp2cwLPdmFNueqvp/MUoR/rA9U1yvNhGRDjJS++KF4u7 +nbWSZczWBfxDTGuDJ4+uS3BkeeFGsL2z2v+tkKZUfnnK0c6ZW7Qk9pUZNqRBnptP +QKjWikq98Dn0+jJUdiK6fG4LjPUL4B1jvKZUSCtm4jCLsYWymF1ffrZprEyYX3i5 +0T0CqN+HAo8TvosYCPedMJR7Hh4BOSrw1gfZchgPh5gcq0I3zO5zat6HkF1y6joF +50f+p/f5fSf5xqyTui5sVvb8P99XlKDuGy3EJe4Bah/LKdvot8/NdXh2xL+Bj9QU +l1MFeUrpktKgNbdzPsmg4VbVy7CTkynVw3tSmNMVc85HP6mpAE6eobSDWCtLf6wm +f4GJZBK+Sk9Vd3NeyI+QOIUWDs2cfn460HOXiocRDEjEzqB5N3LMWLtYO1Vr7EbN +NOfuAj2A5Rs2+X4yftN3RcJMQK5fWZQHyEQkkowLZLNIt+54xCs5BCrK2GK1zCi/ ++3Yp77Low9M4qjXB2bHblW2Edi5XmxdyNrtDymVbH3QLKKA6JgkBVy+jOacCZkp2 +Dg/1c+Rb3qnW4jWkbvNb3UFFnzl3W7VDLL0wttpwgrVTkA/Ivu/Qe3XH/N0iZdfu +ZNXVGXYhTIySbu18cb7O +=UzD3 +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-01-28-cpu_flags_x86-introduction/2015-01-28-cpu_flags_x86-introduction.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-01-28-cpu_flags_x86-introduction/2015-01-28-cpu_flags_x86-introduction.en.txt new file mode 100644 index 0000000..f0a03f4 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-01-28-cpu_flags_x86-introduction/2015-01-28-cpu_flags_x86-introduction.en.txt @@ -0,0 +1,48 @@ +Title: CPU_FLAGS_X86 introduction +Author: Michał Górny <mgorny@gentoo.org> +Content-Type: text/plain +Posted: 2015-01-28 +Revision: 2 +News-Item-Format: 1.0 +Display-If-Keyword: amd64 +Display-If-Keyword: ~amd64 +Display-If-Keyword: x86 +Display-If-Keyword: ~x86 + +The USE flags corresponding to the instruction sets and other features +specific to the x86 (amd64) architecture are being moved into a separate +USE flag group called CPU_FLAGS_X86. + +In order not to lose CPU-specific optimizations, users will be required +to update their make.conf (and package.use) file. For example, if +the following USE flags were present: + + USE="mmx mmxext sse sse2 sse3" + +Those flags need to be copied into: + + CPU_FLAGS_X86="mmx mmxext sse sse2 sse3" + +Please note that the same CPU_FLAGS_X86 variable is used both on x86 +and amd64 systems. + +When in doubt, you can consult the flag descriptions using one of +the commonly available tools, e.g. `equery uses` from gentoolkit: + + $ equery uses media-video/ffmpeg + +Most of the flag names match /proc/cpuinfo names, with the notable +exception of SSE3 which is called 'pni' in /proc/cpuinfo (please also +do not confuse it with distinct SSSE3). + +To help users enable the correct USE flags, we are providing a Python +script that generates the correct value using /proc/cpuinfo. It can be +found in the app-portage/cpuinfo2cpuflags package: + + $ emerge -1v app-portage/cpuinfo2cpuflags + $ cpuinfo2cpuflags-x86 + +In order to ensure safe migration and maintain compatibility with +external repositories, it is recommended to preserve the old USE +settings for a period of one year or until no package of interest is +still using them. diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-01-28-cpu_flags_x86-introduction/2015-01-28-cpu_flags_x86-introduction.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-01-28-cpu_flags_x86-introduction/2015-01-28-cpu_flags_x86-introduction.en.txt.asc new file mode 100644 index 0000000..56506a2 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-01-28-cpu_flags_x86-introduction/2015-01-28-cpu_flags_x86-introduction.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iQJ8BAABCgBmBQJUyUkPXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC +MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOyegP/0KylFSxoFDnSLgflO7acA6J +Q4SjnflF8TQvhF5c6pYURPLJEeEE4vl4i6B7QeSndwU7+vAThxwt3/ZS/VNmmypD +M9uMFXHO0J7C1iBHSANjG8Rv2VN9fp5gFSUQPo3XSY7X2TMcsyRFTQwLT2mD9kpD +DCmBfedfNcrIbJwOC2yhMKgGBimmWztMbyoPP79E0Nh0X6ohq6YumzUHObZzqQlw +xfEquk7hrIa2LpVzOepNTR/efFwvMQ5mIWqlzVLeSw57muGmaU1xHYHfyzzp2JYV +lQvTxs98jgDzTcQt4FsWBaCmWBG8hhe5g/eUlO9/SAwO7yAfWuTQSeVAxcBJi/CJ +v2kSZ42JlHFg7NXz6jb4DlAmID0r53H1u41nx8c146KZgKpo/V5fzxzE4dhSQViR +ammOKYsGl4ZjP1OYcJtumNSNWvLZgsz98MRNxiKsIFnndm6DgSNhHTTJaU6xwpYg +qxQ/A13Pgc/Tp6bXP+CcfEAwUpQUxC/ghkTDU4Q/vF/NR0l3L2DMkli6x5U1uy2f +E6C1au06s7U6mc/jorquwxZEbNzUuEI4UrFb3IbU+BU6a6t33YSnbhLjWcZqRHZS +E5sOJQtfSk5FBfIR0BXPJJFbFr5impneAPMvuJ3cu7mE7DnVNVekY7MAKs1KHwZQ +/HenWNxCJfxE7DKw7oBo +=hfNU +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt new file mode 100644 index 0000000..47d54f4 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt @@ -0,0 +1,35 @@ +Title: ffmpeg/libav conflict management: USE=libav +Author: Michał Górny <mgorny@gentoo.org> +Content-Type: text/plain +Posted: 2015-02-01 +Revision: 2 +News-Item-Format: 1.0 +Display-If-Installed: media-video/ffmpeg +Display-If-Installed: media-video/libav + +The support for automatic choice between ffmpeg and libav is going to be +deprecated in favor of explicit choice via USE flags. This change aims +to solve multiple repeating issues, including Portage undesirably +wanting to replace one package with the other, lack of proper reverse +dependency on ffmpeg/libav upgrades and some of the hard-to-understand +upgrade failures involving blockers. It also may be used to make ffmpeg +and libav co-installable in the future. + +The current USE=ffmpeg will maintain its role of enabling optional +support for ffmpeg or a compatible implementation (libav) in a package. +However, whenever appropriate additional USE=libav will be introduced to +control the preference of one implementation over the other. + +Users who currently use libav need to enable USE=libav in +/etc/portage/make.conf. It should be noted that users still need to +enable USE=ffmpeg on packages with optional libav support as well. +Users who currently use ffmpeg need to take no action. + +Please also note that some packages support only one of the two +implementations. An attempt to install one of those packages may result +in blockers requiring the user changes the global USE=libav state. + +Please do not alter the state of 'libav' flag on a per-package basis +(e.g. via package.use). The flag needs to be set globally to have +consistent value throughout all packages. Otherwise, blockers will +prevent upgrades. diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt.asc new file mode 100644 index 0000000..4c707dd --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0 + +iQJ7BAABCgBmBQJVL6ACXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5MTlDREQ0NUU5Mjc4RkU2RjJDNTAyNzU0 +RkRGOUNGRDJGQUM1MTRFAAoJEE/fnP0vrFFO/OEP+OVRQZ9qhhCQZk2aMPHyVjWq +WOosaFV/CzBNSevLsr1cSdYOVBPD8jfbEpnX77cAU515GhFYBj5t6/3ALvHrR+yv +TELpGoJqCrfzX7QjI+uNWTkWGd3LztcZF1qrfyKsaYV2rhtZP8DQEca73HVSpe/Z +HpDVG6x/PQX3ynLcRH3ojaEATA2By8pf/rrDZZumRVce0+Af87U0FvEvOU8iVQCS +c4eI9XkOMSN0ZrGyfE1Rdqqr3VzGgCKltdOXoQQxhzsC9CPFsCHcXSnFjpM318h9 +FRyDauyuGR0tDQvLJZzkcQTP4V+hayA/IgBxlDKQwAf98u9MOc83CzglIUnYiI7A +26Ez8Vnl+zTaMwKSTzoq/Zc9rLU44by3ew0u9vhhLeDs80Xqmrk4KRi+761fJwWi +mj5QG94Z8lCEUzddAjHt4D2AOjoxMGhKZj8vxcKhjZQMz4Cl9HgZ6KllyX84rNYZ +/No6Ob3H5yUCJYVxMOKDGgZWl3aWi2wmYyENPckDA3lBOi0dKumjJCvMGIGEJLfO +/sNsFKdA1bf5xSq021c3AOFUuCBbnq0aO2jlrVITEFgKUnsV0IqJEttFyI8eDwb2 +jwnRmKmGzjpNley4FLYM9f9J5r6JKo3PZ3r0YbYjHgJ/7+IFRD4tdSt9epKRaX/1 +QFZnkjYnvflc7oq69Tw= +=r8nK +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-02-nfs-service-changes/2015-02-02-nfs-service-changes.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-02-nfs-service-changes/2015-02-02-nfs-service-changes.en.txt new file mode 100644 index 0000000..7e1b2be --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-02-nfs-service-changes/2015-02-02-nfs-service-changes.en.txt @@ -0,0 +1,39 @@ +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-02-nfs-service-changes/2015-02-02-nfs-service-changes.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-02-nfs-service-changes/2015-02-02-nfs-service-changes.en.txt.asc new file mode 100644 index 0000000..e4b872d --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-02-nfs-service-changes/2015-02-02-nfs-service-changes.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iEYEABECAAYFAlTOvR8ACgkQblQW9DDEZTgZVQCfet8NCFgtHFd2Td5Njglf3cHo +lJsAn3qXn3U9YXr313KKe0aNNQ3x6nu2 +=XpII +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt new file mode 100644 index 0000000..5a2d212 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt @@ -0,0 +1,77 @@ +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 + +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt.asc new file mode 100644 index 0000000..796ef41 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0 + +iQJ8BAABCgBmBQJU05EeXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2OUZEQTI0MjY5QzhCNUE3RTlFMjMxRTkw +MTg2ODIyMzFCOTI2RTRGAAoJEAGGgiMbkm5PkLgQAJsBmEFsvV3e0mMJr+vIW8pV ++aunYvpZE5QYCtTX/buwBH4QHHvZz5LgOxSjZvkDPJtpgFNtP1d46XbK0tySmNfR +zYBASELkwrnF2ODmKSvo0HpqMOYNjkP7sSD23+mRN+TPS8Fw2QS8Wt9yDP4ba2yx +mJLGaelB5B98FSnbvTw3Tz+0lbuqyqF3kbp7/Z2t+CERhAsKCRF8TedCsvaIaR3M +jn73FmHN5XmPjUHgL/fxoKFSVcz+0oixLYSON/3J5g6ZZscvhwVOrkBVtrCgot0q +PYnPiFIHT1IKXMwDbReIfFkFw6FPbvWID0WjMzBmqVoroHEitOSqygVDA/4RYRMe +RrsozGxWOwah7Mu+v28Pk61J1pk/RjlbNXmr86V51hCPdd7fidf4tHzSJgIfWYth +u5QTu14Fi9rk2gtmJVjoC24dqkNVCemZXeFhqvrQ+/JsBCkdkVz+YyzkaSzwOj/q +vDtSF/VcHTr40bz9TNs3faEJ1OBxJ0f4vdbTB+jOvfzlib0v6dAdHWnyDuLcNaVe +e/idsUvEumDU9Phr+KMprHtvIRjplhdriNUrGWjWCJtRce7IHzk0bwxyhB/60QQr +N4gr4oW9m63LfMSLMEwnsV9VCGaX9k0Jh8zDXRaqb4vutXUwB1B7MJfaQKQnOEon +2PHNsP6quhXB5Dk9Lu1b +=nLlP +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-03-28-true-multilib/2015-03-28-true-multilib.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-03-28-true-multilib/2015-03-28-true-multilib.en.txt new file mode 100644 index 0000000..e368783 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-03-28-true-multilib/2015-03-28-true-multilib.en.txt @@ -0,0 +1,48 @@ +Title: True multilib support on amd64 +Author: Michał Górny <mgorny@gentoo.org> +Content-Type: text/plain +Posted: 2015-03-28 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Keyword: amd64 +Display-If-Keyword: ~amd64 + +Starting on 2015-03-29, we are enabling true multilib support on amd64 +and masking the old emul-linux-x86 package sets for removal. This +change provides our users with the opportunity to build 32-bit libraries +from source with all the flexibility given by ebuilds and the security +of using mainline ebuilds, rather than relying on pre-packaged binary +versions of them. + +The switch to the new system is likely to require a specific action from +the users of our multilib profiles. Since the new system collides with +the old one, the Package Manager must be able to clearly satisfy all +the dependencies using the new system in order to proceed. This may +require unmerging packages installed from third-party repositories that +have not been updated to support the new system. + +In order to enable building necessary 32-bit libraries, users will be +required to enable the abi_x86_32 USE flag on respective packages. +This can be done using /etc/portage/package.use entries alike +the following: + + sys-libs/zlib abi_x86_32 + +In most of the cases, Portage will be able to deliver correct +suggestions for that when using the --autounmask feature. However, some +users may prefer setting ABI_X86 globally to enable 32-bit libraries +in all packages that support building them. This can be done using +the following package.use entry: + + */* abi_x86_32 + +In case of issues, blockers especially, users are recommended +to manually uninstall any emul-linux-x86 packages that may have been +installed on their systems. This will aid the Package Manager +in choosing the correct dependency resolution path. If using Portage, +this can be done using the following command: + + $ emerge -C 'app-emulation/emul-linux-x86*' + +Note: 32-bit applications may be temporarily broken after this step. +Therefore, it should be followed by a @world upgrade immediately. diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-03-28-true-multilib/2015-03-28-true-multilib.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-03-28-true-multilib/2015-03-28-true-multilib.en.txt.asc new file mode 100644 index 0000000..d0894bb --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-03-28-true-multilib/2015-03-28-true-multilib.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iQJ8BAABCgBmBQJVFyVTXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC +MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOzS8P/Rd69CSdiDN2yZhOGWaOwK40 +ueGH7BWTRM0tEovaGNrO2MQaT+ZKXacqoDY0DPLhuC/TMuI+NbvKALeWTEfVZ5d1 +zWckrjzzchc+BoBx6sTV+sSLgFPR9JVZ5HoVJyW+RlKS2Z8bzyKMVg/zd8ViAllG +CqMVcamnLsXZQnJ8wsD+gu+UCvBvQOd0kxWJNQa9FsiYdLnVZQZYdOtfk2DKGvhg +7B1lo1r7O9izZtm0ND//Wu/IJNWEutkD2KmWqdB8SBa5YtMM78IUinzsUExtNAxf +ihZTc/lSYB8fFx88VTso3lo1ndR7MEoMQIyydJJkEeOS1ue4LemuTuLMYHIL1jp4 +J//5EHgFz0zcFR8unUnZBBZDcL+9taTfGiQyNaEu4YQ3K/R56DAkBEHRbIt3dtXS +9/VLbg865JDqxaMsZPff5RwFhUa6WanD3pJDp8GQ+Fg1uG2sSDA/1SsqQjA0vyC7 +pAU6vbK82ZhBGsrwjEhFzGZ3QOLbZfy/l+dULL/zlYTQbwb4xQ8nYbK9EIc41i8e +qIvRsDbQ+Q9boOQB/bm1+2o65+LKs1kPMPcFyANJ1IMEgl1wDwHCqhO30y7MDtbT +eMI6WPG4S4z4/gQNK4WE5/nDB3/sfPuc0zOyMzavFDMeWFHUclDhvTSgi3WN5/vi +vl+tBROxSvJOAVDch6Xs +=hbsM +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-06-apache-addhandler-addtype/2015-04-06-apache-addhandler-addtype.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-06-apache-addhandler-addtype/2015-04-06-apache-addhandler-addtype.en.txt new file mode 100644 index 0000000..f90d091 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-06-apache-addhandler-addtype/2015-04-06-apache-addhandler-addtype.en.txt @@ -0,0 +1,100 @@ +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-06-apache-addhandler-addtype/2015-04-06-apache-addhandler-addtype.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-06-apache-addhandler-addtype/2015-04-06-apache-addhandler-addtype.en.txt.asc new file mode 100644 index 0000000..24ff156 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-06-apache-addhandler-addtype/2015-04-06-apache-addhandler-addtype.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iEYEABECAAYFAlUigTAACgkQsAvGakAaFgCjYgCgolN2sUZAffYDBcPQ5tQ/nJJH +vOUAn2VaVIeKYOcmlQV8hct2IhL4ZfMC +=/vsQ +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-16-ffmpeg-default/2015-04-16-ffmpeg-default.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-16-ffmpeg-default/2015-04-16-ffmpeg-default.en.txt new file mode 100644 index 0000000..82c01f1 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-16-ffmpeg-default/2015-04-16-ffmpeg-default.en.txt @@ -0,0 +1,25 @@ +Title: FFmpeg default +Author: Ben de Groot <yngwin@gentoo.org> +Content-Type: text/plain +Posted: 2015-04-16 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: media-video/ffmpeg +Display-If-Installed: media-video/libav + +Since the choice between ffmpeg and libav has been made more +explicit, there has been a lot of discussion about what the +default implementation should be. It can be concluded that +media-video/ffmpeg has wider support, and would be somewhat +more convenient for most end-users. + +For this reason the default implementation has been switched +back from media-video/libav to media-video/ffmpeg by removing +the libav useflag from the base profile. + +If the libav useflag is already globally enabled or disabled +in /etc/portage/make.conf, then no further action is required. + +Users who implicitly relied on libav being enabled in their +profile, and who wish to continue using libav, should enable +USE=libav in their /etc/portage/make.conf file. diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-16-ffmpeg-default/2015-04-16-ffmpeg-default.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-16-ffmpeg-default/2015-04-16-ffmpeg-default.en.txt.asc new file mode 100644 index 0000000..1944c0f --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-04-16-ffmpeg-default/2015-04-16-ffmpeg-default.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0 + +iQJ8BAABCgBmBQJVL6BuXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5MTlDREQ0NUU5Mjc4RkU2RjJDNTAyNzU0 +RkRGOUNGRDJGQUM1MTRFAAoJEE/fnP0vrFFOHVsQAL8S2H3MxtXxvAucRydeNa1u +UfXoyVC/0QzwWAGCmrBCOpf7XSdDZth8HSBmlnE9ttEqc5Csbn7hOiENOuUfhzsH +6QtPtOSvGtAk3Kw3M+e0Q6pezPE8AzpUIs3RZVu4+vDz553MqEyzAS8bC8Eldzku +c4CQ9/mztAEyvmjfZRh7ZGlW7D+9G+L9SOK8EH2SBjMi5RhOrly0eZa5cF9nXAyz +UC1D0wRahyCBOdipRSbJnhe/QuRYrozVqjqLam1w2m31E4tswRE6hos77QB4yhr9 +NAVO36/KUuU7PeI7bIMh7ORcC5WzrlCwoD4T1eg13BSTtgFdK3U23w3y/BJLkdrx +ha36fYhnbo2x+am/VZ4TVrBrf5gTXUVZjV3pKPAt2Ce6h/FA+yy4POK+m/+LtAhG +aWJXiHN+ZkaP2thM9bSBE4dAgwFdBfg7z9UPCG7Zx6QC+3q5nLh1Kq9409kczVly +8tVRjO/Lp19xMGBc93EsLDv7ald91oeYJ/mW04BDrq5XpTEDHmRuz8BHNR7c7zMP +tY0CmogMc/NS1NIncRNEMCz6QcN1D4cHpudnApbmnoyQJrd7N1QIEGjYahKO4yZv +Ju/Zzjtm0XLIZwApeY+qEGEOpker1QC25iSsLa+m0jFOedSShGy92P7aQWM5rg84 +CTxqR92X3fUhWU5fTPTu +=l+fp +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-05-01-shorewall-changes/2015-05-01-shorewall-changes.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-05-01-shorewall-changes/2015-05-01-shorewall-changes.en.txt new file mode 100644 index 0000000..08d1cdb --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-05-01-shorewall-changes/2015-05-01-shorewall-changes.en.txt @@ -0,0 +1,43 @@ +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-05-01-shorewall-changes/2015-05-01-shorewall-changes.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-05-01-shorewall-changes/2015-05-01-shorewall-changes.en.txt.asc new file mode 100644 index 0000000..6515bd2 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-05-01-shorewall-changes/2015-05-01-shorewall-changes.en.txt.asc @@ -0,0 +1,55 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA1 + +Title: shorewall is now a single package +Author: Thomas D. <whissi@whissi.de> +Content-Type: text/plain +Posted: 2015-04-<to-be-set> +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. +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0 + +iKYEARECAGYFAlVC6DlfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl +bnBncC5maWZ0aGhvcnNlbWFuLm5ldDdDQUM1OUY0ODkzMERBREU1NUQ1RjJBRkIy +OEVDMjEzQjgwNzJCMEQACgkQso7CE7gHKw18gwCfd+9rMpm1KMRfZMKJjlIUFPzB +SZMAn02AdNbfGTSVRdMTgH1hj9+I1Hyd +=WJss +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-06-08-udev-init-scripts-changes/2015-06-08-udev-init-scripts-changes.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-06-08-udev-init-scripts-changes/2015-06-08-udev-init-scripts-changes.en.txt new file mode 100644 index 0000000..5ab36d7 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-06-08-udev-init-scripts-changes/2015-06-08-udev-init-scripts-changes.en.txt @@ -0,0 +1,20 @@ +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-06-08-udev-init-scripts-changes/2015-06-08-udev-init-scripts-changes.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-06-08-udev-init-scripts-changes/2015-06-08-udev-init-scripts-changes.en.txt.asc new file mode 100644 index 0000000..0adec34 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-06-08-udev-init-scripts-changes/2015-06-08-udev-init-scripts-changes.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iEYEABECAAYFAlV4rskACgkQblQW9DDEZTjjugCdEES0H+9SNP+C3JMP0WjVKewl +teoAn2F7jXjWUv6G6ONSax59CXG0itS+ +=ZSH+ +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-07-25-python-targets/2015-07-25-python-targets.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-07-25-python-targets/2015-07-25-python-targets.en.txt new file mode 100644 index 0000000..720eb66 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-07-25-python-targets/2015-07-25-python-targets.en.txt @@ -0,0 +1,26 @@ +Title: Python 3.4 enabled by default +Author: Mike Gilbert <floppym@gentoo.org> +Content-Type: text/plain +Posted: 2015-07-25 +Revision: 1 +News-Item-Format: 1.0 + +Python 3.4 is now enabled by default, replacing Python 3.3 as the +default Python 3 interpreter. + +PYTHON_TARGETS will be adjusted to contain python2_7 and python3_4 by +default via your profile. + +PYTHON_SINGLE_TARGET will remain set to python2_7 by default. + +If you have PYTHON_TARGETS set in make.conf, that setting will still be +respected. You may want to adjust this setting manually. + +Once the changes have taken place, a world update should take care of +reinstalling any python libraries you have installed. You should also +switch your default python3 interpreter using eselect python. + +For example: + +eselect python set --python3 python3.4 +emerge -uDv --changed-use @world diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-07-25-python-targets/2015-07-25-python-targets.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-07-25-python-targets/2015-07-25-python-targets.en.txt.asc new file mode 100644 index 0000000..ea7e36f --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-07-25-python-targets/2015-07-25-python-targets.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iF4EABEIAAYFAlWzsagACgkQRxvnM+8pGj8f6gD/REEK79IoxTdE0+GctUg17/iA +HRkBR+nCz+VOdHd2ziMA/1mGLGFMPlH+hTuTMwDXkqNZj6ubjQCmNwFrX3cntoAH +=eOWd +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-11-nepomuk-removal/2015-08-11-nepomuk-removal.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-11-nepomuk-removal/2015-08-11-nepomuk-removal.en.txt new file mode 100644 index 0000000..488c980 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-11-nepomuk-removal/2015-08-11-nepomuk-removal.en.txt @@ -0,0 +1,24 @@ +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-11-nepomuk-removal/2015-08-11-nepomuk-removal.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-11-nepomuk-removal/2015-08-11-nepomuk-removal.en.txt.asc new file mode 100644 index 0000000..5943672 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-11-nepomuk-removal/2015-08-11-nepomuk-removal.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.1 + +iQJ8BAABCgBmBQJVyjeuXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0N0Y0MTczMjZGRTRGODM5M0MzOTU4RDAy +OTU0NDVDRUY5MDcyRDJGAAoJEClURc75By0vv+AQAMkio+WhdU+gE3rDNdKuRts4 +aXafLqE8pIi+kcURGmsuWquc9hv90qcRgYdN7O12jIRHA9YLhsJCa8tbvDw9cP3r +17qG1FBwAE1qDDhWOAeMN+LovL5qnRnZNN52LSSbpFbCp7gzSwSGp+gRsNg3VYVW +LtwwYUm22DafFIfWAgk0ie/2H3JdTaJv/Ob++ZE6aQjlnLplQe9n0fGYmrp3EV8Y +gumVD3tH7327Ic2vexxvy/sWcPgbY4UeNXQKxlYkIpwcFzm/bjofqFHrq1xH5Dm5 +arxMb56M98U5oVtrWve1+7TVDbWsOfOEjaEliAuel7QjS6aAMlQHoWhpn1maFCZX +vpTVW6JS0o+GbTg39+oGxQ/x6WCuNUW/kf3Y4SWxYygL61nrf/lK7EyBKefF0IZd +G+HDFXkMff2WXE/bp8GZRoGz5UCpWaEqx7blhNNQRTI8AXFQpMPdLJGpkIiepRIl +1FRCNeZ5GMlXjszsTxyU6YomYHqK+nalV2olcb1mu8u8DuEMdFWfY9ckQtMYQJ1i +9bxAGtZuQMiEGBp0PJ4JxBgpnRYhsQyry6MCCdBN7vEeb0Gwd/i3baG2xb8FNIEw +TRHYpD1NlaPoF8L7x2qn9eNbJSgM0d/y5y0ZVWnUes/yczBZEEHUfL/S8o5cX3bb +1PVTIWOsEtz0mzFI5Mfy +=6hti +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-13-openssh-weak-keys/2015-08-13-openssh-weak-keys.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-13-openssh-weak-keys/2015-08-13-openssh-weak-keys.en.txt new file mode 100644 index 0000000..1c4f296 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-13-openssh-weak-keys/2015-08-13-openssh-weak-keys.en.txt @@ -0,0 +1,27 @@ +Title: OpenSSH 7.0 disables ssh-dss keys by default +Author: Mike Frysinger <vapier@gentoo.org> +Content-Type: text/plain +Posted: 2015-08-13 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: net-misc/openssh + +Starting with the 7.0 release of OpenSSH, support for ssh-dss keys has +been disabled by default at runtime due to their inherit weakness. If +you rely on these key types, you will have to take corrective action or +risk being locked out. + +Your best option is to generate new keys using strong algos such as rsa +or ecdsa or ed25519. RSA keys will give you the greatest portability +with other clients/servers while ed25519 will get you the best security +with OpenSSH (but requires recent versions of client & server). + +If you are stuck with DSA keys, you can re-enable support locally by +updating your sshd_config and ~/.ssh/config files with lines like so: + PubkeyAcceptedKeyTypes=+ssh-dss + +Be aware though that eventually OpenSSH will drop support for DSA keys +entirely, so this is only a stop gap solution. + +More details can be found on OpenSSH's website: + http://www.openssh.com/legacy.html diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-26-ruby-19-removal/2015-08-26-ruby-19-removal.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-26-ruby-19-removal/2015-08-26-ruby-19-removal.en.txt new file mode 100644 index 0000000..ddb00ac --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-26-ruby-19-removal/2015-08-26-ruby-19-removal.en.txt @@ -0,0 +1,26 @@ +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: 1 +News-Item-Format: 1.0 +Display-If-Installed: dev-lang/ruby + +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-26-ruby-19-removal/2015-08-26-ruby-19-removal.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-26-ruby-19-removal/2015-08-26-ruby-19-removal.en.txt.asc new file mode 100644 index 0000000..35a07d8 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-08-26-ruby-19-removal/2015-08-26-ruby-19-removal.en.txt.asc @@ -0,0 +1,13 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.1 + +iQF8BAABCgBmBQJV4bFzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGNEQyNDdEMTRGNDc0OEQwQTMyQ0MxRjA3 +NEQ5Rjc0RUVBQzZBM0IxAAoJEHTZ907qxqOxW2kIALxg863MY7tk4W9VCPyhS6LH +wwVKBT4nxemCnQANkhXvVn8cbvCVUB+mp9Tdt7mGFVFXjZuwEQovpem+ewr6Zqjp +n/WSDihR5raAg87vq14NtXVhkuYlqTEO402GXE1CdBboJeJh7M1dEMPFcz7E8Hp+ +MdCKw6I9mCTrvRR9fwaWuch1oMeR3dNEYLHYyUUiA5hZXNRXEO1Eb05HsXs+P/po +blyQqTLIEycJ7oNooZtVvqOOVrg/8j6teoZI2FOS138EwZGejySKy50ljWhbPST0 +p8DklsbtJGcxggnERYIMdAD06NG83OLahBcI6QRN2Jg4e+mcVFf9lJPyFutjfg8= +=WCcY +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-09-09-libvirt-init-script-changes/2015-09-09-libvirt-init-script-changes.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-09-09-libvirt-init-script-changes/2015-09-09-libvirt-init-script-changes.en.txt new file mode 100644 index 0000000..83ed083 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-09-09-libvirt-init-script-changes/2015-09-09-libvirt-init-script-changes.en.txt @@ -0,0 +1,24 @@ +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-09-09-libvirt-init-script-changes/2015-09-09-libvirt-init-script-changes.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-09-09-libvirt-init-script-changes/2015-09-09-libvirt-init-script-changes.en.txt.asc new file mode 100644 index 0000000..5ba22c3 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-09-09-libvirt-init-script-changes/2015-09-09-libvirt-init-script-changes.en.txt.asc @@ -0,0 +1,19 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0 + +iQJ8BAABCgBmBQJV8FXfXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNTM5MEQ2RTNFMTkyNzlCNzVDMzIwOTVB +MkJDMDNEQzg3RUQxQkQ0AAoJEKK8A9yH7RvU1vkP/R5H3l7EJJtFsyfNNYKacRTF +CuIaUsaSbOGehdS0NY3iEj41glDKT1XUrOQoDKuiKjSC1O2H6qkhBmy180Zl0VqB +6yCEiSYGC6VRlkCfD/6rLZa3pS6YRzNdNOPE8nsUo3vqcOFovgPEgzGoKb6h7dnp +quuPjed9vhPcjvEAkHrb0MGWGVt9EprSfGq2Pt3NsmEsx+8FY6VAVdTBc59nw7RS +xln4aKXKUW9nqreOILXoa+4afJrQpdEwqMm1dd2fHtfQny++aSPpldYrVPjkdBl7 +pqiTmM0nV81kyuxhhBpkPdW7DRURfXSHhGvGTwu0TuCznPacLQA8GtM8kdENTIQG +aY8qFDQHMOQXCDnJl5oRFO1V/rzGnvWhc/i46iU7C8nueIpZEwBiopG0dXmW1K0E +r1egYn2b2y/gymduUVk+ONMMjrH83iyHOmwyC7F5Xy1UhX01zbclDRzmnjN2Mo7h +ZoDWxapALYu0AplejgVUggnQAVjFHUDsg/HPAUafhgIuDDrW7PaUUxyYYQKbfWtK +5+5WBe6KonVSRqahnyE/5zpwfWKDHy99BwY+7hz0TboEgsDroUctX2N5OazDfyfg +zK60C1VcPgjzJJSnwaVkt6eAoaTHAYPFDO0kobL8ZJscPx2fGJc/1hubhNUAF/R+ +3lawwv3U7b5Xg+7+kmNk +=PNbk +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-07-openrc-0-18-localmount-and-netmount-changes/2015-10-07-openrc-0-18-localmount-and-netmount-changes.en.txt new file mode 100644 index 0000000..7b2b688 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-07-openrc-0-18-localmount-and-netmount-changes/2015-10-07-openrc-0-18-localmount-and-netmount-changes.en.txt @@ -0,0 +1,17 @@ +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-07-openrc-0-18-localmount-and-netmount-changes/2015-10-07-openrc-0-18-localmount-and-netmount-changes.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-07-openrc-0-18-localmount-and-netmount-changes/2015-10-07-openrc-0-18-localmount-and-netmount-changes.en.txt.asc new file mode 100644 index 0000000..eb9d832 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-07-openrc-0-18-localmount-and-netmount-changes/2015-10-07-openrc-0-18-localmount-and-netmount-changes.en.txt.asc @@ -0,0 +1,17 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iQIcBAABCAAGBQJWFU3/AAoJEJtAqO3K+uczmWwP/1gjGujAFj8NcxQaB6LM8eOr +BkBPe5xpTb6JqSaPZy6EKAziHgryk9RUUCCTF2EI0hrzB8sg79bJ7x1I/XoFMhKu +qQsRtvjtiLix75L08lgZ5KuQULba3ErOJJhoBLFM3mrGJNC0AgCN2it+HHbYPfdf +zR6jBfEtvsVzQ2LN6Fh6FQswtOyoag+lei2w//vLK9hFgrAkjGmjAl4G+UywW+hM +TAiwDuwdIn6izQ4Hfu1dmdA4ugdpMwVGIVwmoub/DbpNbpvQQMf8FGBgzzbGgWs3 +RSqZPOlfH3CX0E/jJanUY7l8YFtS3nd7XLPPFkB2WZ6fKqYF0DFTRtrcOqHDT88N +ksMFvnCt6jF/6r15/Sz9VUQoBfIEnMRLqeHfrH/MROVDTg9nnhY6uqYDr0Yn29pD +t8wGfgs5Kds0tiUxnCvcTBazRztVDKQZQPxUsrNBmGdVRf8L757ltMZofftZh8fl +SehUrA/YO+X1ROlUvvv5x9Ik6AAARcJOotTHbLWplayyC6f/bvAkmy8UnLXo30Zh +Z2rx3ZAZ0UuVYZWKWkXl1vJg8ANK93o7nvUTgc1/LVJhG5BoxceDEy4DJmXAiPgC +erghByQQfAi2aDlslql6mDx4XAQwuBFPYnkHZapGCgAlsSMw8Lh0Jkp0rw5ic3Q0 +QZyhSSWZkF7VjTRB6nY9 +=Bkvu +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt new file mode 100644 index 0000000..3d5c76c --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt @@ -0,0 +1,62 @@ +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/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt.asc new file mode 100644 index 0000000..31e9f24 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt.asc @@ -0,0 +1,17 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iQIcBAABCAAGBQJWLOeNAAoJEGYZIgZZJvHWlRwP/28YwYuwqSrJ8eOKl+PFITKI +0wlMT/zSSvLU5vOV/ukfS1mILWHIYMr6hNwKu4gqA9YLKUgmhCL1R5HsujFQo1/3 +4n9tSnBsNvdLTJEB15fe5htavwnLaxMBqVGCGALRl1INlYFBbmQjm2W5nX8Jw1Uv +WwayBk+9tfhvCw/gvfo904MNaS7Xhj3XiE8YIwpom6mjrjJV6hRX0OpcL/dByRfh +MN/03EdYzPl+sUd7LD3zMsmLCKSiOw+OoWg8zF/2Qr0oEuTrJIwtbxPCMQrMwh7p +NhDZwot2yQhlLqLN5jHtaxWo2HL+jnljWcbvuUlx5K9S4swhcYfVze4PdKszf5E0 +Nc/YCzewL+26f5F2xkD60B8lx5EXSL3ysdzm7zgqhn2rkSVy0AMNg+GduR81T+j1 +VmzFKDGWsthgH0xd552zs22dA3tAFya575pNFi5JlMUpu0Qha6zC9UDZ5RVcJmBJ +EBJVeAJLLkDpuPC3IMcVNr1UCG2TK5W3GimdY9nzjgZL2fvcXLmEYVHjVm/scDOy +8zJ8Nw/LWshT/jXgZfelFrgyL0+gm8NB4mVWTGZWAlBhzAoolIv+KbhVgyLQ1Pjh +7AQfyrr0KTpgW24kd9dnzCD2QnAM07AHNRmG/XMbtls8g+zVGl7zFQvWXGDPdrUC +2YBiOa9vmqOjbTJWeV7r +=R4yN +-----END PGP SIGNATURE----- diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-22-gcc-5-new-c++11-abi/2015-10-22-gcc-5-new-c++11-abi.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-22-gcc-5-new-c++11-abi/2015-10-22-gcc-5-new-c++11-abi.en.txt new file mode 100644 index 0000000..5f6ffbb --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-10-22-gcc-5-new-c++11-abi/2015-10-22-gcc-5-new-c++11-abi.en.txt @@ -0,0 +1,21 @@ +Title: GCC 5 Defaults to the New C++11 ABI +Author: Mike Frysinger <vapier@gentoo.org> +Content-Type: text/plain +Posted: 2015-10-22 +Revision: 1 +News-Item-Format: 1.0 +Display-If-Installed: >=sys-devel/gcc-5 + +GCC 5 uses the new C++ ABI by default. When building new code, you might run +into link time errors that include lines similar to: +...: undefined reference to '_ZNSt6chrono12steady_clock3nowEv@GLIBCXX_3.4.17' + +Or you might see linkage failures with "std::__cxx11::string" in the output. + +These are signs that you need to rebuild packages using the new C++ ABI. +You can quickly do so by using revdep-rebuild (from gentoolkit) like so: +# revdep-rebuild --library 'libstdc\+\+\.so\.6' -- --exclude gcc + +For more details, feel free to peruse: +https://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/ +https://blogs.gentoo.org/blueness/2015/03/10/the-c11-abi-incompatibility-problem-in-gentoo/ diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-12-16-python-abiflags-rebuild-needed/2015-12-16-python-abiflags-rebuild-needed.en.txt b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-12-16-python-abiflags-rebuild-needed/2015-12-16-python-abiflags-rebuild-needed.en.txt new file mode 100644 index 0000000..bc83653 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-12-16-python-abiflags-rebuild-needed/2015-12-16-python-abiflags-rebuild-needed.en.txt @@ -0,0 +1,46 @@ +Title: Python ABIFLAGS rebuild needed +Author: Mike Gilbert <floppym@gentoo.org> +Content-Type: text/plain +Posted: 2015-12-16 +Revision: 2 +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.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 + +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 should rebuild affected packages using the following command. + +emerge -1v $(find /usr/lib*/python3* -name '*cpython-3[3-5].so') + +You may experience build failures in related packages until this has been +completed. + +References: +[1] https://www.python.org/dev/peps/pep-3149/ diff --git a/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-12-16-python-abiflags-rebuild-needed/2015-12-16-python-abiflags-rebuild-needed.en.txt.asc b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-12-16-python-abiflags-rebuild-needed/2015-12-16-python-abiflags-rebuild-needed.en.txt.asc new file mode 100644 index 0000000..e69d853 --- /dev/null +++ b/gentoobrowse-api/unittests/fixtures/756569aa764177340726dd3d40b41d89b11b20c7/metadata/news/2015-12-16-python-abiflags-rebuild-needed/2015-12-16-python-abiflags-rebuild-needed.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2 + +iF4EABEIAAYFAlZy4MMACgkQRxvnM+8pGj9NvgD/YNEIOd4fNmM9YcFnRHEPstus +DUXXyRPRw2aagQwgrRkBAMn6ZW49Vof0uXQ8y0oU9BZ14xjAHwXYoZbBzn2TLdH1 +=PzBj +-----END PGP SIGNATURE----- |