From 26262b314fa723a2e86f4a9b8b344a72eb9c0393 Mon Sep 17 00:00:00 2001 From: V3n3RiX Date: Mon, 25 Jul 2022 20:57:05 +0100 Subject: gentoo auto-resync : 25:07:2022 - 20:57:05 --- ...01-08-some-dhcpcd-hooks-are-now-examples.en.txt | 21 --------- .../2016-01-27-upgrading-to-apache-2_4.en.txt | 23 ---------- .../2016-04-07-kde-plasma5-stable.en.txt | 38 ---------------- .../2016-04-24-default-video-cards.en.txt | 27 ----------- .../2016-05-23-lastpass-changes.en.txt | 30 ------------- .../2016-06-23-l10n-use_expand.en.txt | 49 -------------------- .../2016-08-08-openafs-debug_rodata.en.txt | 30 ------------- ...16-09-26-migration-to-sys-libs_uclibc-ng.en.txt | 47 ------------------- .../2016-09-27-openrc_0_22_updates.en.txt | 22 --------- ...04-important_fstab_and_localmount_update.en.txt | 28 ------------ .../2016-12-06-ruby-20-removal.en.txt | 27 ----------- .../2017-01-15-kde-plasma-4-removal.en.txt | 50 --------------------- metadata/news/Manifest | 30 ++++++------- metadata/news/Manifest.files.gz | Bin 16077 -> 13864 bytes metadata/news/timestamp.chk | 2 +- metadata/news/timestamp.commit | 2 +- 16 files changed, 17 insertions(+), 409 deletions(-) delete mode 100644 metadata/news/2016-01-08-some-dhcpcd-hooks-are-now-examples/2016-01-08-some-dhcpcd-hooks-are-now-examples.en.txt delete mode 100644 metadata/news/2016-01-27-upgrading-to-apache-2_4/2016-01-27-upgrading-to-apache-2_4.en.txt delete mode 100644 metadata/news/2016-04-07-kde-plasma5-stable/2016-04-07-kde-plasma5-stable.en.txt delete mode 100644 metadata/news/2016-04-24-default-video-cards/2016-04-24-default-video-cards.en.txt delete mode 100644 metadata/news/2016-05-23-lastpass-changes/2016-05-23-lastpass-changes.en.txt delete mode 100644 metadata/news/2016-06-23-l10n-use_expand/2016-06-23-l10n-use_expand.en.txt delete mode 100644 metadata/news/2016-08-08-openafs-debug_rodata/2016-08-08-openafs-debug_rodata.en.txt delete mode 100644 metadata/news/2016-09-26-migration-to-sys-libs_uclibc-ng/2016-09-26-migration-to-sys-libs_uclibc-ng.en.txt delete mode 100644 metadata/news/2016-09-27-openrc_0_22_updates/2016-09-27-openrc_0_22_updates.en.txt delete mode 100644 metadata/news/2016-11-04-important_fstab_and_localmount_update/2016-11-04-important_fstab_and_localmount_update.en.txt delete mode 100644 metadata/news/2016-12-06-ruby-20-removal/2016-12-06-ruby-20-removal.en.txt delete mode 100644 metadata/news/2017-01-15-kde-plasma-4-removal/2017-01-15-kde-plasma-4-removal.en.txt (limited to 'metadata/news') diff --git a/metadata/news/2016-01-08-some-dhcpcd-hooks-are-now-examples/2016-01-08-some-dhcpcd-hooks-are-now-examples.en.txt b/metadata/news/2016-01-08-some-dhcpcd-hooks-are-now-examples/2016-01-08-some-dhcpcd-hooks-are-now-examples.en.txt deleted file mode 100644 index 848a842b446c..000000000000 --- a/metadata/news/2016-01-08-some-dhcpcd-hooks-are-now-examples/2016-01-08-some-dhcpcd-hooks-are-now-examples.en.txt +++ /dev/null @@ -1,21 +0,0 @@ -Title: Some dhcpcd hooks are now examples -Author: William Hubbs -Content-Type: text/plain -Posted: 2016-01-08 -Revision: 2 -News-Item-Format: 1.0 -Display-If-Installed: <=net-misc/dhcpcd-6.10.0 - -In dhcpcd-6.10.0, the following hooks are no longer installed in -/lib/dhcpcd/dhcpcd-hooks by default: - -10-wpa_supplicant -15-timezone -29-lookup-hostname - -These are now installed in /usr/share/dhcpcd/hooks, which is an example -directory. - -If you were using these hooks before you upgrade to 6.10.0, you will -need to copy them back to the /lib/dhcpcd/dhcpcd-hooks directory after the -upgrade. diff --git a/metadata/news/2016-01-27-upgrading-to-apache-2_4/2016-01-27-upgrading-to-apache-2_4.en.txt b/metadata/news/2016-01-27-upgrading-to-apache-2_4/2016-01-27-upgrading-to-apache-2_4.en.txt deleted file mode 100644 index bff0e7d400f9..000000000000 --- a/metadata/news/2016-01-27-upgrading-to-apache-2_4/2016-01-27-upgrading-to-apache-2_4.en.txt +++ /dev/null @@ -1,23 +0,0 @@ -Title: Upgrading Apache from 2.2 to 2.4 -Author: Dirkjan Ochtman -Content-Type: text/plain -Posted: 2016-01-27 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: www-servers/apache - -With the 2.4 branch released by upstream almost 4 years ago, stable -Gentoo systems will soon be upgraded from apache 2.2 to apache 2.4. -When upgrading, some configuration changes will have to be made. -Upstream has a handy guide: - -https://httpd.apache.org/docs/2.4/upgrading.html - -For more information on all the new features, start here: - -https://httpd.apache.org/docs/trunk/new_features_2_4.html - -After emerging Apache 2.4, you will also need to rebuild any -third-party modules: - -emerge -av1 /usr/lib/apache2/modules --exclude=www-servers/apache diff --git a/metadata/news/2016-04-07-kde-plasma5-stable/2016-04-07-kde-plasma5-stable.en.txt b/metadata/news/2016-04-07-kde-plasma5-stable/2016-04-07-kde-plasma5-stable.en.txt deleted file mode 100644 index c9302f0911ec..000000000000 --- a/metadata/news/2016-04-07-kde-plasma5-stable/2016-04-07-kde-plasma5-stable.en.txt +++ /dev/null @@ -1,38 +0,0 @@ -Title: KDE Plasma 5 Upgrade -Author: Michael Palimaka -Content-Type: text/plain -Posted: 2016-04-02 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: kde-base/plasma-workspace - -KDE Workspaces 4.11 has reached end of life and is no longer supported -by upstream. It is therefore recommended for all users to upgrade to -KDE Plasma 5. - -A detailed upgrade guide is available[1], but in most cases it is enough to -switch to the new desktop/plasma profile, update @world, and -emerge kde-plasma/plasma-meta: - -# eselect profile list -# eselect profile set -# emerge --ask --changed-use --newrepo --deep world -# emerge --ask --verbose kde-plasma/plasma-meta - -If you normally use KDM to launch Plasma, note that it is no longer supported. -Upstream recommends x11-misc/sddm instead which is pulled in by plasma-meta by -default. OpenRC users should edit /etc/conf.d/xdm and update DISPLAYMANAGER. -Systemd users should run: systemctl reenable sddm.service - -Due to an an evolution of KDE upstream's release process[2], the traditional -monolithic KDE 4 release is now split into three distinct components. This -means that KDE Applications are now separate from the Plasma desktop and -older KDE 4-based applications will continue to function as normal inside -Plasma 5. - -KDE Workspaces 4.11 will remain in the tree for a reasonable time, but -be warned that it is unmaintained and may cause conflicts with -newer versions of KDE Applications. - -[1] https://wiki.gentoo.org/wiki/KDE/Plasma_5_upgrade -[2] https://dot.kde.org/2013/09/04/kde-release-structure-evolves diff --git a/metadata/news/2016-04-24-default-video-cards/2016-04-24-default-video-cards.en.txt b/metadata/news/2016-04-24-default-video-cards/2016-04-24-default-video-cards.en.txt deleted file mode 100644 index 8a94240b08e9..000000000000 --- a/metadata/news/2016-04-24-default-video-cards/2016-04-24-default-video-cards.en.txt +++ /dev/null @@ -1,27 +0,0 @@ -Title: Changes in default VIDEO_CARDS -Author: Chí-Thanh Christopher Nguyễn -Content-Type: text/plain -Posted: 2016-04-24 -Revision: 2 -News-Item-Format: 1.0 -Display-If-Keyword: amd64 -Display-If-Keyword: x86 -Display-If-Installed: x11-drivers/xf86-video-dummy -Display-If-Installed: x11-drivers/xf86-video-glint -Display-If-Installed: x11-drivers/xf86-video-mach64 -Display-If-Installed: x11-drivers/xf86-video-mga -Display-If-Installed: x11-drivers/xf86-video-nv -Display-If-Installed: x11-drivers/xf86-video-r128 -Display-If-Installed: x11-drivers/xf86-video-savage -Display-If-Installed: x11-drivers/xf86-video-tdfx -Display-If-Installed: x11-drivers/xf86-video-trident -Display-If-Installed: x11-drivers/xf86-video-v4l -Display-If-Installed: x11-drivers/xf86-video-via -Display-If-Installed: x11-drivers/xf86-video-vmware - -In order to better reflect the graphics chipsets present on modern -systems, the default VIDEO_CARDS setting has been changed to -"amdgpu fbdev intel nouveau radeon radeonsi vesa" - -If your graphics chipset requires a different driver, and you have not set -VIDEO_CARDS in make.conf, it is advisable to do that now. diff --git a/metadata/news/2016-05-23-lastpass-changes/2016-05-23-lastpass-changes.en.txt b/metadata/news/2016-05-23-lastpass-changes/2016-05-23-lastpass-changes.en.txt deleted file mode 100644 index 4534932a7929..000000000000 --- a/metadata/news/2016-05-23-lastpass-changes/2016-05-23-lastpass-changes.en.txt +++ /dev/null @@ -1,30 +0,0 @@ -Title: LastPass package migration -Author: Göktürk Yüksek -Author: Robin H. Johnson -Content-Type: text/plain -Posted: 2016-05-23 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: app-admin/lastpass - -LastPass-3 and earlier versions installed browser extensions along -with the necessary binary components. LastPass-4 and later versions -install only the binary components and leave installing the browser -extensions to the user. Furthermore, LastPass-3 is not available -anymore, it will be removed soon and users are required to upgrade. A -transparent package move is not possible due to the mentioned changes -and a manual migration is required. - -The currently installed package must be removed before proceeding with -the migration: - -emerge --unmerge --ask app-admin/lastpass - -LastPass for Firefox users can safely upgrade to version 4 by visiting -the official LastPass website and following the download instructions. -The browser extension already contains the required binary components. -No packages need to be installed. - -Users of Chrome/Chromium and Opera browsers need to switch to -app-admin/lastpass-binary-component and follow the instructions -displayed on the screen after the installation to complete the process. diff --git a/metadata/news/2016-06-23-l10n-use_expand/2016-06-23-l10n-use_expand.en.txt b/metadata/news/2016-06-23-l10n-use_expand/2016-06-23-l10n-use_expand.en.txt deleted file mode 100644 index 2ff30d780bff..000000000000 --- a/metadata/news/2016-06-23-l10n-use_expand/2016-06-23-l10n-use_expand.en.txt +++ /dev/null @@ -1,49 +0,0 @@ -Title: L10N USE_EXPAND variable replacing LINGUAS -Author: Mart Raudsepp -Author: Ulrich Müller -Content-Type: text/plain -Posted: 2016-06-19 -Revision: 1 -News-Item-Format: 1.0 - -The L10N variable is replacing LINGUAS as a USE_EXPAND, to avoid a -conceptual clash with the standard gettext LINGUAS behaviour. - -L10N controls which extra localization support will be installed. -This is commonly used for downloads of additional language packs. - -If you have set LINGUAS in your make.conf, you most likely want to add -its entries also to L10N. Note that while the common two letter language -codes (like "de" or "fr") are identical, more complex entries have a -different syntax because L10N now uses IETF language tags. (For example, -"pt_BR" becomes "pt-BR" and "sr@latin" becomes "sr-Latn".) You can look -up the available codes in profiles/desc/l10n.desc in the gentoo tree. -A detailed description of language tags (aka BCP 47) can be found at: -https://www.w3.org/International/articles/language-tags/ - -After a transition time for packages to be converted, the LINGUAS -environment variable will maintain the standard gettext behaviour and -will work as expected with all package managers. It controls which -language translations are built and installed. An unset value means all -available, an empty value means none, and a value can be an unordered -list of gettext language codes, with or without country codes. Usually -two letter language codes suffice, but can be narrowed down by country -codes with a "ll_CC" formatting, where "ll" is the language code and -"CC" is the country code, e.g., "en_GB". Some rare languages also have -three letter language codes. Note that LINGUAS does not only affect -installed gettext catalog files (*.mo), but also lines of translations -in an always shipped file (e.g., *.desktop). - -If you want English with a set LINGUAS, it is suggested to list it with -the desired country code, in case the default is not the usual "en_US". -It is also common to list "en" then, in case a package is natively -written in a different language, but does provide an English translation -for whichever country. A list of LINGUAS language codes is available at: -http://www.gnu.org/software/gettext/manual/gettext.html#Language-Codes - -If you have per-package customizations of the LINGUAS USE_EXPAND, you -should also rename those. This typically means changing linguas_* to -l10n_*, and possibly updating the syntax as described above. - -https://wiki.gentoo.org/wiki/Localization/Guide has also been updated to -reflect this change. diff --git a/metadata/news/2016-08-08-openafs-debug_rodata/2016-08-08-openafs-debug_rodata.en.txt b/metadata/news/2016-08-08-openafs-debug_rodata/2016-08-08-openafs-debug_rodata.en.txt deleted file mode 100644 index 3997c7df8113..000000000000 --- a/metadata/news/2016-08-08-openafs-debug_rodata/2016-08-08-openafs-debug_rodata.en.txt +++ /dev/null @@ -1,30 +0,0 @@ -Title: OpenAFS no longer needs kernel option DEBUG_RODATA -Author: NP-Hardass -Author: Andrew Savchenko -Content-Type: text/plain -Posted: 2016-08-08 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: <=net-fs/openafs-kernel-1.6.18.2 -Display-If-Keyword: amd64 -Display-If-Keyword: ~amd64-linux -Display-If-Keyword: ~sparc -Display-If-Keyword: x86 -Display-If-Keyword: ~x86-linux - -As a result of bug #127084 [1], it was determined that OpenAFS's -kernel module required that the kernel's data structures be -read-write (CONFIG_DEBUG_RODATA=n). With recent OpenAFS versions -this limitation is no longer required. We tested the latest version -of OpenAFS with Linux kernels from 3.4 till 4.6, and determined that -OpenAFS kernel module works fine with CONFIG_DEBUG_RODATA=y. - -Starting with net-fs/openafs-kernel-1.6.18.2, this condition is no -longer forced in the ebuild. Considering the security implications -of having CONFIG_DEBUG_RODATA turned off, it is highly advised that -you adjust your kernel config accordingly. Please note that the -default setting for CONFIG_DEBUG_RODATA is "y" and unless you have -another reason for keeping it disabled, we highly recommend that -you re-enable CONFIG_DEBUG_RODATA. - -[1] https://bugs.gentoo.org/show_bug.cgi?id=127084 diff --git a/metadata/news/2016-09-26-migration-to-sys-libs_uclibc-ng/2016-09-26-migration-to-sys-libs_uclibc-ng.en.txt b/metadata/news/2016-09-26-migration-to-sys-libs_uclibc-ng/2016-09-26-migration-to-sys-libs_uclibc-ng.en.txt deleted file mode 100644 index 6a0e2f016ab3..000000000000 --- a/metadata/news/2016-09-26-migration-to-sys-libs_uclibc-ng/2016-09-26-migration-to-sys-libs_uclibc-ng.en.txt +++ /dev/null @@ -1,47 +0,0 @@ -Title: Migration to sys-libs/uclibc-ng -Author: Anthony G. Basile -Content-Type: text/plain -Posted: 2016-09-26 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: sys-libs/uclibc -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 - -Upstream development of uClibc has been stalled since July 2015 and -there hasn't been a proper release since May 2012 [1]. New patches -addressing important issues have been submitted but these have not been -reviewed nor have they been committed to the master branch. Also, -backporting even those patches which have been committed to master is -now impractical as too many intermediate layers of patches conflict. -For all intents and purposes, upstream uClibc is dead. - -Fortunately, a fork called uClibc-ng [2] was begun by Waldemar Brodkorb -in February 2015 and is actively being maintained. Accordingly, -Gentoo's Hardened uClibc project will be migrating to uClibc-ng as its -libc provider. Currently stage3 tarballs based on sys-libs/uclibc-ng -are available for all supported arches at [3] and these will become the -default after October 5, 2016. Older stage3s based on sys-libs/uclibc -will be removed. - -Unfortunately, migrating a production system from uclibc to uclibc-ng -is not straightforward owing to the central role played by libc. A -migration guide is provided at [4]. This has been tested on live -systems with success, but the user is cautioned to plan a backup and -recovery plan should something go wrong. - -Refs. -[1] https://git.uclibc.org/uClibc/log/ -[2] http://uclibc-ng.org/ -[3] http://distfiles.gentoo.org/experimental/ -[4] https://wiki.gentoo.org/wiki/Project:Hardened_uClibc#Migration_to_uClibc-ng diff --git a/metadata/news/2016-09-27-openrc_0_22_updates/2016-09-27-openrc_0_22_updates.en.txt b/metadata/news/2016-09-27-openrc_0_22_updates/2016-09-27-openrc_0_22_updates.en.txt deleted file mode 100644 index 48dfe46ce467..000000000000 --- a/metadata/news/2016-09-27-openrc_0_22_updates/2016-09-27-openrc_0_22_updates.en.txt +++ /dev/null @@ -1,22 +0,0 @@ -Title: OpenRC 0.22 updates -Author: William Hubbs -Content-Type: text/plain -Posted: 2016-09-27 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: <=sys-apps/openrc-0.22 - -OpenRC 0.22 introduces the following changes: - -- In previous versions of OpenRC, configuration information was processed - so that service-specific configuration stored in /etc/conf.d/* was - overridden by global configuration stored in /etc/rc.conf. OpenRC 0.22 - reverses that. Global configuration stored in /etc/rc.conf is read first - then overridden by configuration stored in /etc/conf.d/*. - -- The swapfiles service, which was basically a copy of the swap service, - has been removed. If you are only using local swap partitions, as - described in the handbook for example, this change will not affect you. - If you are using swap files or swap partitions on network-backed devices - such as iSCSI, please adjust the dependencies of the swap - service as shown in /etc/conf.d/swap to reflect your situation. diff --git a/metadata/news/2016-11-04-important_fstab_and_localmount_update/2016-11-04-important_fstab_and_localmount_update.en.txt b/metadata/news/2016-11-04-important_fstab_and_localmount_update/2016-11-04-important_fstab_and_localmount_update.en.txt deleted file mode 100644 index 3cd9a8f25541..000000000000 --- a/metadata/news/2016-11-04-important_fstab_and_localmount_update/2016-11-04-important_fstab_and_localmount_update.en.txt +++ /dev/null @@ -1,28 +0,0 @@ -Title: Important fstab and localmount update -Author: William Hubbs -Author: Ian Stakenvicius -Display-If-Installed: <=sys-apps/openrc-0.23 -Content-Type: text/plain -Posted: 2016-11-04 -Revision: 2 -News-Item-Format: 1.0 - -Recent updates to service scripts in OpenRC and (e)udev have removed the -requirement for udev to "settle" before its startup completes. The -result of this is that services which used to wait for udev to finish -processing all kernel events will now start earlier. One such service -is localmount. - -If "/dev/disk/by-*" device paths are used for mount points in -fstab, it is possible that those symbolic links will not exist when -localmount starts and attempts to mount them. - -The recommended solution is to convert fstab from using -"/dev/disk/by-*" to the LABEL=, UUID=, PARTLABEL= or PARTUUID= syntax. -This syntax is supported directly by both util-linux and busybox's mount -commands and has no dependency on any device manager. More information -on this syntax can be found in the fstab(5) and mount(8) man pages. - -To force the old behaviour, instead of converting fstab, you can add -rc_want="dev-settle" to /etc/conf.d/localmount or add udev-settle to the -sysinit runlevel. diff --git a/metadata/news/2016-12-06-ruby-20-removal/2016-12-06-ruby-20-removal.en.txt b/metadata/news/2016-12-06-ruby-20-removal/2016-12-06-ruby-20-removal.en.txt deleted file mode 100644 index c6bc2cf7fb44..000000000000 --- a/metadata/news/2016-12-06-ruby-20-removal/2016-12-06-ruby-20-removal.en.txt +++ /dev/null @@ -1,27 +0,0 @@ -Title: Ruby 2.0 removal; Ruby 2.1 default -Author: Hans de Graaff -Content-Type: text/plain -Posted: 2016-12-04 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: -Content-Type: text/plain -Posted: 2017-01-08 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: kde-plasma/kdebase-startkde -Display-If-Installed: kde-plasma/kdm -Display-If-Profile: default/linux/alpha/13.0/desktop/kde -Display-If-Profile: default/linux/alpha/13.0/desktop/kde/systemd -Display-If-Profile: default/linux/amd64/13.0/desktop/kde -Display-If-Profile: default/linux/amd64/13.0/desktop/kde/systemd -Display-If-Profile: default/linux/arm/13.0/desktop/kde -Display-If-Profile: default/linux/arm/13.0/desktop/kde/systemd -Display-If-Profile: default/linux/arm/13.0/armv4/desktop/kde -Display-If-Profile: default/linux/arm/13.0/armv4t/desktop/kde -Display-If-Profile: default/linux/arm/13.0/armv5te/desktop/kde -Display-If-Profile: default/linux/arm/13.0/armv6j/desktop/kde -Display-If-Profile: default/linux/arm/13.0/armv7a/desktop/kde -Display-If-Profile: default/linux/ia64/13.0/desktop/kde -Display-If-Profile: default/linux/ia64/13.0/desktop/kde/systemd -Display-If-Profile: default/linux/m68k/13.0/desktop/kde -Display-If-Profile: default/linux/powerpc/ppc32/13.0/desktop/kde -Display-If-Profile: default/linux/powerpc/ppc32/13.0/desktop/kde/systemd -Display-If-Profile: default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/kde -Display-If-Profile: default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/kde/systemd -Display-If-Profile: default/linux/powerpc/ppc64/13.0/64bit-userland/desktop/kde -Display-If-Profile: default/linux/powerpc/ppc64/13.0/64bit-userland/desktop/kde/systemd -Display-If-Profile: default/linux/sh/13.0/desktop/kde -Display-If-Profile: default/linux/sparc/13.0/desktop/kde -Display-If-Profile: default/linux/sparc/13.0/desktop/kde/systemd -Display-If-Profile: default/linux/x86/13.0/desktop/kde -Display-If-Profile: default/linux/x86/13.0/desktop/kde/systemd - -KDE Plasma 4 has reached end of life in Portage. Upstream dropped support -in 2015-08-19, no security bugs have been fixed since then. It is therefore -required for all users to upgrade to KDE Plasma 5. - -KDM is being removed as well. Upstream recommends x11-misc/sddm instead which -is pulled in by plasma-meta by default. -OpenRC users edit /etc/conf.d/xdm and update DISPLAYMANAGER. -Systemd users run: systemctl reenable sddm.service - -Part of the cleanup will also be the KDE desktop profile, which is superseded -by the Plasma desktop profile. Please follow the detailed upgrade guide.[1] - -KDE Plasma 4.11 packages will be moved to kde-sunset overlay.[2] - -[1] https://wiki.gentoo.org/wiki/KDE/Plasma_5_upgrade -[2] https://wiki.gentoo.org/wiki/Overlay:Kde-sunset diff --git a/metadata/news/Manifest b/metadata/news/Manifest index e60603080a23..89368aeadb7b 100644 --- a/metadata/news/Manifest +++ b/metadata/news/Manifest @@ -1,23 +1,23 @@ -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 -MANIFEST Manifest.files.gz 16077 BLAKE2B 13a0087d25427f18ef538f24038e79b53f0f6188f78ddada0883df9df0c7e42f4ca5aec7cd8b2f30648e8efe5d186939a0a4627d065810fb27d03e39dc2df9e9 SHA512 789fd7f25ffac2e5f222a612e23d79ac9cbef3a60fd645506bc234c25cd05a40a85791cc39f5a991b0a6630148cfee81586003336cbe08828e2426fcf493b208 -TIMESTAMP 2022-07-25T12:39:53Z +MANIFEST Manifest.files.gz 13864 BLAKE2B 373887a06bb63946485d0b9e08e52b3b3c3fbeda530b58fbe19569ccedfd0a8f7c63f073261fcef68edcbf9331108cf543382117b2f60c464926fff49fff9e18 SHA512 b3adafe44390700af75c3b98d6b21ba11902c1f2033fb07a8064382a68a6b6c023b73b318e0a8159e5911175172732771aae9261f870aee90bb5b6e69de3f24d +TIMESTAMP 2022-07-25T18:40:01Z -----BEGIN PGP SIGNATURE----- -iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAmLejxlfFIAAAAAALgAo +iQKTBAEBCgB9FiEE4dartjv8+0ugL98c7FkO6skYklAFAmLe44FfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUx RDZBQkI2M0JGQ0ZCNEJBMDJGREYxQ0VDNTkwRUVBQzkxODkyNTAACgkQ7FkO6skY -klDuaQ/9HfHcKbp3GIP4wqu6by4zzV1FfwabvwR+bwqAJeYFBXjawq/FhraAQwYV -YyBLrKw6qa6LxqKMu0XKlXJr06QmEtgAQPX4Qk3RMKebh3HhvGHQ6EqvcYc82IkZ -WFNrYI93GjrpyKSTeznYKDwZATOC3wZ4PeN3ABjy5WVrnpJPBDsVhnSg2s8q2c3b -kZpXj7pTTKh9wLG8w9MpSq9cegpBlkNRvwaKs1xWOwo8OuAjV+9ygw4cit6i9WWN -1Dr6VH6edJ/MkJyj8qYmMTWnO9xXv1QPvKTxh/VCP15J+yfAQe48v/MNe7G9ig4i -37ya1+y91j7FsE7U24RWlIWNbYSgqIS4YNfHH2TnMjqZEYeykL6JK1NybxTCaZYG -sUw6suUATjhMaIxFHJPj305IKt0eDXr4xP4Iv+dWPaOaz9KTs8P+kgSggV54jFUR -cACSl1KkA9yRWAdfZiyFKj8AiG6DxYqyRI5OIZINyxeozpj/3dXPxaCtf8DSqKyQ -iPAgUvOOeZjId/YIOVzZ/sVlEqsIJDPAb+gfuelpSxOcfS7/8y7lJtE4zFGTt8jL -V9VcGpOiI3vUNT9HsM8KMd6Kv1v6qlZA/XiAdzTCeBhQ4Iohw5lE/aU/fPQOu/es -2WG94IrGwzOruEWzXdl3t0/HAqL+Ys0PxS0bYRZQsLsYctpWnag= -=6+Lh +klBNOBAAkR4/CkGh2O36jCfbJ8VAj4GljZH39Zj3A/22tBC/5ukdM6J1ciJcnDvc +YYhUdN4g2LqQZSPuCpfpibuUp4wcxKHcpHWXcmhWiIZRlW+aVFCDC6N7xPkbyvpQ +QkRwNde+LTMkI3ikWm34UwFdSzB5m4ARC+AXxfTWL+80zYv0yup7V8XTEVdzXL/0 +es/mxz4euAhsDaLxnl5NxRIK8qyCLPfyPbz+NbSrmPiV6AGFD69pyXb+fJXuXaSl +s+IDAp8XZ8VVCvnL9rTSypqPp8gxpy7QGfrhipI6k0VQ6Zfs0hL0IzOab+4avH7Q +y/K7bFfY+l/FROVJtywCI9ImE1+4D6gkyWnbt5kn5qbVnyK55MA2yNuvKZzChoCo +BBSYfyLuUV8y+Bs6li30dnCWkWvLITcYHlpFviNTqjtlg+w4hxQVc8yjEAFN1OAv +FgbkRUxBFt7Mmw02S8/CPDA4gsKbmVn8XsuiS4sUak1Xvl/DMDN1IyxQW/VeAwoF +1rz8+c7imSUtoYGOXXBvKEZyM/ez2nY3+I4HoJzwvfNRind6emBtDW9khvG16v99 +Vk2ZuRYG9owtPwDZ1tBOvXUeJ2I8+qMciZsciOzX1tbPjrd5fCShvehB736pr/IF +SOzTzvYk7KSNizgkGsACFXdVsiGxvmT4so0M5ucS4JGoz4ky/o0= +=Qt0W -----END PGP SIGNATURE----- diff --git a/metadata/news/Manifest.files.gz b/metadata/news/Manifest.files.gz index 1eaea810a2d8..cd92c07505d9 100644 Binary files a/metadata/news/Manifest.files.gz and b/metadata/news/Manifest.files.gz differ diff --git a/metadata/news/timestamp.chk b/metadata/news/timestamp.chk index b62bd138a995..312267dc2aca 100644 --- a/metadata/news/timestamp.chk +++ b/metadata/news/timestamp.chk @@ -1 +1 @@ -Mon, 25 Jul 2022 12:39:49 +0000 +Mon, 25 Jul 2022 18:39:58 +0000 diff --git a/metadata/news/timestamp.commit b/metadata/news/timestamp.commit index f5e45b2a0465..c869f5e6214f 100644 --- a/metadata/news/timestamp.commit +++ b/metadata/news/timestamp.commit @@ -1 +1 @@ -7dc22525e5170f646a8019f555d950276c4f208a 1658670955 2022-07-24T13:55:55+00:00 +8c8dc9f31a085eedd1fc8b96bba8d883f3239310 1658765725 2022-07-25T16:15:25+00:00 -- cgit v1.2.3