diff options
Diffstat (limited to 'metadata/news')
10 files changed, 448 insertions, 94 deletions
diff --git a/metadata/news/2017-02-10-upgrade-to-sys-libs_uclibc-ng-1_0_22/2017-02-10-upgrade-to-sys-libs_uclibc-ng-1_0_22.en.txt b/metadata/news/2017-02-10-upgrade-to-sys-libs_uclibc-ng-1_0_22/2017-02-10-upgrade-to-sys-libs_uclibc-ng-1_0_22.en.txt deleted file mode 100644 index b413ce40a58b..000000000000 --- a/metadata/news/2017-02-10-upgrade-to-sys-libs_uclibc-ng-1_0_22/2017-02-10-upgrade-to-sys-libs_uclibc-ng-1_0_22.en.txt +++ /dev/null @@ -1,77 +0,0 @@ -Title: Upgrade to =sys-libs/uclibc-ng-1.0.22 -Author: Anthony G. Basile <blueness@gentoo.org> -Content-Type: text/plain -Posted: 2017-02-10 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: sys-libs/uclibc-ng -Display-If-Profile: default/linux/uclibc/amd64 -Display-If-Profile: hardened/linux/uclibc/amd64 -Display-If-Profile: default/linux/uclibc/arm/armv7a -Display-If-Profile: hardened/linux/uclibc/arm/armv7a -Display-If-Profile: default/linux/uclibc/mips -Display-If-Profile: hardened/linux/uclibc/mips -Display-If-Profile: default/linux/uclibc/mips/mipsel -Display-If-Profile: hardened/linux/uclibc/mips/mipsel -Display-If-Profile: default/linux/uclibc/ppc -Display-If-Profile: hardened/linux/uclibc/ppc -Display-If-Profile: default/linux/uclibc/x86 -Display-If-Profile: hardened/linux/uclibc/x86 - -There have been two major changes in uclibc-ng which need special -attention when upgrading. Version 1.0.19 restructured the breakout -libraries, libcrypt.so.0, libdl.so.0, and friends. The functions in -those libraries are now included in libuClibc-0.1.0.19.so. Version -1.0.21 and above removed libc support for obstack, expecting packages to -use their bundled GNU lib code. Both changes require special upgrade -procedures which we outline below: - -0. Because of changes in the library structure in previous versions, -make sure you are working with 1.0.19 and rebuild world using - - emerge -e @world - -This will make sure all the executables link directly against libc.so.0 -(as reported by `readelf -d`) rather than via symlinks like libdl.so.0 --> libc.so.0. Then upgrade from 1.0.19 to 1.0.20 without symlink-compat: - - USE="-symlink-compat" emerge =sys-libs/uclibc-ng-1.0.20 - -1. Get rid of the obstack.h header since it's used by configure scripts -to look for function prototypes and macros. - - mv /usr/include/obstack.h ~ - -2. We also need to force the use of any bundled gnu lib code. We can do -this by removing the definition of _GNU_OBSTACK_INTERFACE_VERSION from -gnu-version.h - - cp /usr/include/gnu-versions.h ~ - sed -i -e '/#define _GNU_OBSTACK/d' /usr/include/gnu-versions.h - -3. We need to tell stdio.h that __UCLIBC_HAS_OBSTACK__ is false. We do -this via the uClibc_config.h file. - - cp /usr/include/bits/uClibc_config.h ~ - sed -i -e '/__UCLIBC_HAS_OBSTACK__/ s/1/0/' \ - /usr/include/bits/uClibc_config.h - -4. To be safe, you may want to back up your entire /lib directory so -you can fall back should something go wrong: - - cp -a /lib /lib.bak - -5. Now when we rebuild @world, all packages will use their bundled -obstack code rather than depending on libc to provide it. - - ac_cv_func_obstack_vprintf=no emerge --keep-going --exclude \ - sys-libs/uclibc-ng -e @world - -6. Finally update uclibc-ng to the latest - - emerge =sys-libs/uclibc-ng-1.0.22 - -7. For good measure, rebuild the entire system - - emerge —e @world - diff --git a/metadata/news/2024-05-06-wireplumber-0_5-bump/2024-05-06-wireplumber-0_5-bump.en.txt b/metadata/news/2024-05-06-wireplumber-0_5-bump/2024-05-06-wireplumber-0_5-bump.en.txt new file mode 100644 index 000000000000..d2524741f181 --- /dev/null +++ b/metadata/news/2024-05-06-wireplumber-0_5-bump/2024-05-06-wireplumber-0_5-bump.en.txt @@ -0,0 +1,25 @@ +Title: media-video/wireplumber-0.5.2 may break on upgrade +Author: James Calligeros <jcalligeros99@gmail.com> +Posted: 2024-05-06 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: media-video/wireplumber + +As some will be aware, WirePlumber 0.5.0 introduced a significant +breaking change to its entire configuration system, eliminating the use +of Lua scripts for configuration purposes. This also came with a +complete rework of how Lua scripts are registered with WirePlumber +for execution. + +Most typical desktop users, including EasyEffects users, should not +notice any change to their system. That said, it was not uncommon for +people to suggest or implement configuration changes using the Lua API. + +Any custom functionality which relies on WirePlumber's Lua API will +break upon upgrade. + +If you rely on this functionality, please review the WirePlumber +documentation on porting your Lua scripts to the new API and +registering them with the system before upgrading: + +https://pipewire.pages.freedesktop.org/wireplumber/daemon/configuration/migration.html diff --git a/metadata/news/2024-05-07-perl-features-use-expand/2024-05-07-perl-features-use-expand.en.txt b/metadata/news/2024-05-07-perl-features-use-expand/2024-05-07-perl-features-use-expand.en.txt new file mode 100644 index 000000000000..417238f3c1b0 --- /dev/null +++ b/metadata/news/2024-05-07-perl-features-use-expand/2024-05-07-perl-features-use-expand.en.txt @@ -0,0 +1,31 @@ +Title: dev-lang/perl useflags become a PERL_FEATURES use-expand +Author: Andreas K. Huettel <dilfridge@gentoo.org> +Posted: 2024-05-07 +Revision: 2 +News-Item-Format: 2.0 + +Starting with dev-lang/perl-5.38.2-r3, the three use flags "debug", +"ithreads", and "quadmath" of Perl are renamed into a common +use-expand variable, PERL_FEATURES, which should be set *globally* +in make.conf. + +If you do *not* want to change the settings of your Perl, make +sure that the new variable PERL_FEATURES contains the same settings +that were applied to your Perl all along. + +I.e., if you have dev-lang/perl[ithreads] installed, make sure +to now set in make.conf + PERL_FEATURES="ithreads" + +If you *want* to change the settings of your Perl, you may have to +run perl-cleaner after rebuilding dev-lang/perl: + perl-cleaner --modules ; perl-cleaner --force --libperl + +In either case, a full world update + emerge -uDNav world +is recommended and should also bring your system into a consistent +state. + +Background: This change in the structure of the useflags is +intended to solve bug 930123. The three useflags influence not only +how Perl itself is installed, but also all Perl modules... diff --git a/metadata/news/2024-05-09-python3-12/2024-05-09-python3-12.en.txt b/metadata/news/2024-05-09-python3-12/2024-05-09-python3-12.en.txt new file mode 100644 index 000000000000..cedb196d7b3d --- /dev/null +++ b/metadata/news/2024-05-09-python3-12/2024-05-09-python3-12.en.txt @@ -0,0 +1,120 @@ +Title: Python 3.12 to become the default on 2024-06-01 +Author: Michał Górny <mgorny@gentoo.org> +Posted: 2024-05-09 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: dev-lang/python:3.10 +Display-If-Installed: dev-lang/python:3.11 + +We are planning to switch the default Python target of Gentoo systems +on 2024-06-01, from Python 3.11 to Python 3.12. If you have not changed +the values of PYTHON_TARGETS or PYTHON_SINGLE_TARGET, the change will +have immediate effect on your system and the package manager will try +to switch automatically on the next upgrade following the change. + +If you did change the values, prefer a safer approach or have problems +with the update, read on. + +Please note that the default upgrade method switches packages to the new +Python versions as they are rebuilt. This means that all interdependent +packages have to support the new version for the upgrade to proceed, +and that some programs may temporarily fail to find their dependencies +throughout the upgrade (although programs that are already started +are unlikely to be affected). + + +If you have PYTHON_TARGETS or PYTHON_SINGLE_TARGET declared +in make.conf, please remove these declarations as they will interfere +with the package.use samples provided below. Using make.conf for Python +targets is discouraged as it prevents package defaults from applying +when necessary. This news item assumes using /etc/portage/package.use +or your package manager's equivalent file for configuration. + + +At this point, you have a few configuration options to choose from: + +1. If you wish Python upgrades to apply automatically, you can remove + PYTHON_TARGETS and PYTHON_SINGLE_TARGET declarations. When + the defaults change, your package manager should handle the upgrade + automatically. However, you may still need to run the update + commands if any problems arise. + +2. If you wish to defer the upgrade for the time being, you can + explicitly set the old values in package.use. + +3. If you wish to force the upgrade earlier, you can explicitly set + the new values and run the upgrade commands. + +4. If you wish to use a safer approach (i.e. less likely to temporarily + break packages during the upgrade), you can perform a multi-step + upgrade as outlined below. + +5. Finally, you can use an arbitrary combination of PYTHON_TARGETS + and PYTHON_SINGLE_TARGET. + + +Deferring the upgrade +===================== +To defer the upgrade, explicitly set the old targets: + + */* PYTHON_TARGETS: -* python3_11 + */* PYTHON_SINGLE_TARGET: -* python3_11 + +This will enforce Python 3.11 and block any future updates. However, +please note that this is only a temporary solution and you will +eventually need to perform the migration. + + +Forcing the upgrade +=================== +To force the upgrade earlier, explicitly select the Python 3.12 targets: + + */* PYTHON_TARGETS: -* python3_12 + */* PYTHON_SINGLE_TARGET: -* python3_12 + +However, it is important to remember to remove this after the defaults +change, as it will interfere with the automatic switch to the next +Python version in the future. + + +Safer upgrade procedure +======================= +A safer approach is to add Python 3.12 support to your system first, +and only then remove Python 3.11. However, note that this involves two +rebuilds of all the affected packages, so it will take noticeably +longer. + +First, enable both Python 3.11 and Python 3.12, and then run the upgrade +commands: + + */* PYTHON_TARGETS: -* python3_11 python3_12 + */* PYTHON_SINGLE_TARGET: -* python3_11 + +Then switch PYTHON_SINGLE_TARGET and run the second batch of upgrades: + + */* PYTHON_TARGETS: -* python3_11 python3_12 + */* PYTHON_SINGLE_TARGET: -* python3_12 + +Finally, switch to the final version and upgrade: + + */* PYTHON_TARGETS: -* python3_12 + */* PYTHON_SINGLE_TARGET: -* python3_12 + +You may wish to remove the target overrides after the defaults switch. +Alternatively, you can keep them to block the next automatic upgrade +to Python 3.13, and upgrade manually then. + + +Upgrade commands +================ +The Python 3.11 cleanup requires that Python 3.11 is removed from +the complete dependency trees in batch. If some of the +installed packages using an older Python version are not triaged +for the upgrade, the package manager will throw dependency conflicts. +This makes it important that the upgrade is carried via a --deep +--changed-use @world upgrade, as well as that any stray packages +are removed prior to it, e.g.: + + emerge --depclean + emerge -1vUD @world + emerge --depclean diff --git a/metadata/news/2024-05-09-python3-12/2024-05-09-python3-12.pl.txt b/metadata/news/2024-05-09-python3-12/2024-05-09-python3-12.pl.txt new file mode 100644 index 000000000000..0870e41bed56 --- /dev/null +++ b/metadata/news/2024-05-09-python3-12/2024-05-09-python3-12.pl.txt @@ -0,0 +1,133 @@ +Title: Python 3.12 stanie się domyślną wersją począwszy od 2024-06-01 +Author: Michał Górny <mgorny@gentoo.org> +Translator: Michał Górny <mgorny@gentoo.org> +Posted: 2024-05-09 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: dev-lang/python:3.10 +Display-If-Installed: dev-lang/python:3.11 + +Gentoo planuje zmienić domyślną wersję Pythona z 3.11 na 3.12 w dniu +1. czerwca 2024 r. Użytkownicy, którzy nie zmieniali wartości flag +PYTHON_TARGETS oraz PYTHON_SINGLE_TARGET nie muszą nic robić. Menadżer +pakietów automatycznie zaktualizuje wsparcie Pythona do nowej wersji +przy kolejnej aktualizacji systemu po tej zmianie. + +Informacje zawarte w tej wiadomości przeznaczone są dla użytkowników, +którzy zmieniali preferowaną wersję Pythona bądź chcą przeprowadzić +aktualizację w bezpieczniejszy sposób. + +Uwaga: standardowa metoda aktualizacji podmienia obsługiwaną wersję +Pythona w poszczególnych pakietach w miarę ich aktualizacji. +Oznacza to, że aktualizacja systemu możliwa będzie wyłącznie, jeżeli +wszystkie zainstalowane pakiety obsługują nową wersję. W trakcie +aktualizacji zależności poszczególnych zainstalowanych programów mogą +stać się tymczasowo niedostępne, nie powinno to jednak mieć wpływu +na działanie już uruchomionych aplikacji. + + +Użytkownicy, którzy wykorzystują plik make.conf do ustawienia wartości +zmiennych PYTHON_TARGETS lub PYTHON_SINGLE_TARGET powinni usunąć +te wartości, gdyż będą one kolidowały z przykładami package.use +przedstawionymi w tej wiadomości. Wykorzystywanie pliku make.conf +do konfiguracji tych zmiennych jest niewskazane, gdyż ustawienia te +nadpisują domyślne wartości flag zawarte w poszczególnych pakietach. +Dalszy ciąg tej wiadomości zakłada wykorzystywanie package.use +lub równoważnego pliku konfiguracyjnego. + + +Dostępne są następujące możliwości aktualizacji: + +1. Automatyczna aktualizacja wersji Pythona. Aby skorzystać z tej + opcji, należy usunąć zmienne PYTHON_TARGETS + oraz PYTHON_SINGLE_TARGET. Wówczas menadżer pakietów automatycznie + przeprowadzi aktualizację ilekroć zmieni się domyślna wersja Pythona + w Gentoo. Niemniej, może zaistnieć konieczność ręcznej aktualizacji + w przypadku wystąpienia problemów. + +2. Odroczenie aktualizacji poprzez wymuszenie poprzedniej wersji + w pliku package.use. + +3. Wymuszenie wcześniejszej aktualizacji poprzez podanie nowej wersji + i dokonanie aktualizacji systemu. + +4. Zastosowanie bezpiecznego podejścia (tj. zmniejszającego ryzyko + niesprawnych programów w trakcie aktualizacji) poprzez wykonanie + aktualizacji w kilku krokach. Proces ten jest szczegółowo opisany + w dalszej części wiadomości. + +5. Zastosowanie dowolnej kombinacji zmiennych PYTHON_TARGETS + oraz PYTHON_SINGLE_TARGET. + + +Odroczenie aktualizacji +======================= +Aby odroczyć aktualizację do późniejszego terminu, należy wymusić +poprzednią wersję Pythona: + + */* PYTHON_TARGETS: -* python3_11 + */* PYTHON_SINGLE_TARGET: -* python3_11 + +W ten sposób Python 3.11 zostanie wymuszony na stałe i przyszłe +aktualizacje zostaną zablokowane. Należy jednak pamiętać, że jest +to rozwiązanie tymczasowe i w przyszłości aktualizacja stanie się +konieczna. + + +Wymuszenie aktualizacji +======================= +Aby wymusić aktualizację wcześniej, należy wybrać Pythona 3.12: + + */* PYTHON_TARGETS: -* python3_12 + */* PYTHON_SINGLE_TARGET: -* python3_12 + +Zalecane jest jednak usunięcie tych ustawień po podanym wyżej terminie, +aby nie kolidowały w przyszłości z kolejną zmianą domyślnej wersji +Pythona. + + +Bezpieczna procedura aktualizacji +================================= +Bezpieczniejszą alternatywą do standardowego procesu jest wprowadzenie +wsparcia Pythona 3.12 w pierwszym kroku, a następnie usunięcie Pythona +3.11. Należy jednak pamiętać, że będzie wymagało to dwukrotnego +przebudowania wszystkich pakietów używających Pythona, tak więc łączny +czas aktualizacji zostanie wydłużony. + +Najpierw załączyć należy obydwie wersje Pythona i przeprowadzić +aktualizację systemu: + + */* PYTHON_TARGETS: -* python3_11 python3_12 + */* PYTHON_SINGLE_TARGET: -* python3_11 + +Następnie przełączyć należy wartość PYTHON_SINGLE_TARGET i przebudować +pakiety używające tych flag: + + */* PYTHON_TARGETS: -* python3_11 python3_12 + */* PYTHON_SINGLE_TARGET: -* python3_12 + +W ostatnim kroku należy wyłączyć poprzednią wersję i przeprowadzić +kolejną aktualizację: + + */* PYTHON_TARGETS: -* python3_12 + */* PYTHON_SINGLE_TARGET: -* python3_12 + +Po terminie zmiany domyślnych wartości, konfigurację tę można usunąć. +Alternatywnie, pozostawienie jej zablokuje przyszłą aktualizację +do Pythona 3.13 i pozwoli na ręczne przeprowadzenie bezpieczniej +aktualizacji. + + +Proces aktualizacji +=================== +Usunięcie Pythona 3.11 wymaga, by odpowiednie flagi zostały jednocześnie +wyłączone w całym drzewie zależności. Jeżeli niektóre z zainstalowanych +pakietów nie zostaną uwzględnione w planowanej aktualizacji, mogą one +zablokować ten proces. Dlatego też istotne jest przeprowadzenie +aktualizacji przy pomocy parametrów `--deep --changed-use @world` bądź +równoważnych, jak również wcześniejsze usunięcie niepotrzebnych +pakietów. Można tego dokonać używając poleceń: + + emerge --depclean + emerge -1vUD @world + emerge --depclean diff --git a/metadata/news/2024-05-17-dracut-ext-kmods/2024-05-17-dracut-ext-kmods.en.txt b/metadata/news/2024-05-17-dracut-ext-kmods/2024-05-17-dracut-ext-kmods.en.txt new file mode 100644 index 000000000000..af58a6386afe --- /dev/null +++ b/metadata/news/2024-05-17-dracut-ext-kmods/2024-05-17-dracut-ext-kmods.en.txt @@ -0,0 +1,122 @@ +Title: Changes to dracut kernel module/microcode handling +Author: Andrew Ammerlaan <andrewammerlaan@gentoo.org> +Posted: 2024-05-17 +Revision: 2 +News-Item-Format: 2.0 +Display-If-Installed: sys-kernel/dracut +Display-If-Installed: virtual/dist-kernel +Display-If-Installed: sys-kernel/linux-firmware +Display-If-Installed: sys-firmware/intel-microcode + + +Impact +==================== + +Several changes were made regarding out-of-tree kernel modules, CPU +microcode, and how these are handled in initial RAM file systems +(initramfs) generated by sys-kernel/dracut for distribution kernels. +Depending on the local Dracut and USE flag configuration, some +configuration adjustments may be required as a result of these changes. + + +Background (the problem) +==================== + +Previously Dracut implicitly included all out-of-tree kernel modules +it could find. This leads to several problems: +- It unnecessarily increases the size of the initramfs +- It creates a bit of a mess when using distribution kernels, consider + the following: + 1) Distribution kernel is upgraded + 2) Initramfs for the new kernel is generated, it does not include + any out-of-tree kernel modules. + 3) Portage triggers rebuild of the out-of-tree kernel modules + 4) If zfs is installed, its rebuild will trigger an initramfs + re-installation. Otherwise no rebuild is triggered. + Problem: What is and is not included in the initramfs is now + ambiguous. It depends on the emerge order of the kernel modules + when zfs is used. And will completely change if at some later stage + regeneration of the initramfs is triggered manually via e.g.: + emerge --config sys-kernel/gentoo-kernel + As a result, Dracut's "--reproducible" setting is not working. And + the functionality of the initramfs may change (seemingly) at random. + + +Background (the fix) +==================== + +Several things have been changed: +- Out-of-tree kernel modules installed by portage are explicitly omitted + from the initramfs generated by Dracut by default. +- Packages that install a kernel module for which it might make sense to + have it in the initramfs, have gained the "initramfs" USE flag. When + this flag is enabled, Dracut is instructed to include the installed + kernel modules. Packages for which it is essential that its kernel + modules are included in the initramfs have this new flag enabled + by default. +- When distribution kernels are used (USE=dist-kernel), and a module + that should be in the initramfs is installed (USE=initramfs) the + initramfs is always re-generated. +- The packages installing CPU microcode (sys-kernel/linux-firmware + and sys-firmware/intel-microcode) have been adjusted to mirror the + above changes for out-of-tree kernel modules. Both packages + have gained the "dist-kernel" USE flag, and the "initramfs" flag is + now enabled by default. When both flags are enabled, Dracut is + configured to include the installed microcode in the initramfs, and + then the initramfs is regenerated. When the "dist-kernel" flag is + disabled, the "initramfs" flag behaves as it previously did. + + +User Action Required (Dracut and/or Distribution Kernel users) +==================== + +Users of sys-kernel/dracut and/or Distribution Kernels should double +check two things: +1) Please ensure that you are *not* globally enabling or disabling + the "initramfs" USE flag. Enabling it globally might result in an + unnecessarily large initramfs. Disabling it globally might result + in missing functionality in the initramfs. Which could lead to boot + failure if, for example, the zfs module is missing while the root + partition is a zfs. +2) Any add_drivers, or omit_drivers lines in /etc/dracut.conf or + /etc/dracut.conf.d/* may override the Dracut configuration snippets + installed by the kernel module packages in + /usr/lib/dracut/dracut.conf.d. Please review your Dracut + configuration files to ensure that you are not unintentionally + overriding the settings set by Portage. + + +User Action Required (other users) +==================== + +Other users may wish to disable the "initramfs" USE flag on +sys-kernel/linux-firmware and/or sys-firmware/intel-microcode +if they already have other mechanisms in place for updating the CPU +microcode (such as kernel built-in CPU microcode). Users who do not +use sys-kernel/dracut or Distribution Kernels can safely disable +the "initramfs" USE flag globally. + + +Frequently Asked Questions +==================== + +A package installing a kernel module I would like in my initramfs has +not gained the "initramfs" USE flag. How do I proceed? + + Please report a new bug on bugs.gentoo.org, requesting that the + package maintainer consider adding support to the package for + including the modules in the initramfs. In the meantime you can + locally override the configuration provided by the package (see + below). Note though that when distribution kernels are used, + regeneration of the initramfs must be triggered manually via e.g.: + emerge --config sys-kernel/gentoo-kernel + +How do I override the provided Dracut configuration snippets to +include/exclude a custom list of modules? + + To override the provided configuration snippet, create a new file + /etc/dracut.conf.d/10-PACKAGENAME.conf, replacing PACKAGENAME with + the name of the package providing the module. Add to this file: + omit_drivers+=" my list of drivers to omit " + and/or + add_drivers+=" my list of drivers to include " diff --git a/metadata/news/Manifest b/metadata/news/Manifest index 8db933ac49ee..23dc4d1e7898 100644 --- a/metadata/news/Manifest +++ b/metadata/news/Manifest @@ -1,23 +1,23 @@ -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 -MANIFEST Manifest.files.gz 17308 BLAKE2B d6f0e1960300dcb206a4c928e0f5497ce5fdccacc5a0e5c2508a7af6e8f9498d7b9fb9ec3f5d3954053fc79e8414e01e57845b94cb5cd6f55794cf59ea3c0d33 SHA512 5f19269ff35bf881a2c86ab1b5ce45cd93f05493fcf48e1b653586b091edc5c0a54df7ffbf400b137990209ea574d0bf309d777111a8f29a227fc82a5ed91540 -TIMESTAMP 2024-04-30T22:10:20Z +MANIFEST Manifest.files.gz 18015 BLAKE2B 0f236b16aa7102e94bdd290c9f35570b14fb7fd85c65d186e87b6144aaab308d7d7d90c949a1a279026ed000388dfc6d58203e21b0ea6f443155b2f84bd0dac1 SHA512 f7c4e16fcc69c01f6670c47e53c3d66dee0c1805037a50a3c5b41e311cff17079a9031b211bdfb4ad68df22ad33fe9c562c28c14eec3932a15d0e9e3a86b3533 +TIMESTAMP 2024-05-21T21:36:41Z -----BEGIN PGP SIGNATURE----- -iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAmYxbExfFIAAAAAALgAo +iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAmZNE+lfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUx RDZBQkI2M0JGQ0ZCNEJBMDJGREYxQ0VDNTkwRUVBQzkxODkyNTAACgkQ7FkO6skY -klA1Hw//dPe+uGPmd55bLRUoDiQWJ3LfpAPEPEIZgBL9ain6hGX3h6oWR95VJbVA -dK4/4GhkG7xQAB7Wcfyo9luq+GK19nGkNdnzMYQ2U3ba/iuV3VQwYPZvnlOwkXWJ -R7cotiPNnunY5jgfwd4Npo5uvOFC6GubQdFY2bXf7C9FD21dyGrKBK57m0KeFs1A -FISl2U4xjOvDJEs28XeFRQ2R9p0WCGWCRW3lJfENtsKH4KcMYHwLkBGqgOGnefhB -fgGrJNQJwwY+HShL/pXB6xBW4nbc7a88YvxFByqfEHEdQsgTMO6Z7fvZv4/wD0F5 -WgJ7X93T+7U4it62hFPEHCaPsPSd9FoGrLOYGDQL/k2ndw7AEgDy6KWokW2luT5e -aju7e6EFVApr/zoer6RoS9HRR3DCm2IJxqlhlF9BduYm7c+Aq27KCUBS5hhxqbO6 -7zlR0XWaClaac/AOl2iaaZmCa4nLCjdx7nWxLxeESGZBOQZLnQwZYlCfAf1J7SkA -lHlBEvxq38JrWGzU0dOhISZW7voGKv8NReyz3N4iGA2TA9gVD+7nALUxMj/I34oa -cr4rK3M9w7bXEltthIFeRwPYHfJySRtvZ0ZzQgSQsGC38UROnN7XHv6hC7ZoUzn2 -z5NGOirLnbOqsMuxo9oEJOFGXQJzx1lEWv0zc1rJCEW7OUBT/3Y= -=uPlg +klCi4w//XAc+gMJB7+Lsi4W4yyODnQSanl+0gsQbvnA6aLsg68QCGdOTDbdlFMHB +pDsw/2Nm7tmB9JvZI8RQI5zkuWfM83juX1TQC0FVp6y2nVxnp8M5EPhH4VOHdWdY +OY33iOj3V/6nb9LjcxzkqYkvYwQj/TJ/zpxzCI8QFk1fJfL96/DpI/keY+DxFL/P +xRHwjQLwSW/6zzPvgmM3KtBn16qVp3gXQeDahd+RjEMOQzjso7KQsbOpWxflTyx0 +uiK66P3q0jcjXnP4zzudObKBkV/cYYcg/4n/3CKS0UncWtxIniH3Z+ZB06pHWf16 +fS4t5pO6KdJtGwmyEgpUk4/ojltq40e4DtMiFIa8CJlsGuMzrMW03RETKRm+BqcW +qRaHDSKFAd+6+YFB9lN6r36tBG31+3wrC4LjQ/0JcDZqpu4ixY6vlXos6L1cAiJu +Qflk01DPkG9thC1H8DqU0N3M/Ar7e8FqVJgqPmT6cV1zo/3vS3UbkZ9xeMhHOpGf +8rNbm2sr6jMQcFvFNm9Z6DIKWJJ/GSSSJgtx5UnfJb96TkB58m9bvSacaN8fHbNh +tRNehScZHAE/jYuZ2UP9GfvwNRG7ofnSbnS5FYXdfyBDxP/Dlz0nRoAv/sKyR7Wg +0qHFOcQ47dG46TBjek1tV5i7kkrmtQ5qEyvqSAVTscp+DNZ/d1A= +=A89k -----END PGP SIGNATURE----- diff --git a/metadata/news/Manifest.files.gz b/metadata/news/Manifest.files.gz Binary files differindex 6d4db6daaff8..6c5b959ec221 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 ac9bcaa4bcde..0c96a25a890c 100644 --- a/metadata/news/timestamp.chk +++ b/metadata/news/timestamp.chk @@ -1 +1 @@ -Tue, 30 Apr 2024 22:10:16 +0000 +Tue, 21 May 2024 21:36:07 +0000 diff --git a/metadata/news/timestamp.commit b/metadata/news/timestamp.commit index 403103bf6630..2f62e7032ecc 100644 --- a/metadata/news/timestamp.commit +++ b/metadata/news/timestamp.commit @@ -1 +1 @@ -3bd00d5baa333cfe77fe5fdbca3a943089d6518b 1711298955 2024-03-24T16:49:15+00:00 +3557467d15bb3e848c1a73e70dfaa786a2de29d9 1716131556 2024-05-19T15:12:36Z |