diff options
Diffstat (limited to 'metadata/news')
13 files changed, 149 insertions, 284 deletions
diff --git a/metadata/news/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt b/metadata/news/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt deleted file mode 100644 index 926f6ffdb26b..000000000000 --- a/metadata/news/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt +++ /dev/null @@ -1,36 +0,0 @@ -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/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/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 deleted file mode 100644 index d074dbe27d24..000000000000 --- a/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 +++ /dev/null @@ -1,50 +0,0 @@ -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/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt b/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt index 5a2d2124ba42..aeff021602be 100644 --- a/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt +++ b/metadata/news/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt @@ -4,7 +4,7 @@ Content-Type: text/plain Posted: 2015-02-02 Revision: 1 News-Item-Format: 1.0 -Display-If-Installed: sys-apps/portage +Display-If-Installed: <sys-apps/portage-2.3.62 There is a new plug-in sync system in >=sys-apps/portage-2.2.16. This system will allow third party modules to be easily installed. Look diff --git a/metadata/news/2015-07-25-python-targets/2015-07-25-python-targets.en.txt b/metadata/news/2015-07-25-python-targets/2015-07-25-python-targets.en.txt deleted file mode 100644 index 720eb66760d2..000000000000 --- a/metadata/news/2015-07-25-python-targets/2015-07-25-python-targets.en.txt +++ /dev/null @@ -1,26 +0,0 @@ -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/metadata/news/2017-12-26-experimental-amd64-17-1-profiles/2017-12-26-experimental-amd64-17-1-profiles.en.txt b/metadata/news/2017-12-26-experimental-amd64-17-1-profiles/2017-12-26-experimental-amd64-17-1-profiles.en.txt deleted file mode 100644 index 44187995cbbe..000000000000 --- a/metadata/news/2017-12-26-experimental-amd64-17-1-profiles/2017-12-26-experimental-amd64-17-1-profiles.en.txt +++ /dev/null @@ -1,106 +0,0 @@ -Title: Experimental amd64 17.1 profiles up for testing -Author: Michał Górny <mgorny@gentoo.org> -Posted: 2017-12-26 -Revision: 3 -News-Item-Format: 2.0 -Display-If-Profile: default/linux/amd64/13.0 -Display-If-Profile: default/linux/amd64/13.0/selinux -Display-If-Profile: default/linux/amd64/13.0/desktop -Display-If-Profile: default/linux/amd64/13.0/desktop/gnome -Display-If-Profile: default/linux/amd64/13.0/desktop/gnome/systemd -Display-If-Profile: default/linux/amd64/13.0/desktop/plasma -Display-If-Profile: default/linux/amd64/13.0/desktop/plasma/systemd -Display-If-Profile: default/linux/amd64/13.0/developer -Display-If-Profile: default/linux/amd64/13.0/no-multilib -Display-If-Profile: default/linux/amd64/13.0/systemd -Display-If-Profile: default/linux/amd64/17.0 -Display-If-Profile: default/linux/amd64/17.0/selinux -Display-If-Profile: default/linux/amd64/17.0/hardened -Display-If-Profile: default/linux/amd64/17.0/hardened/selinux -Display-If-Profile: default/linux/amd64/17.0/desktop -Display-If-Profile: default/linux/amd64/17.0/desktop/gnome -Display-If-Profile: default/linux/amd64/17.0/desktop/gnome/systemd -Display-If-Profile: default/linux/amd64/17.0/desktop/plasma -Display-If-Profile: default/linux/amd64/17.0/desktop/plasma/systemd -Display-If-Profile: default/linux/amd64/17.0/developer -Display-If-Profile: default/linux/amd64/17.0/no-multilib -Display-If-Profile: default/linux/amd64/17.0/no-multilib/hardened -Display-If-Profile: default/linux/amd64/17.0/no-multilib/hardened/selinux -Display-If-Profile: default/linux/amd64/17.0/systemd - -A new set of 17.1 amd64 profiles has been added to the Gentoo -repository. Those profiles switch to a more standard 'no SYMLINK_LIB' -multilib layout, and require explicit migration as described below. They -are considered experimental at the moment, and have a fair risk -of breaking your system. We would therefore like to ask our users to -test them on their non-production ~amd64 systems. - -In those profiles, the lib->lib64 compatibility symlink is removed. -The 'lib' directory becomes a separate directory, that is used -for cross-arch and native non-library packages (gcc, clang) and 32-bit -libraries on the multilib profile (for better compatibility with -prebuilt x86 packages). - -Migration from both 13.0 and 17.0 profiles is supported. In case -of the former, please read the news item for 17.0 upgrade first -and enable gcc 6.4.0 or newer first as explained there. - -The migration is performed using app-portage/unsymlink-lib tool. -The following steps can be used to upgrade your system: - -1. Sync and upgrade your system to the newest package versions - to reduce the risk of issues. - -2. Install the tool, e.g. via 'emerge -1v app-portage/unsymlink-lib' - -3. Run 'unsymlink-lib --analyze' and check the output for obvious - mistakes. If you need to perform any changes to the system, remember - to run 'unsymlink-lib --analyze' again afterwards. - -[past this point do not call emerge or modify /usr manually] - -4. This is a very good time to make a backup. - -5. Run 'unsymlink-lib --migrate'. You can add '--pretend' first to see - what is going to happen. - -6. Reboot your system and see if it still boots. Check if important - programs work. In particular, check if e.g. 'emerge --info' works - (but do not install anything). If you hit any serious problems, - you can use 'unsymlink-lib --rollback' to revert the changes - and return to step 3. - -7. Run 'unsymlink-lib --finish'. You can add '--pretend' first to see - what is going to happen but note that you're going to see a very long - list of files to remove. - -8. Switch the profile, e.g.: - - eselect profile set --force default/linux/amd64/17.1/desktop - -[at this point you can start using emerge again] - -9. Rebuild sys-devel/gcc. If you are switching from 13.0 profiles, - rebuild sys-devel/binutils and sys-libs/glibc afterwards. - -10. If you are using a multilib profile, rebuild all 32-bit packages. - This can be done using: - - emerge -1v /lib32 /usr/lib32 - - Alternatively, if you are switching from one of the 13.0 profiles - you can rebuild all packages as detailed in the 17.0 news item. - -11. Once the last 32-bit package is rebuilt, your package manager - should remove the orphaned /lib32 and /usr/lib32 symlinks. If that - does not happen, remove them manually. - -For known issues, please see bug #506276 [1]. If you have any problems -with the new profiles or the migration procedure, please report a bug -and make it block the tracker. - -For more information on the layout, please see the wiki article -on AMD64 multilib layouts [2]. - -[1]:https://bugs.gentoo.org/506276 -[2]:https://wiki.gentoo.org/wiki/Project:AMD64/Multilib_layout diff --git a/metadata/news/2018-01-30-portage-rsync-verification/2018-01-30-portage-rsync-verification.en.txt b/metadata/news/2018-01-30-portage-rsync-verification/2018-01-30-portage-rsync-verification.en.txt index 1964855e4d1a..0e7fd910d7c8 100644 --- a/metadata/news/2018-01-30-portage-rsync-verification/2018-01-30-portage-rsync-verification.en.txt +++ b/metadata/news/2018-01-30-portage-rsync-verification/2018-01-30-portage-rsync-verification.en.txt @@ -3,7 +3,7 @@ Author: Michał Górny <mgorny@gentoo.org> Posted: 2018-01-30 Revision: 1 News-Item-Format: 2.0 -Display-If-Installed: sys-apps/portage +Display-If-Installed: <sys-apps/portage-2.3.62 Starting with sys-apps/portage-2.3.21, Portage will verify the Gentoo repository after rsync by default. diff --git a/metadata/news/2018-03-13-portage-rsync-verification-unstable/2018-03-13-portage-rsync-verification-unstable.en.txt b/metadata/news/2018-03-13-portage-rsync-verification-unstable/2018-03-13-portage-rsync-verification-unstable.en.txt deleted file mode 100644 index 9f96f2719235..000000000000 --- a/metadata/news/2018-03-13-portage-rsync-verification-unstable/2018-03-13-portage-rsync-verification-unstable.en.txt +++ /dev/null @@ -1,46 +0,0 @@ -Title: Portage rsync tree verification unstable -Author: Zac Medico <zmedico@gentoo.org> -Posted: 2018-03-13 -Revision: 1 -News-Item-Format: 2.0 -Display-If-Installed: sys-apps/portage - -Portage rsync tree verification is being temporarily turned off by -default, starting with sys-apps/portage-2.3.24. This permits -stabilization of sys-apps/portage-2.3.24 while still working on bugs -relating to tree verification [1]: deadlocks [2] & key fetching [3]. - -If users wish to enable the 'rsync-verify' USE flag for sys-apps/portage, -they need to follow these steps: - -1) In order to unmask the 'rsync-verify' USE flag, create a file named -/etc/portage/profile/package.use.mask containing a line like the -following: - - sys-apps/portage -rsync-verify - -2) Once the 'rsync-verify' USE flag has been unmasked as described -in step 1, it can be enabled with a line like the following in -/etc/portage/package.use: - - sys-apps/portage rsync-verify - -3) After the configuration changes in steps 1 and 2 have been made, run -the following command: - - emerge --oneshot --newuse '>=sys-apps/portage-2.3.24' - -After all above steps are successfully completed, a line like the -following should appear in the emerge --info output for the gentoo -repository: - - sync-rsync-verify-metamanifest: yes - -If you wish to disable it for some reason, you can set -'sync-rsync-verify-metamanifest = no' in your repos.conf. - -[1] https://bugs.gentoo.org/650144 sys-apps/portage: [TRACKER] issues - related to 'rsync-verify' USE flag -[2] https://bugs.gentoo.org/647964 app-portage/gemato-11.2: deadlock? -[3] https://bugs.gentoo.org/649276 sys-apps/portage: gpg key refresh - needs exponential backoff with jitter diff --git a/metadata/news/2018-07-11-portage-sync-allow-hardlinks/2018-07-11-portage-sync-allow-hardlinks.en.txt b/metadata/news/2018-07-11-portage-sync-allow-hardlinks/2018-07-11-portage-sync-allow-hardlinks.en.txt index d64f0cb3fe36..18dc6b395842 100644 --- a/metadata/news/2018-07-11-portage-sync-allow-hardlinks/2018-07-11-portage-sync-allow-hardlinks.en.txt +++ b/metadata/news/2018-07-11-portage-sync-allow-hardlinks/2018-07-11-portage-sync-allow-hardlinks.en.txt @@ -3,7 +3,7 @@ Author: Zac Medico <zmedico@gentoo.org> Posted: 2018-07-11 Revision: 1 News-Item-Format: 2.0 -Display-If-Installed: sys-apps/portage +Display-If-Installed: <sys-apps/portage-2.3.62 For users of the rsync tree, beginning with sys-apps/portage-2.3.42, the default behavior for sync operations will use hardlinks in order diff --git a/metadata/news/2019-06-05-amd64-17-1-profiles-are-now-stable/2019-06-05-amd64-17-1-profiles-are-now-stable.en.txt b/metadata/news/2019-06-05-amd64-17-1-profiles-are-now-stable/2019-06-05-amd64-17-1-profiles-are-now-stable.en.txt new file mode 100644 index 000000000000..8684e63b2c6d --- /dev/null +++ b/metadata/news/2019-06-05-amd64-17-1-profiles-are-now-stable/2019-06-05-amd64-17-1-profiles-are-now-stable.en.txt @@ -0,0 +1,129 @@ +Title: amd64 17.1 profiles are now stable +Author: Michał Górny <mgorny@gentoo.org> +Posted: 2019-06-05 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Profile: default/linux/amd64/13.0 +Display-If-Profile: default/linux/amd64/13.0/selinux +Display-If-Profile: default/linux/amd64/13.0/desktop +Display-If-Profile: default/linux/amd64/13.0/desktop/gnome +Display-If-Profile: default/linux/amd64/13.0/desktop/gnome/systemd +Display-If-Profile: default/linux/amd64/13.0/desktop/plasma +Display-If-Profile: default/linux/amd64/13.0/desktop/plasma/systemd +Display-If-Profile: default/linux/amd64/13.0/developer +Display-If-Profile: default/linux/amd64/13.0/no-multilib +Display-If-Profile: default/linux/amd64/13.0/systemd +Display-If-Profile: default/linux/amd64/17.0 +Display-If-Profile: default/linux/amd64/17.0/selinux +Display-If-Profile: default/linux/amd64/17.0/hardened +Display-If-Profile: default/linux/amd64/17.0/hardened/selinux +Display-If-Profile: default/linux/amd64/17.0/desktop +Display-If-Profile: default/linux/amd64/17.0/desktop/gnome +Display-If-Profile: default/linux/amd64/17.0/desktop/gnome/systemd +Display-If-Profile: default/linux/amd64/17.0/desktop/plasma +Display-If-Profile: default/linux/amd64/17.0/desktop/plasma/systemd +Display-If-Profile: default/linux/amd64/17.0/developer +Display-If-Profile: default/linux/amd64/17.0/no-multilib +Display-If-Profile: default/linux/amd64/17.0/no-multilib/hardened +Display-If-Profile: default/linux/amd64/17.0/no-multilib/hardened/selinux +Display-If-Profile: default/linux/amd64/17.0/systemd + +A new set of 17.1 amd64 profiles has been added to the Gentoo +repository in Dec 2017. These profiles switch to a more standard +'no SYMLINK_LIB' multilib layout, and require explicit migration as +described below. They are considered stable at the moment, and we would +like to request all users to upgrade their systems. The old profiles +will be deprecated in the near future. + +In the new profiles, the lib->lib64 compatibility symlink is removed. +64-bit libraries need to be installed directly to lib64. /lib +and /usr/lib become real directories, that are used for cross-arch +and native non-library packages (gcc, clang) and 32-bit libraries +on the multilib profile (which improves compatibility with prebuilt x86 +packages). + +Migration from both 13.0 and 17.0 profiles is supported. In case +of the former, reading the news item for 17.0 upgrade [1] +is recommended. + +The migration is performed using app-portage/unsymlink-lib tool. +The following steps can be used to upgrade your system: + +1. Sync and upgrade your system to the newest package versions + to reduce the risk of issues. + +2. If you are still running a 13.0 profile, select gcc 6.4.0 or later + as the system compiler, source /etc/profile and reinstall libtool: + + # gcc-config -l + [1] x86_64-pc-linux-gnu-5.5.0 * + [2] x86_64-pc-linux-gnu-8.3.0 + # gcc-config 2 + # . /etc/profile + # emerge -1v libtool + +3. Install the tool: + + # emerge -1v app-portage/unsymlink-lib + +4. Run 'unsymlink-lib --analyze' and check the output for obvious + mistakes. If you need to perform any changes to the system, remember + to run 'unsymlink-lib --analyze' again afterwards. + +[past this point do not call emerge or modify /usr manually] + +5. This is a very good time to make a backup. + +6. Run 'unsymlink-lib --migrate'. You can add '--pretend' first to see + what is going to happen. + +7. Reboot your system. Check if important programs work. + In particular, verify that e.g. 'emerge --info' works (but do not + install anything). If you hit any serious problems, you can use + 'unsymlink-lib --rollback' to revert the changes and return to + step 4. + +8. Run 'unsymlink-lib --finish'. You can add '--pretend' first to see + what is going to happen but note that you're going to see a very long + list of files to remove. + +9. Switch the profile, e.g.: + + # eselect profile set default/linux/amd64/17.1/desktop + +[at this point you can start using emerge again] + +10. Rebuild the toolchain: + + # emerge -1v sys-devel/gcc:8.3.0 + [ repeat for other slots you will be using ] + [ if you are upgrading from 13.0 profile, also: ] + # emerge -1v sys-devel/binutils + # emerge -1v sys-libs/glibc + +11. If you are using a multilib profile, rebuild all 32-bit packages. + This can be done using: + + # emerge -1v /lib32 /usr/lib32 + + Alternatively, if you are switching from one of the 13.0 profiles + you can rebuild all packages as detailed in the 17.0 news item: + + # emerge -ev @world + +12. Once the last 32-bit package is rebuilt, your package manager + should remove the orphaned /lib32 and /usr/lib32 symlinks. If that + does not happen, remove them manually: + + # rm /lib32 /usr/lib32 + +For known issues, please see bug #506276 [2]. If you have any problems +with the new profiles or the migration procedure, please report a bug +and make it block the tracker. + +For more information on the layout, please see the wiki article +on AMD64 multilib layouts [3]. + +[1] https://gentoo.org/support/news-items/2017-11-30-new-17-profiles.html +[2] https://bugs.gentoo.org/506276 +[3] https://wiki.gentoo.org/wiki/Project:AMD64/Multilib_layout diff --git a/metadata/news/Manifest b/metadata/news/Manifest index 96421a36b5b8..11bbe4c59c60 100644 --- a/metadata/news/Manifest +++ b/metadata/news/Manifest @@ -1,23 +1,23 @@ -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 -MANIFEST Manifest.files.gz 12603 BLAKE2B a79d75e4f4662a5da90ee4742ec303db4c73f3bb97f6217d05e943f5776a211906d5999decd77485dc272c9920e24e7cbf107d907c8e34585539a285d149db6d SHA512 bfd34ad827e1416c9556f6e5a654d6eafab7e565285294931a98718aeb0bdcc2506ab7792bb5fda3a428b3e6707642cf97a453216e768a31f3b6a3ae0d51d34c -TIMESTAMP 2019-06-02T20:08:57Z +MANIFEST Manifest.files.gz 11866 BLAKE2B f23bc74aa78c3a8573f47feacf2e5cc14f70bf31dba9eb6bba372431df427cf98b4316a4d1656a092d484f4cbaa8b06d94f7c624e8c976d1874619bcf0fd26ed SHA512 7cc5cfddda8eabcceabfdc97b1fcc9f794240a08288a5eb4cd91d0ddc9f8278dc119c2ae6d3712515aa16ed39855c9566a005818a70d5770fdc1d6d497e0558b +TIMESTAMP 2019-06-08T07:08:50Z -----BEGIN PGP SIGNATURE----- -iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAlz0LNpfFIAAAAAALgAo +iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAlz7XwJfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUx RDZBQkI2M0JGQ0ZCNEJBMDJGREYxQ0VDNTkwRUVBQzkxODkyNTAACgkQ7FkO6skY -klCqgQ//daf1/7kAzySmJEKcUZG4cbKRDQEVQqlPdvrgmH0Oyxaf98JbhXCW1u46 -002/55qMGC3eCIUdrxB/t7KRPKzVX1IFY80XAtAoC6uZCYaLPoAEXZP+5OasRcSw -XXuZXVfUPTQAd62aiyfkFU69vutnD+Iqs+hGhr9wdYLzLeagmAFUTu8WU1fXtr1Z -rYtUa/U584KGoTNlya8fUQdKLW59ma/HpJUvQ/YuXcBasTo3ZlxHkPcE1ltm+qXu -NHl1VN1t6ULQwrz638WZe7I1qRfylX3N/3xwBQKxH6rO4d3LXCF1/J1ogwt0azld -Fo4iJFcCutW3VNnnBUr+O5A1FtPuqdJh3iDZiAfaMOe5SEpG93puxmGHtZfrzuaf -i0IoX64QdqZUt6EKDPB4vNpOdcdlL1TnxXPVSl4y0CYztb5roR/xziMLuosJX8X/ -zoO35UTU74DkV9xKNDYvtExCHJYqvYkz4EKc32Q49sj2aNQkLBcQHQV+LM7iZEoc -zE/zIniUmFNYheh2gwYYEbL/LPBIwTDMElPrUFrQqOkj2wHHciuKZEvTKQ87/blQ -YRZOV8TD8VH47U4tdnRzt7UF1SXj2AvfXFrKrstvK+23L7yudiirxsr24YPKGx86 -u/Z0hvvBermZ1lqTPFdkCpcaghasJfxgY/FOAfqdBtd0QkQnuuc= -=mOQj +klBzcA/8COXZ2fQ6Uq3lb2Ej+RRHPxaRBKtlCCqwXCSdf6DW+qu2MmjdHw0HhwFW +YufzbZgd8BqJ6ieeEoiCfnxJtCGu6+JfWGmdgWYN1XYRfp8AluXEz+w3Q37et5OW +85QunI55s6rcPj5+9S2KeaZRh4A4dEwt4+DmvReEYhGlvIxRVkj8T71Jyo1mTg1m +4NKp6YGzF6Vy/SimLai+bWx5oIymQAjlnCiNTAeUBhav3LWejQBONsCrdGJV++Un +L5ftLiRbDogYqs55hw1kbJWiMkzaPL/YY27vNqMlJG6pfQjJV78PSZQz5SZ8HL7t +X1V/4n7DCEwJfioMWA9wS7tk2a5dtCrHpIbxpokzMnNOEemdYhLsprKCE++q+OCg +a4eZGr4eXDl2lpOpuIpQat8HtT3buScUOXRjPMIQUrFf+rxavfrzgHUgPJz37yJ2 +OBC728NYN4/WMgqRMMHzEg7cyV9DrZeiGfYqJgAueTaM4Vlu+uEdZSPPR4jd5JVk +FfNyyWd5tg5MrztR5XjslX5CaktKe4iW3RumYZF+VX4X5YLTxsFXkbNhQrZH26Ri +crAvNAJIWjvej9GcWxxTh2tjV5qHUzIssYy48B0BFCydyURCnyo8w4kh6V2Un7hz +UvsEjjrdcfASnHLnnyLYeAZN2UPXPNLl6roP1Y8Nq6BI8OkeKQY= +=E39D -----END PGP SIGNATURE----- diff --git a/metadata/news/Manifest.files.gz b/metadata/news/Manifest.files.gz Binary files differindex 8670e60f29fe..9ece3ebe4280 100644 --- a/metadata/news/Manifest.files.gz +++ b/metadata/news/Manifest.files.gz diff --git a/metadata/news/timestamp.chk b/metadata/news/timestamp.chk index a5240019f154..94f5d443814c 100644 --- a/metadata/news/timestamp.chk +++ b/metadata/news/timestamp.chk @@ -1 +1 @@ -Sun, 02 Jun 2019 20:08:54 +0000 +Sat, 08 Jun 2019 07:08:46 +0000 diff --git a/metadata/news/timestamp.commit b/metadata/news/timestamp.commit index 327cd79b4562..0670e204cd23 100644 --- a/metadata/news/timestamp.commit +++ b/metadata/news/timestamp.commit @@ -1 +1 @@ -8c82e8e72bf9157172b8a153ac8927c9f06500fd 1559295613 2019-05-31T09:40:13+00:00 +1823d8a300bfe87eb459fc10278d630a1ec37a3d 1559922844 2019-06-07T15:54:04+00:00 |