[gentoo-commits] data/gentoo-news:master commit in: 2024-06-08-texlive-2023-bump/
commit: 0af1caad65efe62715f6d461895ee5568c9faeff Author: Florian Schmaus gentoo org> AuthorDate: Sat Jun 8 08:55:28 2024 + Commit: Florian Schmaus gentoo org> CommitDate: Sat Jun 8 08:55:28 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=0af1caad 2024-06-08-texlive-2023-bump: adjust underline to length of headline Signed-off-by: Florian Schmaus gentoo.org> 2024-06-08-texlive-2023-bump/2024-06-08-texlive-2023-bump.en.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2024-06-08-texlive-2023-bump/2024-06-08-texlive-2023-bump.en.txt b/2024-06-08-texlive-2023-bump/2024-06-08-texlive-2023-bump.en.txt index 2c821e0..7ab0231 100644 --- a/2024-06-08-texlive-2023-bump/2024-06-08-texlive-2023-bump.en.txt +++ b/2024-06-08-texlive-2023-bump/2024-06-08-texlive-2023-bump.en.txt @@ -7,7 +7,7 @@ Display-If-Installed:
[gentoo-commits] data/gentoo-news:master commit in: 2024-06-08-texlive-2023-bump/
commit: a4d43b71affe2a80e9eff0663ebd9c2889bb0c57 Author: Florian Schmaus gentoo org> AuthorDate: Thu May 30 09:54:24 2024 + Commit: Florian Schmaus gentoo org> CommitDate: Sat Jun 8 07:47:11 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=a4d43b71 2024-06-08-texlive-2023-bump: add news item Signed-off-by: Florian Schmaus gentoo.org> .../2024-06-08-texlive-2023-bump.en.txt| 34 ++ 1 file changed, 34 insertions(+) diff --git a/2024-06-08-texlive-2023-bump/2024-06-08-texlive-2023-bump.en.txt b/2024-06-08-texlive-2023-bump/2024-06-08-texlive-2023-bump.en.txt new file mode 100644 index 000..2c821e0 --- /dev/null +++ b/2024-06-08-texlive-2023-bump/2024-06-08-texlive-2023-bump.en.txt @@ -0,0 +1,34 @@ +Title: Upgrading to TeX Live 2023 +Author: Florian Schmaus +Posted: 2024-06-05 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: =app-text/texlive-2023' +[only proceed if texlive update is available] +2. emerge --unmerge --deselect=n 'dev-texlive/*' +3. emerge '>=app-text/texlive-2023' + +The steps above are equivalent to the following bash snippet: + +if emerge -p '>=app-text/texlive-2023'; then +emerge --unmerge --deselect=n 'dev-texlive/*' +emerge '>=app-text/texlive-2023' +fi
[gentoo-commits] data/gentoo-news:master commit in: 2024-05-17-dracut-ext-kmods/
commit: 3557467d15bb3e848c1a73e70dfaa786a2de29d9 Author: Andrew Ammerlaan gentoo org> AuthorDate: Sun May 19 15:12:36 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Sun May 19 15:12:36 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=3557467d 2024-05-17-dracut-ext-kmods: clarify the non-dracut/dist-kernel case Signed-off-by: Andrew Ammerlaan gentoo.org> .../2024-05-17-dracut-ext-kmods.en.txt | 22 +++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/2024-05-17-dracut-ext-kmods/2024-05-17-dracut-ext-kmods.en.txt b/2024-05-17-dracut-ext-kmods/2024-05-17-dracut-ext-kmods.en.txt index ff2bdf6..af58a63 100644 --- a/2024-05-17-dracut-ext-kmods/2024-05-17-dracut-ext-kmods.en.txt +++ b/2024-05-17-dracut-ext-kmods/2024-05-17-dracut-ext-kmods.en.txt @@ -1,7 +1,7 @@ Title: Changes to dracut kernel module/microcode handling Author: Andrew Ammerlaan Posted: 2024-05-17 -Revision: 1 +Revision: 2 News-Item-Format: 2.0 Display-If-Installed: sys-kernel/dracut Display-If-Installed: virtual/dist-kernel @@ -18,6 +18,7 @@ microcode, and how these are handled in initial RAM file systems Depending on the local Dracut and USE flag configuration, some configuration adjustments may be required as a result of these changes. + Background (the problem) @@ -40,6 +41,7 @@ it could find. This leads to several problems: As a result, Dracut's "--reproducible" setting is not working. And the functionality of the initramfs may change (seemingly) at random. + Background (the fix) @@ -64,10 +66,12 @@ Several things have been changed: then the initramfs is regenerated. When the "dist-kernel" flag is disabled, the "initramfs" flag behaves as it previously did. -User Action Required + +User Action Required (Dracut and/or Distribution Kernel users) -Users should double check two things: +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 @@ -81,6 +85,18 @@ Users should double check two things: 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
[gentoo-commits] data/gentoo-news:master commit in: 2024-05-17-dracut-ext-kmods/
commit: c64a05c51a237c6011b0d57d3739cb27e1927f3d Author: Andrew Ammerlaan gentoo org> AuthorDate: Fri May 17 08:19:31 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Fri May 17 08:19:31 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=c64a05c5 2024-05-17-dracut-ext-kmods: add news item Signed-off-by: Andrew Ammerlaan gentoo.org> .../2024-05-17-dracut-ext-kmods.en.txt | 106 + 1 file changed, 106 insertions(+) diff --git a/2024-05-17-dracut-ext-kmods/2024-05-17-dracut-ext-kmods.en.txt b/2024-05-17-dracut-ext-kmods/2024-05-17-dracut-ext-kmods.en.txt new file mode 100644 index 000..ff2bdf6 --- /dev/null +++ b/2024-05-17-dracut-ext-kmods/2024-05-17-dracut-ext-kmods.en.txt @@ -0,0 +1,106 @@ +Title: Changes to dracut kernel module/microcode handling +Author: Andrew Ammerlaan +Posted: 2024-05-17 +Revision: 1 +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 + + +Users 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. + +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
[gentoo-commits] data/gentoo-news:master commit in: 2024-05-09-python3-12/
commit: 54a41c87307533fe370c99eb5295f5a638fe8d42 Author: Michał Górny gentoo org> AuthorDate: Mon May 6 17:13:03 2024 + Commit: Michał Górny gentoo org> CommitDate: Thu May 9 03:50:11 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=54a41c87 2024-05-09-python3-12: Add Signed-off-by: Michał Górny gentoo.org> 2024-05-09-python3-12/2024-05-09-python3-12.en.txt | 120 +++ 2024-05-09-python3-12/2024-05-09-python3-12.pl.txt | 133 + 2 files changed, 253 insertions(+) diff --git a/2024-05-09-python3-12/2024-05-09-python3-12.en.txt b/2024-05-09-python3-12/2024-05-09-python3-12.en.txt new file mode 100644 index 000..cedb196 --- /dev/null +++ b/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 +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
[gentoo-commits] data/gentoo-news:master commit in: 2024-05-07-perl-features-use-expand/
commit: 9b2a821e455c662000a56f630fd0c38b397e7cb8 Author: Andreas K. Hüttel gentoo org> AuthorDate: Tue May 7 09:32:25 2024 + Commit: Andreas K. Hüttel gentoo org> CommitDate: Tue May 7 09:32:25 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=9b2a821e 2024-05-07-perl rev. 2: fix posted date Signed-off-by: Andreas K. Hüttel gentoo.org> .../2024-05-07-perl-features-use-expand.en.txt| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2024-05-07-perl-features-use-expand/2024-05-07-perl-features-use-expand.en.txt b/2024-05-07-perl-features-use-expand/2024-05-07-perl-features-use-expand.en.txt index bde92d9..417238f 100644 --- a/2024-05-07-perl-features-use-expand/2024-05-07-perl-features-use-expand.en.txt +++ b/2024-05-07-perl-features-use-expand/2024-05-07-perl-features-use-expand.en.txt @@ -1,7 +1,7 @@ Title: dev-lang/perl useflags become a PERL_FEATURES use-expand Author: Andreas K. Huettel -Posted: 2024-05-10 -Revision: 1 +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",
[gentoo-commits] data/gentoo-news:master commit in: 2024-05-07-perl-features-use-expand/
commit: 4b348e89b0b705b97c0582eeca0bab2435c4d778 Author: Andreas K. Hüttel gentoo org> AuthorDate: Tue May 7 07:50:54 2024 + Commit: Andreas K. Hüttel gentoo org> CommitDate: Tue May 7 07:51:22 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=4b348e89 Add 2024-05-07-perl-features-use-expand Signed-off-by: Andreas K. Hüttel gentoo.org> .../2024-05-07-perl-features-use-expand.en.txt | 31 ++ 1 file changed, 31 insertions(+) diff --git a/2024-05-07-perl-features-use-expand/2024-05-07-perl-features-use-expand.en.txt b/2024-05-07-perl-features-use-expand/2024-05-07-perl-features-use-expand.en.txt new file mode 100644 index 000..bde92d9 --- /dev/null +++ b/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 +Posted: 2024-05-10 +Revision: 1 +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...
[gentoo-commits] data/gentoo-news:master commit in: 2017-02-10-upgrade-to-sys-libs_uclibc-ng-1_0_22/
commit: 6e72ffeb1947d59cd4ee4f5a74829735c4564f6b Author: Sam James gentoo org> AuthorDate: Mon May 6 13:28:14 2024 + Commit: Sam James gentoo org> CommitDate: Mon May 6 13:28:25 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=6e72ffeb 2017-02-10-upgrade-to-sys-libs_uclibc-ng-1_0_22: delete news item We dropped uclibc-ng support in the '2021-08-18-uclibc-ng-retirement' news item (45d03823eeb53dc970545f17363af2b3ac7ad614). Signed-off-by: Sam James gentoo.org> ...-10-upgrade-to-sys-libs_uclibc-ng-1_0_22.en.txt | 77 -- 1 file changed, 77 deletions(-) diff --git a/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/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 b413ce4..000 --- a/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 -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 -
[gentoo-commits] data/gentoo-news:master commit in: 2024-05-06-wireplumber-0_5-bump/, 2024-05-03-wireplumber-0_5-bump/
commit: 8eb7599940bf2bfa05311e856726fc78293ab6b5 Author: Sam James gentoo org> AuthorDate: Mon May 6 07:31:04 2024 + Commit: Sam James gentoo org> CommitDate: Mon May 6 07:31:04 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=8eb75999 2024-05-03-wireplumber-0_5-bump: rename to 2024-05-06-wireplumber-0_5-bump Signed-off-by: Sam James gentoo.org> .../2024-05-06-wireplumber-0_5-bump.en.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt b/2024-05-06-wireplumber-0_5-bump/2024-05-06-wireplumber-0_5-bump.en.txt similarity index 98% rename from 2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt rename to 2024-05-06-wireplumber-0_5-bump/2024-05-06-wireplumber-0_5-bump.en.txt index 22f2314..d252474 100644 --- a/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt +++ b/2024-05-06-wireplumber-0_5-bump/2024-05-06-wireplumber-0_5-bump.en.txt @@ -1,6 +1,6 @@ Title: media-video/wireplumber-0.5.2 may break on upgrade Author: James Calligeros -Posted: 2024-05-03 +Posted: 2024-05-06 Revision: 1 News-Item-Format: 2.0 Display-If-Installed: media-video/wireplumber
[gentoo-commits] data/gentoo-news:master commit in: 2024-05-03-wireplumber-0_5-bump/
commit: ff5cceaf5f2c64ad48396dd68be82e6100d3850a Author: James Calligeros gmail com> AuthorDate: Fri May 3 12:19:27 2024 + Commit: Sam James gentoo org> CommitDate: Mon May 6 07:25:41 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=ff5cceaf 2024-05-03-wireplumber-0_5-bump: add news item Bug: https://bugs.gentoo.org/921393 Signed-off-by: James Calligeros gmail.com> Signed-off-by: Sam James gentoo.org> .../2024-05-03-wireplumber-0_5-bump.en.txt | 25 ++ 1 file changed, 25 insertions(+) diff --git a/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt b/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt new file mode 100644 index 000..22f2314 --- /dev/null +++ b/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt @@ -0,0 +1,25 @@ +Title: media-video/wireplumber-0.5.2 may break on upgrade +Author: James Calligeros +Posted: 2024-05-03 +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
[gentoo-commits] data/gentoo-news:master commit in: 2024-03-22-new-23-profiles/
commit: 3bd00d5baa333cfe77fe5fdbca3a943089d6518b
Author: Andreas K. Hüttel gentoo org>
AuthorDate: Sun Mar 24 16:49:15 2024 +
Commit: Andreas K. Hüttel gentoo org>
CommitDate: Sun Mar 24 16:49:15 2024 +
URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=3bd00d5b
2024-03-22-new-23-profiles: Prefer source-based install
Signed-off-by: Andreas K. Hüttel gentoo.org>
.../2024-03-22-new-23-profiles.en.txt | 28 +++---
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt
b/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt
index d8f6fd3..e90babe 100644
--- a/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt
+++ b/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt
@@ -1,7 +1,7 @@
Title: Profile upgrade to version 23.0 available
Author: Andreas K. Huettel
Posted: 2024-03-22
-Revision: 1
+Revision: 2
News-Item-Format: 2.0
Display-If-Profile: default/linux/alpha/17.0
Display-If-Profile: default/linux/alpha/17.0/*
@@ -50,16 +50,16 @@ architecture, see [2].
Upgrade instructions
-Note 1: The use of binary packages is completely optional, and also not
-as much tested as the source-based upgrade path yet. If you prefer to
-only use the traditional source-based installation, omit the "--getbinpkg"
-parameter in all emerge invocations.
-
-Note 2: If you have manually changed your CHOST to a value different from
-what the stages and profiles set, you may have to do that in the future too.
+Note 1: If you have manually changed your CHOST to a value different from
+what the stages and profiles set, you may have to do that in the future too.
In that case you should know what you are doing, hopefully; please read the
instructions with a critical eye then.
+Note 2: In case you are already familiar with binary packages, you should be
+able to add "--getbinpkg" to the emerge calls to speed things up.
+The use of binary packages is completely optional though, and also not
+as much tested as the source-based upgrade path yet.
+
1. Ensure your system backups are up to date. Please also update
your system fully and depclean before proceeding.
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
@@ -105,16 +105,16 @@ instructions with a critical eye then.
9. Rebuild or reinstall from binary (if available) the following packages in
this order, with the same version as already active:
- emerge --ask --oneshot --getbinpkg sys-devel/binutils
+ emerge --ask --oneshot sys-devel/binutils
(you may have to run binutils-config and re-select your binutils now)
- emerge --ask --oneshot --getbinpkg sys-devel/gcc
+ emerge --ask --oneshot sys-devel/gcc
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it
do
that; instead, abort and try again with --nodeps added to the command
line.)
(you may have to run gcc-config and re-select your gcc now)
and the C library, i.e. for glibc-based systems
- emerge --ask --oneshot --getbinpkg sys-libs/glibc
+ emerge --ask --oneshot sys-libs/glibc
or for musl-based systems
- emerge --ask --oneshot --getbinpkg sys-libs/musl
+ emerge --ask --oneshot sys-libs/musl
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
@@ -130,14 +130,14 @@ If the CHOST has NOT changed, skip to step 13
(env-update). Otherwise,
13. Run env-update && source /etc/profile
14. Re-emerge libtool:
- emerge --ask --oneshot --getbinpkg libtool
+ emerge --ask --oneshot libtool
15. Just for safety, delete the contents of your binary package cache at
${PKGDIR} again:
rm -r /var/cache/binpkgs/*
16. Rebuild world:
- emerge --ask --emptytree --getbinpkg @world
+ emerge --ask --emptytree @world
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
[gentoo-commits] data/gentoo-news:master commit in: 2024-03-22-new-23-profiles/
commit: d3591106b1456128fb9f24a4d6261c101b6dbfec Author: Aliaksei Urbanski gmail com> AuthorDate: Fri Mar 22 23:17:49 2024 + Commit: Sam James gentoo org> CommitDate: Sun Mar 24 10:26:36 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=d3591106 2024-03-22-new-23-profiles: Fix a reference from step 10 to step 4 Signed-off-by: Aliaksei Urbanski gmail.com> Closes: https://github.com/gentoo/gentoo-news/pull/3 Signed-off-by: Sam James gentoo.org> 2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt b/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt index 0e2eeba..d8f6fd3 100644 --- a/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt +++ b/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt @@ -116,7 +116,7 @@ instructions with a critical eye then. or for musl-based systems emerge --ask --oneshot --getbinpkg sys-libs/musl -10. Re-run "emerge --info" and check if CHOST has changed compared to step 3. +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
[gentoo-commits] data/gentoo-news:master commit in: 2024-03-22-new-23-profiles/
commit: 02ea414ad62acc9001cdca824a3d6ae48683 Author: Andreas K. Hüttel gentoo org> AuthorDate: Fri Mar 22 19:24:26 2024 + Commit: Andreas K. Hüttel gentoo org> CommitDate: Fri Mar 22 19:24:26 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=02ea414a 2024-03-22-new-23-profiles: add news item Signed-off-by: Andreas K. Hüttel gentoo.org> .../2024-03-22-new-23-profiles.en.txt | 148 + 1 file changed, 148 insertions(+) diff --git a/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt b/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt new file mode 100644 index 000..0e2eeba --- /dev/null +++ b/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt @@ -0,0 +1,148 @@ +Title: Profile upgrade to version 23.0 available +Author: Andreas K. Huettel +Posted: 2024-03-22 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Profile: default/linux/alpha/17.0 +Display-If-Profile: default/linux/alpha/17.0/* +Display-If-Profile: default/linux/amd64/17.0 +Display-If-Profile: default/linux/amd64/17.0/* +Display-If-Profile: default/linux/amd64/17.1 +Display-If-Profile: default/linux/amd64/17.1/* +Display-If-Profile: default/linux/arm/17.0 +Display-If-Profile: default/linux/arm/17.0/* +Display-If-Profile: default/linux/arm64/17.0 +Display-If-Profile: default/linux/arm64/17.0/* +Display-If-Profile: default/linux/hppa/17.0 +Display-If-Profile: default/linux/hppa/17.0/* +Display-If-Profile: default/linux/ia64/17.0 +Display-If-Profile: default/linux/ia64/17.0/* +Display-If-Profile: default/linux/loong/22.0 +Display-If-Profile: default/linux/loong/22.0/* +Display-If-Profile: default/linux/m68k/17.0 +Display-If-Profile: default/linux/m68k/17.0/* +Display-If-Profile: default/linux/mips/17.0 +Display-If-Profile: default/linux/mips/17.0/* +Display-If-Profile: default/linux/powerpc/ppc64/17.0/* +Display-If-Profile: default/linux/ppc/17.0 +Display-If-Profile: default/linux/ppc/17.0/* +Display-If-Profile: default/linux/ppc64/17.0 +Display-If-Profile: default/linux/ppc64/17.0/* +Display-If-Profile: default/linux/ppc64le/17.0 +Display-If-Profile: default/linux/ppc64le/17.0/* +Display-If-Profile: default/linux/riscv/20.0/* +Display-If-Profile: default/linux/s390/17.0 +Display-If-Profile: default/linux/s390/17.0/* +Display-If-Profile: default/linux/sparc/17.0 +Display-If-Profile: default/linux/sparc/17.0/* +Display-If-Profile: default/linux/x86/17.0 +Display-If-Profile: default/linux/x86/17.0/* + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +We strongly advise to precisely follow the upgrade instructions found +below. The 17.0, 17.1, 20.0, and 22.0 profiles will be marked deprecated +in 2 months and removed a year later. The exact dates may depend on the +architecture, see [2]. + +Upgrade instructions + +Note 1: The use of binary packages is completely optional, and also not +as much tested as the source-based upgrade path yet. If you prefer to +only use the traditional source-based installation, omit the "--getbinpkg" +parameter in all emerge invocations. + +Note 2: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make
[gentoo-commits] data/gentoo-news:master commit in: 2024-03-12-debianutils-installkernel/
commit: 88dc6642839dd61eb2dc861035adb93419e6e9dd Author: Andrew Ammerlaan gentoo org> AuthorDate: Thu Mar 14 09:44:10 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Thu Mar 14 09:44:10 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=88dc6642 2024-03-12-debianutils-installkernel: clarify who must take action Signed-off-by: Andrew Ammerlaan gentoo.org> .../2024-03-12-debianutils-installkernel.en.txt| 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/2024-03-12-debianutils-installkernel/2024-03-12-debianutils-installkernel.en.txt b/2024-03-12-debianutils-installkernel/2024-03-12-debianutils-installkernel.en.txt index 6f30630..c0ddfd4 100644 --- a/2024-03-12-debianutils-installkernel/2024-03-12-debianutils-installkernel.en.txt +++ b/2024-03-12-debianutils-installkernel/2024-03-12-debianutils-installkernel.en.txt @@ -1,7 +1,7 @@ Title: installkernel is no longer implicitly installed Author: Andrew Ammerlaan Posted: 2024-02-26 -Revision: 1 +Revision: 2 News-Item-Format: 2.0 Display-If-Installed: sys-kernel/installkernel Display-If-Installed: >=sys-apps/debianutils-5.14-r1 @@ -37,11 +37,13 @@ is only installed on the system if it is either explicitly selected or pulled in via the distribution kernels (e.g. gentoo-kernel(-bin)). -User Action Required (all users) +User Action Required (users of manually managed kernels) -Users who currently have sys-kernel/installkernel installed, must -ensure that it is explicitly selected by emerging it: +Users who manually configure, compile, and install their kernels, i.e. +users of the sys-kernel/*-sources packages, and who wish to continue +to use sys-kernel/installkernel, must ensure that it is explicitly +selected by emerging it: emerge --noreplace sys-kernel/installkernel @@ -54,8 +56,12 @@ and then re-install their kernel. cd /usr/src/linux # (or other location of the kernel sources) make install -Note that this re-installation is not required for users of the -distribution kernels (e.g. gentoo-kernel(-bin)). + +No manual action is required for users of the distribution kernels: +- sys-kernel/gentoo-kernel, or +- sys-kernel/gentoo-kernel-bin, or +- sys-kernel/vanilla-kernel + [1] https://wiki.gentoo.org/wiki/Installkernel
[gentoo-commits] data/gentoo-news:master commit in: 2024-03-12-debianutils-installkernel/
commit: 3f723d16c712dbeb428052edbcc25b7c5a3153db Author: Andrew Ammerlaan gentoo org> AuthorDate: Tue Mar 12 18:13:01 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Tue Mar 12 18:13:01 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=3f723d16 2024-03-12-debianutils-installkernel: add news item Signed-off-by: Andrew Ammerlaan gentoo.org> .../2024-03-12-debianutils-installkernel.en.txt| 62 ++ 1 file changed, 62 insertions(+) diff --git a/2024-03-12-debianutils-installkernel/2024-03-12-debianutils-installkernel.en.txt b/2024-03-12-debianutils-installkernel/2024-03-12-debianutils-installkernel.en.txt new file mode 100644 index 000..6f30630 --- /dev/null +++ b/2024-03-12-debianutils-installkernel/2024-03-12-debianutils-installkernel.en.txt @@ -0,0 +1,62 @@ +Title: installkernel is no longer implicitly installed +Author: Andrew Ammerlaan +Posted: 2024-02-26 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: sys-kernel/installkernel +Display-If-Installed: >=sys-apps/debianutils-5.14-r1 +Display-If-Installed: app-misc/ca-certificates + +/sbin/installkernel is a script called by the kernel's "make install" +as well as by the distribution kernel's post-install phase. If you are +reading this then chances are you use and rely on installkernel[1] and +what follows is essential for you. + +Previously sys-kernel/installkernel was implicitly installed on many +systems via a dependency in sys-apps/debianutils. This dependency was +toggled by the "installkernel" USE flag, and enabled by default. + +Until recently, sys-apps/debianutils was in turn pulled in by +app-misc/ca-certificates, an essential package installed on many +systems. However, this dependency of app-misc/ca-certificates on +sys-apps/debianutils was removed[2]. As a result many users may find +that sys-apps/debianutils and therefore sys-kernel/installkernel are no +longer part of the dependency graph and will therefore be cleaned up by +"emerge --depclean". + +Removing sys-kernel/installkernel from your system WILL change the way +kernels are installed by "make install"! Instead of the versioned +/boot/vmlinuz-x.y.z that you are used to, "make install" will simply +copy bzImage (or equivalent for your arch) into /boot. This image may +not be picked up by your bootloader or its configuration tools. + +To avoid surprises from such implicit dependencies from happening again +in the future, the dependency on sys-kernel/installkernel in +sys-apps/debianutils is removed. And as such, sys-kernel/installkernel +is only installed on the system if it is either explicitly selected or +pulled in via the distribution kernels (e.g. gentoo-kernel(-bin)). + + +User Action Required (all users) + + +Users who currently have sys-kernel/installkernel installed, must +ensure that it is explicitly selected by emerging it: + + emerge --noreplace sys-kernel/installkernel + +Users who find that sys-kernel/installkernel has already been cleaned +from their systems and are therefore affected by the change in kernel +installation described above should re-install sys-kernel/installkernel +and then re-install their kernel. + + emerge sys-kernel/installkernel + cd /usr/src/linux # (or other location of the kernel sources) + make install + +Note that this re-installation is not required for users of the +distribution kernels (e.g. gentoo-kernel(-bin)). + + +[1] https://wiki.gentoo.org/wiki/Installkernel +[2] https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6e6ccafd58bc7401fa371d2f255d72ddae0131e6
[gentoo-commits] data/gentoo-news:master commit in: 2024-01-18-installkernel-merge/
commit: 0326966428338218af7df5a32560d27e666c5f4b Author: Andrew Ammerlaan gentoo org> AuthorDate: Tue Feb 20 08:44:41 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Tue Feb 20 08:44:41 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=03269664 2024-01-18-installkernel-merge: further clarifications - explicitly mention rEFInd - put instructions for UKI under its own header - update for new layout=compat so instructions here are again on the same page with the instructions in the next news item about the introduction of USE=systemd-boot. https://forums.gentoo.org/viewtopic-t-1167432-highlight-installkernel.html Signed-off-by: Andrew Ammerlaan gentoo.org> .../2024-01-18-installkernel-merge.en.txt | 53 ++ 1 file changed, 43 insertions(+), 10 deletions(-) diff --git a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt index 96ff934..5af1ad1 100644 --- a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt +++ b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt @@ -1,7 +1,7 @@ Title: Merging of installkernel-gentoo and installkernel-systemd Author: Andrew Ammerlaan Posted: 2024-01-18 -Revision: 6 +Revision: 7 News-Item-Format: 2.0 Display-If-Installed: sys-kernel/installkernel Display-If-Installed: sys-kernel/installkernel-gentoo @@ -77,6 +77,31 @@ emerge --noreplace sys-kernel/installkernel emerge --depclean sys-kernel/installkernel-systemd +User Action Required (rEFInd users) + + +Previously sys-kernel/installkernel-gentoo provided kernel installation +automation for users of rEFInd. The new sys-kernel/installkernel provides the +same functionality, which now works with both the traditional installkernel and +systemd's kernel-install. + +Users of rEFInd should: +- ensure that the "systemd-boot" and "grub" USE flags are NOT enabled when +upgrading to >=sys-kernel/installkernel-20. + +Additionally, users of rEFInd may want to +- enable the "refind" USE flag to +install an icon file alongside the installed kernel image which rEFInd will +pick up at runtime. + +Users of rEFInd may wish to explicitly choose either the traditional +installkernel or systemd's kernel-install, in which case they may do so +via USE=-/+systemd. + +sys-kernel/installkernel is renamed from sys-kernel/installkernel-gentoo, +therefore no further user action is required to upgrade to the new package. + + User Action Required (users of other bootloaders and custom scripts) @@ -85,16 +110,24 @@ plugins should either ensure that the same kernel installation method will be used after upgrading to >=sys-kernel/installkernel-14 (via USE=+/-systemd) or migrate these custom plugins (details are on the wiki [1]). -Users of bootloaders other than GRUB or systemd-boot may want to retain the -traditional /boot layout. They may do so by either: -- disabling the "systemd" USE flag, or -- when the "systemd" USE flag is enabled, enabling the "grub" USE flag as well. -- when the "systemd" USE flag is enabled, setting "layout=grub" in -/etc/kernel/install.conf +Users of bootloaders other than GRUB, systemd-boot or refind may want to retain +the traditional /boot layout. They may do so by: +- ensuring that the "systemd-boot", "grub" and "refind" USE flags are disabled. + + +Optional: Unified Kernel Images (all users) + + +Users who wish to use Unified Kernel Images[2] (e.g. for EFI stub booting) may +do so by +- enabling the "ukify" and "uki" USE flags. +Which will automatically install a bootable EFI executable to the EFI system +partition. + +The UEFI firmware, as well as, Systemd-boot, GRUB and rEFInd are capable of +loading Unified Kernel Images. For more details see the wiki page on Unified +Kernel Images[2] -Users who wish to use EFI stub booting may be interested in building an -Unified Kernel Image[2] by enabling the "ukify" and "uki" USE flags. This will -automatically install a bootable EFI executable to the EFI system partition. [1] https://wiki.gentoo.org/wiki/Installkernel [2] https://wiki.gentoo.org/wiki/Unified_kernel_image
[gentoo-commits] data/gentoo-news:master commit in: 2024-02-01-grub-upgrades/
commit: 6ad32a60e7c1ddb580c3e9d564a594a62583f046 Author: Mike Gilbert gentoo org> AuthorDate: Tue Feb 6 19:29:45 2024 + Commit: Mike Gilbert gentoo org> CommitDate: Tue Feb 6 19:29:45 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=6ad32a60 2024-02-01-grub-upgrades: fix typo Signed-off-by: Mike Gilbert gentoo.org> 2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt b/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt index ddcc224..dc122c1 100644 --- a/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt +++ b/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt @@ -32,7 +32,7 @@ symbol mismatch between the core image and modules. [1] Re-runing grub-install both with and without the --removable option should ensure a working GRUB installation. -However, this will clobber any BOOTX64.EFI image provded by other +However, this will clobber any BOOTX64.EFI image provided by other loaders. If dual-booting using another boot loader, users must take care not to replace BOOTX64.EFI if it is not provided by GRUB.
[gentoo-commits] data/gentoo-news:master commit in: 2024-02-01-grub-upgrades/
commit: e0e93c981baef4a697dac91e8a9efed0a4a204b5 Author: Mike Gilbert gentoo org> AuthorDate: Tue Feb 6 19:26:29 2024 + Commit: Mike Gilbert gentoo org> CommitDate: Tue Feb 6 19:26:29 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=e0e93c98 2024-02-01-grub-upgrades: x86_64-pc -> x86_64-efi Signed-off-by: Mike Gilbert gentoo.org> 2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt b/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt index f7aaa72..ddcc224 100644 --- a/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt +++ b/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt @@ -1,7 +1,7 @@ Title: GRUB upgrades Author: Mike Gilbert Posted: 2024-02-01 -Revision: 1 +Revision: 2 News-Item-Format: 2.0 Display-If-Installed: sys-boot/grub @@ -24,7 +24,7 @@ a stale core image to exist. For example: /boot/efi/EFI/BOOT/BOOTX64.EFI (grub 2.06 core image) /boot/efi/EFI/gentoo/grubx64.efi (grub 2.12 core image) -/boot/grub/x86_64-pc/*.mod (grub 2.12 modules) +/boot/grub/x86_64-efi/*.mod (grub 2.12 modules) Booting this system using BOOTX64.EFI image would likely fail due to a symbol mismatch between the core image and modules. [1]
[gentoo-commits] data/gentoo-news:master commit in: 2024-02-01-grub-upgrades/
commit: 65b494db54e9228fbb4dd0c647f9dd11998c3f4c Author: Mike Gilbert gentoo org> AuthorDate: Sun Jan 28 16:23:22 2024 + Commit: Mike Gilbert gentoo org> CommitDate: Tue Feb 6 00:01:37 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=65b494db 2024-02-01-grub-upgrades: add news item Signed-off-by: Mike Gilbert gentoo.org> .../2024-02-01-grub-upgrades.en.txt| 40 ++ 1 file changed, 40 insertions(+) diff --git a/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt b/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt new file mode 100644 index 000..f7aaa72 --- /dev/null +++ b/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt @@ -0,0 +1,40 @@ +Title: GRUB upgrades +Author: Mike Gilbert +Posted: 2024-02-01 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: sys-boot/grub + +When booting with GRUB, it is important that the core image and modules +have matching versions. Usually, running grub-install is sufficient to +ensure this. + +On the UEFI platform, grub-install allows the core image to be placed in +two different locations: + +EFI/gentoo/grubx64.efi +This is the location used by grub-install without options. + +EFI/BOOT/BOOTX64.EFI +This is the location used by grub-install --removable. + +On upgrades, it is common for users to mismatch the grub-install options +they used for the current and previous versions of grub. This will cause +a stale core image to exist. For example: + +/boot/efi/EFI/BOOT/BOOTX64.EFI (grub 2.06 core image) +/boot/efi/EFI/gentoo/grubx64.efi (grub 2.12 core image) +/boot/grub/x86_64-pc/*.mod (grub 2.12 modules) + +Booting this system using BOOTX64.EFI image would likely fail due to a +symbol mismatch between the core image and modules. [1] + +Re-runing grub-install both with and without the --removable option +should ensure a working GRUB installation. + +However, this will clobber any BOOTX64.EFI image provded by other +loaders. If dual-booting using another boot loader, users must take care +not to replace BOOTX64.EFI if it is not provided by GRUB. + +References: +[1] https://bugs.gentoo.org/920708
[gentoo-commits] data/gentoo-news:master commit in: 2024-02-01-installkernel-new-use-systemd-boot/
commit: c80e4be3ba0315b763146069956fad1de936a8b5 Author: Andrew Ammerlaan gentoo org> AuthorDate: Fri Feb 2 06:25:06 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Fri Feb 2 06:25:06 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=c80e4be3 2024-02-01-installkernel-new-use-systemd-boot: add news item Signed-off-by: Andrew Ammerlaan gentoo.org> ...02-01-installkernel-new-use-systemd-boot.en.txt | 33 ++ 1 file changed, 33 insertions(+) diff --git a/2024-02-01-installkernel-new-use-systemd-boot/2024-02-01-installkernel-new-use-systemd-boot.en.txt b/2024-02-01-installkernel-new-use-systemd-boot/2024-02-01-installkernel-new-use-systemd-boot.en.txt new file mode 100644 index 000..e7b8364 --- /dev/null +++ b/2024-02-01-installkernel-new-use-systemd-boot/2024-02-01-installkernel-new-use-systemd-boot.en.txt @@ -0,0 +1,33 @@ +Title: installkernel new USE flag systemd-boot +Author: Andrew Ammerlaan +Posted: 2024-01-30 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: sys-kernel/installkernel[systemd] +Display-If-Installed: sys-apps/systemd[boot] +Display-If-Installed: sys-apps/systemd-utils[boot] + +/sbin/installkernel is a script called by the kernels 'make install' as well +as by the distribution kernels post install phase. sys-kernel/installkernel +provides two paths for installing the kernel: +- the traditional installkernel, or +- systemd's kernel-install + +In sys-kernel/installkernel versions lower then 20, systemd's kernel-install +would default to the layout used for systemd-boot (layout=bls). To improve +backwards compatibility with the traditional installkernel this is no longer +the case in versions 20 and up. Instead the default layout setting when no other +USE flags are enabled is a compatibility layout similar to the traditional +installkernel (layout=compat). + + +User Action Required (systemd-boot users) + + +Users of systemd-boot should: +- enable the "systemd-boot" USE flag +when upgrading to >=sys-kernel/installkernel-20. + + +See also: https://wiki.gentoo.org/wiki/Installkernel +
[gentoo-commits] data/gentoo-news:master commit in: 2024-01-18-installkernel-merge/
commit: 0803a532d7bd76f02c0f633f9441210f33735594 Author: Andrew Ammerlaan gentoo org> AuthorDate: Fri Feb 2 06:26:17 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Fri Feb 2 06:26:17 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=0803a532 2024-01-18-installkernel-merge: add new USE=systemd-boot Signed-off-by: Andrew Ammerlaan gentoo.org> 2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt index f366180..96ff934 100644 --- a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt +++ b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt @@ -1,7 +1,7 @@ Title: Merging of installkernel-gentoo and installkernel-systemd Author: Andrew Ammerlaan Posted: 2024-01-18 -Revision: 5 +Revision: 6 News-Item-Format: 2.0 Display-If-Installed: sys-kernel/installkernel Display-If-Installed: sys-kernel/installkernel-gentoo @@ -56,7 +56,7 @@ automation for users of systemd-boot. sys-kernel/installkernel provides the same functionality but only via systemd's kernel-install. Users of systemd-boot should therefore: -- ensure that the "systemd" USE flag is enabled +- ensure that the "systemd" and "systemd-boot" USE flags are enabled when upgrading to >=sys-kernel/installkernel-14. Users who are using the distribution kernels (i.e. gentoo-kernel(-bin)) should
[gentoo-commits] data/gentoo-news:master commit in: 2024-01-18-installkernel-merge/
commit: 2f0bf0f10c3c3dd34fdcc3089659ade0691bfcb6 Author: Andrew Ammerlaan gentoo org> AuthorDate: Mon Jan 29 11:02:27 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Mon Jan 29 11:03:53 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=2f0bf0f1 2024-01-18-installkernel-merge: clarify dracut flag https://forums.gentoo.org/viewtopic-p-8814851.html Signed-off-by: Andrew Ammerlaan gentoo.org> .../2024-01-18-installkernel-merge.en.txt | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt index 568ce14..f366180 100644 --- a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt +++ b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt @@ -1,7 +1,7 @@ Title: Merging of installkernel-gentoo and installkernel-systemd Author: Andrew Ammerlaan Posted: 2024-01-18 -Revision: 4 +Revision: 5 News-Item-Format: 2.0 Display-If-Installed: sys-kernel/installkernel Display-If-Installed: sys-kernel/installkernel-gentoo @@ -63,6 +63,11 @@ Users who are using the distribution kernels (i.e. gentoo-kernel(-bin)) should enable the "dracut" USE flag on installkernel as well to pull in and enable the dracut initramfs generator. This is enforced by portage. +Note that the automagic behaviour of the dracut kernel-install plugin is +removed in sys-kernel/installkernel. Users who rely on the dracut plugin +automatically generating an initramfs when installing the kernel must +enable the "dracut" USE flag to retain this behaviour. + The upgrade path is enforced by sys-kernel/installkernel-systemd-4, which is just a wrapper pulling in >=sys-kernel/installkernel-14 with the "systemd" flag enabled. sys-kernel/installkernel-systemd may be removed after installing
[gentoo-commits] data/gentoo-news:master commit in: 2024-01-18-installkernel-merge/
commit: 5855de3f2808c3203b690a3f4e04ad5f66b93417 Author: Andrew Ammerlaan gentoo org> AuthorDate: Mon Jan 29 09:28:20 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Mon Jan 29 09:28:20 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=5855de3f 2024-01-18-installkernel-merge: improve formatting, fix typo Signed-off-by: Andrew Ammerlaan gentoo.org> .../2024-01-18-installkernel-merge.en.txt | 19 --- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt index 991c95d..568ce14 100644 --- a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt +++ b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt @@ -1,7 +1,7 @@ Title: Merging of installkernel-gentoo and installkernel-systemd Author: Andrew Ammerlaan Posted: 2024-01-18 -Revision: 3 +Revision: 4 News-Item-Format: 2.0 Display-If-Installed: sys-kernel/installkernel Display-If-Installed: sys-kernel/installkernel-gentoo @@ -33,9 +33,12 @@ User Action Required (GRUB users) Previously sys-kernel/installkernel-gentoo provided kernel installation automation for users of GRUB via USE=grub. The new sys-kernel/installkernel provides the same functionality, which now works with both the traditional -installkernel and systemd's kernel-install. Users of GRUB should check that -the "grub" USE flag is enabled to ensure that systemd's kernel-install uses -the correct layout that grub-mkconfig understands. +installkernel and systemd's kernel-install. + +Users of GRUB should therefore: +- check that the "grub" USE flag is enabled +to ensure that systemd's kernel-install uses the correct layout that +grub-mkconfig understands. Users of GRUB may wish to explicitly choose either the traditional installkernel or systemd's kernel-install, in which case they may do so @@ -50,8 +53,10 @@ User Action Required (systemd-boot users) Previously sys-kernel/installkernel-systemd provided kernel installation automation for users of systemd-boot. sys-kernel/installkernel provides -the same functionality but only via systemd's kernel-install. Users -of systemd-boot should therefore ensure that the "systemd" USE flag is enabled +the same functionality but only via systemd's kernel-install. + +Users of systemd-boot should therefore: +- ensure that the "systemd" USE flag is enabled when upgrading to >=sys-kernel/installkernel-14. Users who are using the distribution kernels (i.e. gentoo-kernel(-bin)) should @@ -75,7 +80,7 @@ plugins should either ensure that the same kernel installation method will be used after upgrading to >=sys-kernel/installkernel-14 (via USE=+/-systemd) or migrate these custom plugins (details are on the wiki [1]). -Users of bootloaders other then GRUB or systemd-boot may want to retain the +Users of bootloaders other than GRUB or systemd-boot may want to retain the traditional /boot layout. They may do so by either: - disabling the "systemd" USE flag, or - when the "systemd" USE flag is enabled, enabling the "grub" USE flag as well.
[gentoo-commits] data/gentoo-news:master commit in: 2024-01-18-installkernel-merge/
commit: 53ad0609398e3424ea4d151bcec887e5112b7ea7 Author: Andrew Ammerlaan gentoo org> AuthorDate: Mon Jan 29 09:08:13 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Mon Jan 29 09:08:13 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=53ad0609 2024-01-18-installkernel-merge: improve clarity - explicitly say that installkernel is called by make install - explicitly say that users of GRUB are expected to enable the grub USE flag - add instructions for retaining the traditional /boot layout for users of other bootloaders - explicitly say that Unified Kernel Images may be wanted to semi-automate EFI stub booting Signed-off-by: Andrew Ammerlaan gentoo.org> .../2024-01-18-installkernel-merge.en.txt | 30 +- 1 file changed, 23 insertions(+), 7 deletions(-) diff --git a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt index aaf7884..991c95d 100644 --- a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt +++ b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt @@ -1,15 +1,18 @@ Title: Merging of installkernel-gentoo and installkernel-systemd Author: Andrew Ammerlaan Posted: 2024-01-18 -Revision: 2 +Revision: 3 News-Item-Format: 2.0 Display-If-Installed: sys-kernel/installkernel Display-If-Installed: sys-kernel/installkernel-gentoo Display-If-Installed: sys-kernel/installkernel-systemd Display-If-Installed: sys-kernel/installkernel-systemd-boot -The functionalities of sys-kernel/installkernel-gentoo and -sys-kernel/installkernel-systemd have been merged into sys-kernel/installkernel. +/sbin/installkernel is a script called by the kernels 'make install' as well +as by the distribution kernels post install phase. It was previously provided +by sys-kernel/installkernel-gentoo or sys-kernel/installkernel-systemd. The +functionalities of these two packages have now been merged into +sys-kernel/installkernel. sys-kernel/installkernel now provides the systemd USE flag to switch between the traditional installkernel (formerly sys-kernel/installkernel-gentoo) and @@ -30,13 +33,16 @@ User Action Required (GRUB users) Previously sys-kernel/installkernel-gentoo provided kernel installation automation for users of GRUB via USE=grub. The new sys-kernel/installkernel provides the same functionality, which now works with both the traditional -installkernel and systemd's kernel-install. In principle no user action is -required unless users wish to explicitly choose either the traditional +installkernel and systemd's kernel-install. Users of GRUB should check that +the "grub" USE flag is enabled to ensure that systemd's kernel-install uses +the correct layout that grub-mkconfig understands. + +Users of GRUB may wish to explicitly choose either the traditional installkernel or systemd's kernel-install, in which case they may do so via USE=-/+systemd. sys-kernel/installkernel is renamed from sys-kernel/installkernel-gentoo, -therefore no user action is required to upgrade. +therefore no user action is required to upgrade to the new package. User Action Required (systemd-boot users) @@ -69,6 +75,16 @@ plugins should either ensure that the same kernel installation method will be used after upgrading to >=sys-kernel/installkernel-14 (via USE=+/-systemd) or migrate these custom plugins (details are on the wiki [1]). +Users of bootloaders other then GRUB or systemd-boot may want to retain the +traditional /boot layout. They may do so by either: +- disabling the "systemd" USE flag, or +- when the "systemd" USE flag is enabled, enabling the "grub" USE flag as well. +- when the "systemd" USE flag is enabled, setting "layout=grub" in +/etc/kernel/install.conf -[1] https://wiki.gentoo.org/wiki/Installkernel +Users who wish to use EFI stub booting may be interested in building an +Unified Kernel Image[2] by enabling the "ukify" and "uki" USE flags. This will +automatically install a bootable EFI executable to the EFI system partition. +[1] https://wiki.gentoo.org/wiki/Installkernel +[2] https://wiki.gentoo.org/wiki/Unified_kernel_image
[gentoo-commits] data/gentoo-news:master commit in: 2024-01-18-installkernel-merge/
commit: 65a74554e82b97334e608980f7205d8a2114c287 Author: Andrew Ammerlaan gentoo org> AuthorDate: Wed Jan 24 15:03:34 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Wed Jan 24 15:03:34 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=65a74554 2024-01-18-installkernel-merge: add note on enabling dracut flag This is now required since we no longer enable the dracut flag by default Signed-off-by: Andrew Ammerlaan gentoo.org> .../2024-01-18-installkernel-merge.en.txt| 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt index 3b36c73..aaf7884 100644 --- a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt +++ b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt @@ -1,7 +1,7 @@ Title: Merging of installkernel-gentoo and installkernel-systemd Author: Andrew Ammerlaan Posted: 2024-01-18 -Revision: 1 +Revision: 2 News-Item-Format: 2.0 Display-If-Installed: sys-kernel/installkernel Display-If-Installed: sys-kernel/installkernel-gentoo @@ -45,11 +45,15 @@ User Action Required (systemd-boot users) Previously sys-kernel/installkernel-systemd provided kernel installation automation for users of systemd-boot. sys-kernel/installkernel provides the same functionality but only via systemd's kernel-install. Users -of systemd-boot should therefore ensure that the systemd USE flag is enabled +of systemd-boot should therefore ensure that the "systemd" USE flag is enabled when upgrading to >=sys-kernel/installkernel-14. -This upgrade path is enforced by sys-kernel/installkernel-systemd-4, which is -just a wrapper pulling in >=sys-kernel/installkernel-14 with the systemd flag +Users who are using the distribution kernels (i.e. gentoo-kernel(-bin)) should +enable the "dracut" USE flag on installkernel as well to pull in and enable +the dracut initramfs generator. This is enforced by portage. + +The upgrade path is enforced by sys-kernel/installkernel-systemd-4, which is +just a wrapper pulling in >=sys-kernel/installkernel-14 with the "systemd" flag enabled. sys-kernel/installkernel-systemd may be removed after installing >=sys-kernel/installkernel-14.
[gentoo-commits] data/gentoo-news:master commit in: 2024-01-18-installkernel-merge/
commit: 201e8195c272a70afa8270f2ee300355344626ec Author: Andrew Ammerlaan gentoo org> AuthorDate: Mon Jan 22 08:46:06 2024 + Commit: Andrew Ammerlaan gentoo org> CommitDate: Mon Jan 22 08:46:06 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=201e8195 2024-01-18-installkernel-merge: add news item Signed-off-by: Andrew Ammerlaan gentoo.org> .../2024-01-18-installkernel-merge.en.txt | 70 ++ 1 file changed, 70 insertions(+) diff --git a/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt new file mode 100644 index 000..3b36c73 --- /dev/null +++ b/2024-01-18-installkernel-merge/2024-01-18-installkernel-merge.en.txt @@ -0,0 +1,70 @@ +Title: Merging of installkernel-gentoo and installkernel-systemd +Author: Andrew Ammerlaan +Posted: 2024-01-18 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: sys-kernel/installkernel +Display-If-Installed: sys-kernel/installkernel-gentoo +Display-If-Installed: sys-kernel/installkernel-systemd +Display-If-Installed: sys-kernel/installkernel-systemd-boot + +The functionalities of sys-kernel/installkernel-gentoo and +sys-kernel/installkernel-systemd have been merged into sys-kernel/installkernel. + +sys-kernel/installkernel now provides the systemd USE flag to switch between +the traditional installkernel (formerly sys-kernel/installkernel-gentoo) and +systemd's kernel-install (formerly sys-kernel/installkernel-systemd(-boot)). + +Additionally, the new sys-kernel/installkernel with the systemd flag enabled +now provides a default install.conf configuration file which ensures that it +will work out-of-the-box with no configuration (other then USE flag +configuration) required for most setups. + +Details on configuration and customization can be found on the installkernel +wiki page [1]. Below we provide the most important migration notes. + + +User Action Required (GRUB users) + + +Previously sys-kernel/installkernel-gentoo provided kernel installation +automation for users of GRUB via USE=grub. The new sys-kernel/installkernel +provides the same functionality, which now works with both the traditional +installkernel and systemd's kernel-install. In principle no user action is +required unless users wish to explicitly choose either the traditional +installkernel or systemd's kernel-install, in which case they may do so +via USE=-/+systemd. + +sys-kernel/installkernel is renamed from sys-kernel/installkernel-gentoo, +therefore no user action is required to upgrade. + + +User Action Required (systemd-boot users) + + +Previously sys-kernel/installkernel-systemd provided kernel installation +automation for users of systemd-boot. sys-kernel/installkernel provides +the same functionality but only via systemd's kernel-install. Users +of systemd-boot should therefore ensure that the systemd USE flag is enabled +when upgrading to >=sys-kernel/installkernel-14. + +This upgrade path is enforced by sys-kernel/installkernel-systemd-4, which is +just a wrapper pulling in >=sys-kernel/installkernel-14 with the systemd flag +enabled. sys-kernel/installkernel-systemd may be removed after installing +>=sys-kernel/installkernel-14. + +emerge --noreplace sys-kernel/installkernel +emerge --depclean sys-kernel/installkernel-systemd + + +User Action Required (users of other bootloaders and custom scripts) + + +Users who have previously relied on custom installkernel or kernel-install +plugins should either ensure that the same kernel installation method will be +used after upgrading to >=sys-kernel/installkernel-14 (via USE=+/-systemd) or +migrate these custom plugins (details are on the wiki [1]). + + +[1] https://wiki.gentoo.org/wiki/Installkernel +
[gentoo-commits] data/gentoo-news:master commit in: 2024-01-05-usr-initramfs/
commit: 114a15884faf88f202073de48812613b264f49e0 Author: Eli Schwartz gmail com> AuthorDate: Tue Jan 2 04:04:32 2024 + Commit: Sam James gentoo org> CommitDate: Fri Jan 5 04:10:37 2024 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=114a1588 2024-01-05-usr-initramfs: add news item Revival of commit a79dd69b0cca439bc0c483c9193c79e0554819d0. Bug: https://bugs.gentoo.org/868306#c10 Bug: https://bugs.gentoo.org/902829 Bug: https://bugs.gentoo.org/915379 Bug: https://bugs.gentoo.org/825078 Signed-off-by: Eli Schwartz gmail.com> Signed-off-by: Sam James gentoo.org> .../2024-01-05-usr-initramfs.en.txt| 46 ++ 1 file changed, 46 insertions(+) diff --git a/2024-01-05-usr-initramfs/2024-01-05-usr-initramfs.en.txt b/2024-01-05-usr-initramfs/2024-01-05-usr-initramfs.en.txt new file mode 100644 index 000..c54d978 --- /dev/null +++ b/2024-01-05-usr-initramfs/2024-01-05-usr-initramfs.en.txt @@ -0,0 +1,46 @@ +Title: Separate /usr now requires an initramfs +Author: Eli Schwartz +Posted: 2024-01-05 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: sys-apps/baselayout[split-usr] + +Systems which have /usr and / on separate filesystems have always required a +dedicated initramfs to bring up both partitions. Systems where both /usr and / +are on the same filesystem may use an initramfs if they wish, or choose not +to. + +Historically, Gentoo has tried to make the separate filesystems use case work +anyway. Despite all our efforts, it is broken and continues to get more broken +under various configurations. The only workable solution is to support +separate /usr but only when an initramfs is present. For more details on why +this is broken, see: + +- https://bugs.gentoo.org/868306#c10 +- https://bugs.gentoo.org/902829 +- http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken +- https://bugs.gentoo.org/915379 +- https://github.com/trofi/nix-guix-gentoo/commit/43d84cc00af530ef912d9c98448b64d6b5282907 +- https://github.com/trofi/nix-guix-gentoo/commit/8f194519982fbfabb6b3ca84c0806b1a379b5d06 +- https://bugs.gentoo.org/825078 + +In 2013, Gentoo policy determined that separate /usr without an initramfs was +officially no longer supported: + +- https://projects.gentoo.org/qa/policy-guide/filesystem.html#pg0202 +- https://gitweb.gentoo.org/data/gentoo-news.git/tree/2013/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt?id=a79dd69b0cca439bc0c483c9193c79e0554819d0 + +11 years later, the support is being withdrawn. On 2024-02-05, we plan to +begin work on decommissioning existing workarounds and will not accept any +more. + +User Action Required + + +If you have separate /usr and are not currently using an initramfs, you have +until 2024-02-05 to set up an initramfs. If you do not, then at some point on +or after this date, routine system upgrades will leave your system unbootable. + +For details on setting up an initramfs, see: + +https://wiki.gentoo.org/wiki/Initramfs/Guide
[gentoo-commits] data/gentoo-news:master commit in: 2023-12-28-lxd-to-lose-access-for-its-image-server/
commit: 1dc53c33d97053429b8c7a82aca0066c139d2da6 Author: Joonas Niilola gentoo org> AuthorDate: Thu Dec 28 17:18:06 2023 + Commit: Joonas Niilola gentoo org> CommitDate: Thu Dec 28 17:20:13 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=1dc53c33 2023-12-28-lxd-to-lose-access-for-its-image-server: add news item Bug: https://bugs.gentoo.org/920527 Signed-off-by: Joonas Niilola gentoo.org> ...-lxd-to-lose-access-for-its-image-server.en.txt | 44 ++ 1 file changed, 44 insertions(+) diff --git a/2023-12-28-lxd-to-lose-access-for-its-image-server/2023-12-28-lxd-to-lose-access-for-its-image-server.en.txt b/2023-12-28-lxd-to-lose-access-for-its-image-server/2023-12-28-lxd-to-lose-access-for-its-image-server.en.txt new file mode 100644 index 000..64d1b54 --- /dev/null +++ b/2023-12-28-lxd-to-lose-access-for-its-image-server/2023-12-28-lxd-to-lose-access-for-its-image-server.en.txt @@ -0,0 +1,44 @@ +Title: LXD to lose access for its image server +Author: Joonas Niilola +Posted: 2023-12-28 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: app-containers/lxd + +Earlier this year Canonical took their LXD project away from the +community-run LinuxContainers and brought it under their own +administration. +While doing so, they removed management access from non-Canonical +employees, along with other things. This caused LXD to be forked and so +Incus was born. Incus would pull updates from upstream LXD to stay +compatible. + +Recently LXD was re-licensed so Incus can't benefit from its code +anymore. Therefore Incus will become a truly independent project. + +However it is LinuxContainers community that still hosts most LXD +images for free, for Incus and LXD. With them unable to benefit or use +LXD anymore, LinuxContainers have decided to stop building and hosting +LXD images. Realistically they can't support LXD given these +restrictions. + +They will start limiting access immediately in 2024 for non-LTS users +which is LXD >=5.18, or "unstable" in Gentoo. LTS LXD, or "stable" +(5.0) in Gentoo will be allowed to pull images until May (an estimate), +or until Incus LTS will be released. Times are subject to change. + +What can you do? + + +1: Switch to Incus. +2: Deploy your own image server. +3: Wait and see what Canonical does. + +For unstable users the matter is rather critical, while stable users +have the luxury of waiting. Note that a downgrade from unstable to +stable is not possible due to database schemas. + +Please follow or take a look at Gentoo bug #920527 with more +information about this situation, and updates e.g. for timetables. + +Bug: https://bugs.gentoo.org/920527
[gentoo-commits] data/gentoo-news:master commit in: 2023-12-17-cups-filters/
commit: 5f4b2f96819a82f3713e78bb72438eeda80ce8f2 Author: Eli Schwartz gmail com> AuthorDate: Mon Dec 4 06:09:54 2023 + Commit: Sam James gentoo org> CommitDate: Mon Dec 18 03:35:32 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=5f4b2f96 2023-12-17-cups-filters.en.txt: add news item Bug: https://bugs.gentoo.org/914586 Bug: https://bugs.gentoo.org/813507 Signed-off-by: Eli Schwartz gmail.com> Signed-off-by: Sam James gentoo.org> .../2023-12-17-cups-filters.en.txt | 41 ++ 1 file changed, 41 insertions(+) diff --git a/2023-12-17-cups-filters/2023-12-17-cups-filters.en.txt b/2023-12-17-cups-filters/2023-12-17-cups-filters.en.txt new file mode 100644 index 000..ec88925 --- /dev/null +++ b/2023-12-17-cups-filters/2023-12-17-cups-filters.en.txt @@ -0,0 +1,41 @@ +Title: CUPS no longer directly depends on its filters +Author: Eli Schwartz +Posted: 2023-11-20 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: >=net-print/cups-2.4.7-r2 + +Reasons +=== + +Historically, net-print/cups has both depended on and been a dependency of +net-print/cups-filters. The latter is required for usability of a CUPS +printing setup, but also must build against the former's libraries. This +results in an ugly dependency cycle, and forcing the entire CUPS printing +setup wherever USE=cups is enabled on a framework. + +Current upstream work on CUPS has focused on modularizing the codebase. There +are now several packages, and there will be more in the future. Installing +net-print/cups-filters is no longer sufficient to ensure all components are +installed. + +In the future, when CUPS v3 is released, filters will be exclusive to legacy +printers, and largely replaced with IPP Everywhere.[1] + +A more future-proof way to install a CUPS production printing setup is needed. + +User Action Required +=== + +cups-filters is required for current versions of CUPS. To prevent depcleaning +if you are a CUPS user (and it was not installed just as a dependency for +something else): + +emerge net-print/cups-meta + +If cups-browsed support is desired, add the following package.use: + +net-print/cups-meta browsed + + +[1] https://openprinting.github.io/current/#the-new-architecture-for-printing-and-scanning
[gentoo-commits] data/gentoo-news:master commit in: 2023-05-20-kde-pipewire-wayland/
commit: 7530e88b17e71806bdb75dcc71f658d2510efc1f Author: Andreas Sturmlechner gentoo org> AuthorDate: Sun May 21 06:58:10 2023 + Commit: Andreas Sturmlechner gentoo org> CommitDate: Sun May 21 06:58:10 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=7530e88b 2023-05-20-kde-pipewire-wayland.en.txt: Add news item Signed-off-by: Andreas Sturmlechner gentoo.org> .../2023-05-20-kde-pipewire-wayland.en.txt | 77 ++ 1 file changed, 77 insertions(+) diff --git a/2023-05-20-kde-pipewire-wayland/2023-05-20-kde-pipewire-wayland.en.txt b/2023-05-20-kde-pipewire-wayland/2023-05-20-kde-pipewire-wayland.en.txt new file mode 100644 index 000..411b820 --- /dev/null +++ b/2023-05-20-kde-pipewire-wayland/2023-05-20-kde-pipewire-wayland.en.txt @@ -0,0 +1,77 @@ +Title: Plasma Profile to enable PipeWire, Wayland support +Author: Andreas Sturmlechner +Posted: 2023-05-21 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Profile: default/linux/amd64/17.1/desktop/plasma +Display-If-Profile: default/linux/amd64/17.1/desktop/plasma/systemd +Display-If-Profile: default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr +Display-If-Profile: default/linux/amd64/23.0/desktop/plasma +Display-If-Profile: default/linux/amd64/23.0/desktop/plasma/systemd + +Reasons +=== + +Gentoo's Plasma profile has not had any sound server enabled since the days of +KDE's own aRts. As the way we output sound has changed dramatically in the years +since - using wireless or often several devices, dynamically connected and +shared between multiple systems, a modern desktop environment is expected to +handle this effortlessly by default. + +In Wayland sessions, the video functionality of PipeWire is not only used for +screensharing but also to take screenshots and -recordings or simply to cast +window content onto task managers' window previews. This is why PipeWire and +Wayland enablement are happening at the same time. + +Plasma Wayland support has come a long way and we consider it stable enough for +daily use with a lot - if not all - systems, even if some known papercuts +remain [1]. Therefore it makes sense for Plasma profile to provide sane default +settings. + + +Changes +=== + +New global USE flags enabled: pipewire, pulseaudio, screencast, wayland +New package.use default: media-video/pipewire[sound-server] + +We want broad sound server support in packages, and these settings will make +PipeWire act as our PulseAudio server where there is no native PipeWire support. + + +Impact On Happy X Users +=== + +Minor. Most dependencies were already required with kde-plasma/plasma-desktop +and its dependencies. Upcoming stable versions of kde-apps/spectacle and +kde-apps/krfb will depend on (K)PipeWire unconditionally. + +No one will lose their X session, but will have the option to easily log in to +a working Wayland session at any time. + +It is possible to set USE="-wayland" against these changes, but it will amount +to no dependency savings, just micro-optimisation in affected packages. + + +User Action Required + + +In order to enact all changes: + +emerge -1avUD @world +Check out how to configure PipeWire for your purpose [2][3] + +In order to keep a PulseAudio or ALSA-only setup: + +Invert above new USE flag settings as needed, see also [2]. + +In order to avoid media-video/pipewire completely: + +This can only be achieved by losing basic task manager, screenshot/screen +recording/sharing functions as provided by Plasma and KDE applications. + + +[1] https://community.kde.org/Plasma/Wayland_Showstoppers +[2] https://www.gentoo.org/support/news-items/2022-07-29-pipewire-sound-server. +html +[3] https://wiki.gentoo.org/wiki/PipeWire
[gentoo-commits] data/gentoo-news:master commit in: 2023-05-11-openssh/
commit: 4d1ca67d4fca1750c90ee3a94375cbbf05d4fd4c Author: Sam James gentoo org> AuthorDate: Sun May 14 05:38:56 2023 + Commit: Sam James gentoo org> CommitDate: Sun May 14 05:39:05 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=4d1ca67d 2023-05-11-openssh: crank revision for earlier changes Fixes: 8a2ba6292647ec521fbf546d6b4c7ed17648ea1a Signed-off-by: Sam James gentoo.org> 2023-05-11-openssh/2023-05-11-openssh.en.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2023-05-11-openssh/2023-05-11-openssh.en.txt b/2023-05-11-openssh/2023-05-11-openssh.en.txt index b679d3e..fb72bad 100644 --- a/2023-05-11-openssh/2023-05-11-openssh.en.txt +++ b/2023-05-11-openssh/2023-05-11-openssh.en.txt @@ -1,7 +1,7 @@ Title: OpenSSH directory configuration changes Author: Sam James Posted: 2023-05-11 -Revision: 1 +Revision: 2 News-Item-Format: 2.0 Display-If-Installed: net-misc/openssh
[gentoo-commits] data/gentoo-news:master commit in: 2023-05-11-openssh/
commit: 8a2ba6292647ec521fbf546d6b4c7ed17648ea1a Author: Sam James gentoo org> AuthorDate: Sat May 13 05:40:05 2023 + Commit: Sam James gentoo org> CommitDate: Sat May 13 05:40:05 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=8a2ba629 2023-05-11-openssh: fix config file typo Also, we want to show it to everyone regardless of OpenSSH version for a while. Signed-off-by: Sam James gentoo.org> 2023-05-11-openssh/2023-05-11-openssh.en.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2023-05-11-openssh/2023-05-11-openssh.en.txt b/2023-05-11-openssh/2023-05-11-openssh.en.txt index 9d2a04b..b679d3e 100644 --- a/2023-05-11-openssh/2023-05-11-openssh.en.txt +++ b/2023-05-11-openssh/2023-05-11-openssh.en.txt @@ -3,7 +3,7 @@ Author: Sam James Posted: 2023-05-11 Revision: 1 News-Item-Format: 2.0 -Display-If-Installed: >=net-misc/openssh-9.3_p1-r1 +Display-If-Installed: net-misc/openssh Gentoo's OpenSSH package will start using the /etc/ssh/sshd_config.d and /etc/ssh/ssh_config.d directories for both Gentoo default settings @@ -24,4 +24,4 @@ number in the filename. For example, if the system administrator has commented out 'AcceptEnv COLORTERM' in /etc/ssh/sshd_config, they will need to do the same in the new -/etc/ssh/sshd_config.d/90gentoo.conf file. +/etc/ssh/sshd_config.d/999gentoo.conf file.
[gentoo-commits] data/gentoo-news:master commit in: 2023-05-11-openssh/, 2023-05-08-openssh/
commit: 6352eb1c086adf27d4dea0858d4c7d9299726149 Author: Sam James gentoo org> AuthorDate: Thu May 11 20:05:30 2023 + Commit: Sam James gentoo org> CommitDate: Thu May 11 20:05:30 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=6352eb1c 2023-05-11-openssh: rename from 2023-05-08-openssh Signed-off-by: Sam James gentoo.org> .../2023-05-11-openssh.en.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2023-05-08-openssh/2023-05-08-openssh.en.txt b/2023-05-11-openssh/2023-05-11-openssh.en.txt similarity index 98% rename from 2023-05-08-openssh/2023-05-08-openssh.en.txt rename to 2023-05-11-openssh/2023-05-11-openssh.en.txt index babbf0a..9d2a04b 100644 --- a/2023-05-08-openssh/2023-05-08-openssh.en.txt +++ b/2023-05-11-openssh/2023-05-11-openssh.en.txt @@ -1,6 +1,6 @@ Title: OpenSSH directory configuration changes Author: Sam James -Posted: 2023-05-08 +Posted: 2023-05-11 Revision: 1 News-Item-Format: 2.0 Display-If-Installed: >=net-misc/openssh-9.3_p1-r1
[gentoo-commits] data/gentoo-news:master commit in: 2023-05-08-openssh/
commit: 7e639ce28d0e18322b00ab66789ef1844debaf9f Author: Sam James gentoo org> AuthorDate: Mon May 8 16:21:14 2023 + Commit: Sam James gentoo org> CommitDate: Tue May 9 21:23:53 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=7e639ce2 2023-05-08-openssh: add item Signed-off-by: Sam James gentoo.org> 2023-05-08-openssh/2023-05-08-openssh.en.txt | 27 +++ 1 file changed, 27 insertions(+) diff --git a/2023-05-08-openssh/2023-05-08-openssh.en.txt b/2023-05-08-openssh/2023-05-08-openssh.en.txt new file mode 100644 index 000..babbf0a --- /dev/null +++ b/2023-05-08-openssh/2023-05-08-openssh.en.txt @@ -0,0 +1,27 @@ +Title: OpenSSH directory configuration changes +Author: Sam James +Posted: 2023-05-08 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: >=net-misc/openssh-9.3_p1-r1 + +Gentoo's OpenSSH package will start using the /etc/ssh/sshd_config.d +and /etc/ssh/ssh_config.d directories for both Gentoo default settings +and use by the administrator. + +The default /etc/ssh/sshd_config and /etc/ssh/ssh_config files will +respectively include configuration files in /etc/ssh/sshd_config.d/* and +/etc/ssh/ssh_config.d/*, making it possible for all customization and +configuration to be done via 'drop-in' files if desired. + +Most users will not need to take any action. The only action required +is if specific Gentoo defaults were overridden in the past, as the new +ebuilds will install them to new files in the new listed directories. + +Such admins will need to edit the new files in the new directories or +make overrides in their own files in the new directories using a smaller +number in the filename. + +For example, if the system administrator has commented out 'AcceptEnv COLORTERM' +in /etc/ssh/sshd_config, they will need to do the same in the new +/etc/ssh/sshd_config.d/90gentoo.conf file.
[gentoo-commits] data/gentoo-news:master commit in: 2023-04-02-python3-11/
commit: f7813ad2b7214195e7776dcc801286139ce6ba3c Author: Michał Górny gentoo org> AuthorDate: Mon Apr 3 03:09:10 2023 + Commit: Michał Górny gentoo org> CommitDate: Mon Apr 3 03:09:10 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=f7813ad2 2023-04-02-python3-11: fix next version Signed-off-by: Michał Górny gentoo.org> 2023-04-02-python3-11/2023-04-02-python3-11.en.txt | 2 +- 2023-04-02-python3-11/2023-04-02-python3-11.pl.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/2023-04-02-python3-11/2023-04-02-python3-11.en.txt b/2023-04-02-python3-11/2023-04-02-python3-11.en.txt index cf24ef1..4956c7c 100644 --- a/2023-04-02-python3-11/2023-04-02-python3-11.en.txt +++ b/2023-04-02-python3-11/2023-04-02-python3-11.en.txt @@ -107,7 +107,7 @@ Finally, switch to the final version and upgrade: 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.11, and upgrade manually then. +to Python 3.12, and upgrade manually then. Upgrade commands diff --git a/2023-04-02-python3-11/2023-04-02-python3-11.pl.txt b/2023-04-02-python3-11/2023-04-02-python3-11.pl.txt index 5c49639..5804857 100644 --- a/2023-04-02-python3-11/2023-04-02-python3-11.pl.txt +++ b/2023-04-02-python3-11/2023-04-02-python3-11.pl.txt @@ -119,7 +119,7 @@ kolejną aktualizację: Po terminie zmiany domyślnych wartości, konfigurację tę można usunąć. Alternatywnie, pozostawienie jej zablokuje przyszłą aktualizację -do Pythona 3.11 i pozwoli na ręczne przeprowadzenie bezpieczniej +do Pythona 3.12 i pozwoli na ręczne przeprowadzenie bezpieczniej aktualizacji.
[gentoo-commits] data/gentoo-news:master commit in: 2023-04-02-python3-11/
commit: 799e50b7a13302a6135fa7cd3391ecbe48576fc2 Author: Michał Górny gentoo org> AuthorDate: Sun Apr 2 15:15:27 2023 + Commit: Michał Górny gentoo org> CommitDate: Sun Apr 2 15:15:27 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=799e50b7 2023-04-02-python3-11: add polish translation Signed-off-by: Michał Górny gentoo.org> 2023-04-02-python3-11/2023-04-02-python3-11.pl.txt | 138 + 1 file changed, 138 insertions(+) diff --git a/2023-04-02-python3-11/2023-04-02-python3-11.pl.txt b/2023-04-02-python3-11/2023-04-02-python3-11.pl.txt new file mode 100644 index 000..5c49639 --- /dev/null +++ b/2023-04-02-python3-11/2023-04-02-python3-11.pl.txt @@ -0,0 +1,138 @@ +Title: Python 3.11 stanie się domyślną wersją począwszy od 2023-05-01 +Author: Michał Górny +Translator: Michał Górny +Posted: 2023-04-02 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: dev-lang/python:3.9 +Display-If-Installed: dev-lang/python:3.10 + +Gentoo planuje zmienić domyślną wersję Pythona z 3.10 na 3.11 w dniu +1. maja 2023 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. + +W tym samym czasie wsparcie Pythona 3.9 zostanie usunięte z eclass. +Paczka interpretera pozostanie wspierana tak długo, jak to będzie +możliwe. PyPy3.9 będzie wspierane do momentu wydania i stabilizacji +PyPy3.10. + + +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_10 +*/* PYTHON_SINGLE_TARGET: -* python3_10 + +W ten sposób Python 3.10 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.11: + +*/* PYTHON_TARGETS: -* python3_11 +*/* PYTHON_SINGLE_TARGET: -* python3_11 + +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.11 w pierwszym kroku, a następnie usunięcie Pythona +3.10. 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: + +*/*
[gentoo-commits] data/gentoo-news:master commit in: 2023-04-02-python3-11/
commit: bf718a7c9761e42e51c9deaa6a1fe7241be4c04a Author: Michał Górny gentoo org> AuthorDate: Fri Mar 31 17:15:15 2023 + Commit: Michał Górny gentoo org> CommitDate: Sun Apr 2 15:11:49 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=bf718a7c 2023-04-01-python3-11: add news item Signed-off-by: Michał Górny gentoo.org> 2023-04-02-python3-11/2023-04-02-python3-11.en.txt | 125 + 1 file changed, 125 insertions(+) diff --git a/2023-04-02-python3-11/2023-04-02-python3-11.en.txt b/2023-04-02-python3-11/2023-04-02-python3-11.en.txt new file mode 100644 index 000..cf24ef1 --- /dev/null +++ b/2023-04-02-python3-11/2023-04-02-python3-11.en.txt @@ -0,0 +1,125 @@ +Title: Python 3.11 to become the default on 2023-05-01 +Author: Michał Górny +Posted: 2023-04-02 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: dev-lang/python:3.9 +Display-If-Installed: dev-lang/python:3.10 + +We are planning to switch the default Python target of Gentoo systems +on 2023-05-01, from Python 3.10 to Python 3.11. 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). + +At the same time, the support for Python 3.9 target will be removed +from the eclasses. The interpreter package will remain supported +for as long as feasible though. PyPy3.9 will remain supported until +PyPy3.10 comes out and becomes stable. + + +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_10 +*/* PYTHON_SINGLE_TARGET: -* python3_10 + +This will enforce Python 3.10 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.11 targets: + +*/* PYTHON_TARGETS: -* python3_11 +*/* PYTHON_SINGLE_TARGET: -* python3_11 + +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.11 support to your system first, +and only then remove Python 3.10. However, note that this involves two +rebuilds of all the affected packages, so it will take noticeably +longer. + +First, enable both Python 3.10 and Python 3.11, and then run the upgrade +commands: + +*/* PYTHON_TARGETS: -* python3_10 python3_11 +*/* PYTHON_SINGLE_TARGET: -* python3_10 + +Then switch PYTHON_SINGLE_TARGET and run the second batch of upgrades: + +*/* PYTHON_TARGETS: -* python3_10 python3_11 +*/* PYTHON_SINGLE_TARGET: -* python3_11 + +Finally, switch to the final version and upgrade: + +*/* PYTHON_TARGETS: -* python3_11 +*/* PYTHON_SINGLE_TARGET: -* python3_11 + +You may wish to remove the target overrides after the defaults switch. +Alternatively, you can keep them
[gentoo-commits] data/gentoo-news:master commit in: 2023-01-28-rap-prefix-sysroot/
commit: 4cb5a1b2d4e8140f331bb5fa1bb2136db9c4bd54
Author: James Le Cuirot gentoo org>
AuthorDate: Sat Mar 25 22:45:04 2023 +
Commit: James Le Cuirot gentoo org>
CommitDate: Sat Mar 25 22:45:04 2023 +
URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=4cb5a1b2
2023-01-28-rap-prefix-sysroot: Add step to update binutils
Signed-off-by: James Le Cuirot gentoo.org>
.../2023-01-28-rap-prefix-sysroot.en.txt | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt
b/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt
index da1f59b..9c6f3d4 100644
--- a/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt
+++ b/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt
@@ -1,7 +1,7 @@
Title: Breaking changes to the RAP Prefix toolchain
Author: James Le Cuirot
Posted: 2023-01-28
-Revision: 2
+Revision: 3
News-Item-Format: 2.0
Display-If-Profile: default/linux/amd64/17.0/no-multilib/prefix/*
Display-If-Profile: default/linux/amd64/17.1/no-multilib/prefix/*
@@ -53,12 +53,15 @@ your toolchain will break when you next update your
compiler or glibc.
3. Update or rebuild sys-libs/glibc.
- 4. Run the following to remove the symlink:
+ 4. Update sys-devel/binutils to at least 2.40-r2. This package is slotted, so
+ ensure at least this version is selected with binutils-config.
+
+ 5. Run the following to remove the symlink:
EPREFIX=$(portageq envvar EPREFIX)
rm "${EPREFIX}${EPREFIX}"
- 5. If dev-libs/libbsd is installed, then update it to 0.11.7-r2 or later.
+ 6. If dev-libs/libbsd is installed, then update it to 0.11.7-r2 or later.
If you are reading this having updated glibc first and you are no longer able
to
build anything, then don't panic. Simply execute the lines below and then carry
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-01-systemd-usrmerge/
commit: af0db5eca18febcc06540d230c960a5e6ed127a3 Author: Sam James gentoo org> AuthorDate: Mon Feb 6 15:50:33 2023 + Commit: Sam James gentoo org> CommitDate: Mon Feb 6 15:50:33 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=af0db5ec 2022-12-01-systemd-usrmerge: suggest system be up to date first This makes life a lot easier with debugging potential issues. Signed-off-by: Sam James gentoo.org> 2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt index be1870c..c851d3c 100644 --- a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt +++ b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt @@ -18,7 +18,8 @@ script is available to perform the actual migration. To migrate a system to merged-usr, follow this procedure: -1. Ensure your system backups are up to date. +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. 2. Install sys-apps/merge-usr.
[gentoo-commits] data/gentoo-news:master commit in: 2023-01-28-rap-prefix-sysroot/
commit: 08c95ae436163d5da31b9d3340071d8666efa08b Author: James Le Cuirot gentoo org> AuthorDate: Wed Feb 1 23:48:31 2023 + Commit: James Le Cuirot gentoo org> CommitDate: Wed Feb 1 23:48:31 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=08c95ae4 2023-01-28-rap-prefix-sysroot: Clarify paragraph about checking USE flag Signed-off-by: James Le Cuirot gentoo.org> 2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt b/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt index 205250b..da1f59b 100644 --- a/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt +++ b/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt @@ -1,7 +1,7 @@ Title: Breaking changes to the RAP Prefix toolchain Author: James Le Cuirot Posted: 2023-01-28 -Revision: 1 +Revision: 2 News-Item-Format: 2.0 Display-If-Profile: default/linux/amd64/17.0/no-multilib/prefix/* Display-If-Profile: default/linux/amd64/17.1/no-multilib/prefix/* @@ -28,7 +28,8 @@ If you using a non-RAP "Prefix Guest" or "Prefix Stack" variant (e.g. macOS) then this does not apply. If you're not sure what kind of prefix you have, then check whether the -prefix-guest USE flag is enabled. +prefix-guest USE flag is enabled. If the following command returns nothing, then +you have a RAP prefix and this does apply. portageq envvar USE | grep prefix-guest
[gentoo-commits] data/gentoo-news:master commit in: 2023-01-28-rap-prefix-sysroot/
commit: 3adad1954b1463ddfe5c9f7d39e308d6b57b2769
Author: James Le Cuirot gentoo org>
AuthorDate: Sat Jan 28 22:10:13 2023 +
Commit: James Le Cuirot gentoo org>
CommitDate: Sat Jan 28 22:10:32 2023 +
URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=3adad195
2023-01-28-rap-prefix-sysroot: Add news item
Signed-off-by: James Le Cuirot gentoo.org>
.../2023-01-28-rap-prefix-sysroot.en.txt | 67 ++
1 file changed, 67 insertions(+)
diff --git a/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt
b/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt
new file mode 100644
index 000..205250b
--- /dev/null
+++ b/2023-01-28-rap-prefix-sysroot/2023-01-28-rap-prefix-sysroot.en.txt
@@ -0,0 +1,67 @@
+Title: Breaking changes to the RAP Prefix toolchain
+Author: James Le Cuirot
+Posted: 2023-01-28
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Profile: default/linux/amd64/17.0/no-multilib/prefix/*
+Display-If-Profile: default/linux/amd64/17.1/no-multilib/prefix/*
+Display-If-Profile: default/linux/amd64/23.0/no-multilib/prefix/*
+Display-If-Profile: default/linux/amd64/23.0/split-usr/no-multilib/prefix/*
+Display-If-Profile: default/linux/arm/17.0/armv7a/prefix/*
+Display-If-Profile: default/linux/arm/23.0/armv7a/prefix/*
+Display-If-Profile: default/linux/arm/23.0/split-usr/armv7a/prefix/*
+Display-If-Profile: default/linux/arm64/17.0/prefix/*
+Display-If-Profile: default/linux/arm64/23.0/prefix/*
+Display-If-Profile: default/linux/arm64/23.0/split-usr/prefix/*
+Display-If-Profile: default/linux/ppc64le/17.0/prefix/*
+Display-If-Profile: default/linux/riscv/20.0/rv64gc/lp64d/prefix/*
+Display-If-Profile: default/linux/riscv/23.0/rv64/lp64d/prefix/*
+Display-If-Profile: default/linux/riscv/23.0/rv64/split-usr/lp64d/prefix/*
+Display-If-Profile: default/linux/x86/17.0/prefix/*
+Display-If-Profile: default/linux/x86/23.0/prefix/*
+Display-If-Profile: default/linux/x86/23.0/split-usr/prefix/*
+
+We are changing the way the toolchain operates on RAP Prefix systems in order
to
+reduce the number of hacks we need to apply and make cross-compiling easier.
+
+If you using a non-RAP "Prefix Guest" or "Prefix Stack" variant (e.g. macOS)
+then this does not apply.
+
+If you're not sure what kind of prefix you have, then check whether the
+prefix-guest USE flag is enabled.
+
+ portageq envvar USE | grep prefix-guest
+
+If you are using a libc other than glibc (e.g. musl) then this *does* apply,
but
+your libc will *not* break, so you should not carry out the following
procedure.
+The only other package known to be affected is dev-libs/libbsd, which you can
+simply update. If you find another package affected by this, then please file a
+bug report.
+
+WARNING! It is important that you carry out the following procedure, otherwise
+your toolchain will break when you next update your compiler or glibc.
+
+ 1. Run the following to create a temporary symlink:
+
+ EPREFIX=$(portageq envvar EPREFIX)
+ mkdir -p "${EPREFIX}${EPREFIX%/*}"
+ ln -sn "${EPREFIX}" "${EPREFIX}${EPREFIX}"
+
+ 2. Update or rebuild all installed slots of sys-devel/gcc and sys-devel/clang
+ (if any). Feel free to remove any you no longer need.
+
+ 3. Update or rebuild sys-libs/glibc.
+
+ 4. Run the following to remove the symlink:
+
+ EPREFIX=$(portageq envvar EPREFIX)
+ rm "${EPREFIX}${EPREFIX}"
+
+ 5. If dev-libs/libbsd is installed, then update it to 0.11.7-r2 or later.
+
+If you are reading this having updated glibc first and you are no longer able
to
+build anything, then don't panic. Simply execute the lines below and then carry
+out the regular procedure above.
+
+ EPREFIX=$(portageq envvar EPREFIX)
+ portageq contents "${EPREFIX}" $(portageq best_version "${EPREFIX}"
sys-libs/glibc) | xargs grep -lIF -d skip "GNU ld script" | xargs sed -i -r "s:
/(usr|lib): ${EPREFIX}/\1:g"
[gentoo-commits] data/gentoo-news:master commit in: 2023-01-01-hardening-fortify-assertions/
commit: a49aa1b25808f0e08157406a45560e3b7efba275 Author: Sam James gentoo org> AuthorDate: Sat Jan 14 23:05:23 2023 + Commit: Sam James gentoo org> CommitDate: Sat Jan 14 23:05:23 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=a49aa1b2 2023-01-01-hardening-fortify-assertions: add missing hardened (SELinux) profiles Thanks-to: Oskari Pirhonen gmail.com> Signed-off-by: Sam James gentoo.org> .../2023-01-01-hardening-fortify-assertions.en.txt | 26 ++ 1 file changed, 17 insertions(+), 9 deletions(-) diff --git a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt index f0aab21..847e968 100644 --- a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt +++ b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt @@ -5,21 +5,29 @@ Revision: 2 News-Item-Format: 2.0 Display-If-Installed: sys-devel/gcc[hardened] Display-If-Profile: features/hardened -Display-If-Profile: default/linux/ppc64le/17.0/musl/hardened -Display-If-Profile: default/linux/ppc/17.0/musl/hardened -Display-If-Profile: default/linux/amd64/17.0/no-multilib/hardened -Display-If-Profile: default/linux/amd64/17.0/hardened Display-If-Profile: default/linux/amd64/17.0/musl/hardened +Display-If-Profile: default/linux/amd64/17.0/musl/hardened/selinux Display-If-Profile: default/linux/amd64/17.1/hardened +Display-If-Profile: default/linux/amd64/17.1/hardened/selinux Display-If-Profile: default/linux/amd64/17.1/no-multilib/hardened -Display-If-Profile: default/linux/x86/17.0/hardened -Display-If-Profile: default/linux/arm/17.0/musl/armv7a/hardened -Display-If-Profile: default/linux/arm/17.0/musl/armv6j/hardened -Display-If-Profile: default/linux/arm/17.0/armv7a/hardened +Display-If-Profile: default/linux/amd64/17.1/no-multilib/hardened/selinux Display-If-Profile: default/linux/arm/17.0/armv6j/hardened -Display-If-Profile: default/linux/ppc64/17.0/musl/hardened +Display-If-Profile: default/linux/arm/17.0/armv7a/hardened +Display-If-Profile: default/linux/arm/17.0/armv7a/hardened/selinux +Display-If-Profile: default/linux/arm/17.0/armv7a/hardened/selinux +Display-If-Profile: default/linux/arm/17.0/musl/armv6j/hardened +Display-If-Profile: default/linux/arm/17.0/musl/armv6j/hardened/selinux +Display-If-Profile: default/linux/arm/17.0/musl/armv7a/hardened +Display-If-Profile: default/linux/arm/17.0/musl/armv7a/hardened/selinux Display-If-Profile: default/linux/arm64/17.0/hardened +Display-If-Profile: default/linux/arm64/17.0/hardened/selinux Display-If-Profile: default/linux/arm64/17.0/musl/hardened +Display-If-Profile: default/linux/arm64/17.0/musl/hardened/selinux +Display-If-Profile: default/linux/ppc/17.0/musl/hardened +Display-If-Profile: default/linux/ppc64/17.0/musl/hardened +Display-If-Profile: default/linux/ppc64le/17.0/musl/hardened +Display-If-Profile: default/linux/x86/17.0/hardened +Display-If-Profile: default/linux/x86/17.0/hardened/selinux Gentoo's hardened profiles are adopting two new modern toolchain hardening techniques:
[gentoo-commits] data/gentoo-news:master commit in: 2023-01-01-hardening-fortify-assertions/
commit: 6b8c798b7b8b2b2ea9cb833842c733c494ad0df2 Author: Sam James gentoo org> AuthorDate: Sun Jan 1 22:10:25 2023 + Commit: Sam James gentoo org> CommitDate: Sun Jan 1 22:10:25 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=6b8c798b 2023-01-01-hardening-fortify-assertions: add Display-If-Installed: sys-devel/gcc[hardened] Signed-off-by: Sam James gentoo.org> .../2023-01-01-hardening-fortify-assertions.en.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt index ea3ac1b..f0aab21 100644 --- a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt +++ b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt @@ -1,8 +1,9 @@ Title: Hardened profiles improvements Author: Sam James Posted: 2023-01-01 -Revision: 1 +Revision: 2 News-Item-Format: 2.0 +Display-If-Installed: sys-devel/gcc[hardened] Display-If-Profile: features/hardened Display-If-Profile: default/linux/ppc64le/17.0/musl/hardened Display-If-Profile: default/linux/ppc/17.0/musl/hardened
[gentoo-commits] data/gentoo-news:master commit in: 2023-01-01-hardening-fortify-assertions/
commit: 5f74f9d9698950a8204c22eddac11eb4654d260e Author: Sam James gentoo org> AuthorDate: Sun Jan 1 22:09:28 2023 + Commit: Sam James gentoo org> CommitDate: Sun Jan 1 22:09:28 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=5f74f9d9 2023-01-01-hardening-fortify-assertions: mention 'gcc-config latest' Signed-off-by: Sam James gentoo.org> .../2023-01-01-hardening-fortify-assertions.en.txt | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt index 3b2ff02..ea3ac1b 100644 --- a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt +++ b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt @@ -39,9 +39,10 @@ of these improvements early, before GCC 12 is marked stable. To fully take advantage of these new settings, GCC must first be upgraded, and then all packages must be re-emerged: -1. emerge --sync -2. emerge --verbose --oneshot ">=sys-devel/gcc-12.2.1_p20221231" -3. emerge --verbose --emptytree @world +1. # emerge --sync +2. # emerge --verbose --oneshot ">=sys-devel/gcc-12.2.1_p20221231" +3. # gcc-config latest +4. # emerge --verbose --emptytree @world ## Troubleshooting
[gentoo-commits] data/gentoo-news:master commit in: 2023-01-01-hardening-fortify-assertions/
commit: 55ff6471ce55a668602922eb922642d0a405b020 Author: Sam James gentoo org> AuthorDate: Sun Jan 1 21:40:20 2023 + Commit: Sam James gentoo org> CommitDate: Sun Jan 1 21:40:20 2023 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=55ff6471 2023-01-01-hardening-fortify-assertions: update GCC version Signed-off-by: Sam James gentoo.org> .../2023-01-01-hardening-fortify-assertions.en.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt index dfe9127..3b2ff02 100644 --- a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt +++ b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt @@ -26,12 +26,12 @@ techniques: 2. libstdc++ assertions (-D_GLIBCXX_ASSERTIONS) [1] These will both be enabled by default with USE=hardened on sys-devel/gcc -for >=sys-devel/gcc-12.2.1_p20221224-r1. +for >=sys-devel/gcc-12.2.1_p20221231. To view the existing list of hardening changes applied by the profiles, see the wiki [2]. -Stable users may wish to add sys-devel/gcc-12.2.1_p20221224-r1 into +Stable users may wish to add sys-devel/gcc-12.2.1_p20221231 into /etc/portage/package.accept_keywords if they wish to take advantage of these improvements early, before GCC 12 is marked stable. @@ -40,7 +40,7 @@ of these improvements early, before GCC 12 is marked stable. To fully take advantage of these new settings, GCC must first be upgraded, and then all packages must be re-emerged: 1. emerge --sync -2. emerge --verbose --oneshot ">=sys-devel/gcc-12.2.1_p20221224-r1" +2. emerge --verbose --oneshot ">=sys-devel/gcc-12.2.1_p20221231" 3. emerge --verbose --emptytree @world ## Troubleshooting
[gentoo-commits] data/gentoo-news:master commit in: 2023-01-01-hardening-fortify-assertions/
commit: 469c078b8ada3bc00da386bd2eaa2dc3410e3323
Author: Sam James gentoo org>
AuthorDate: Wed Dec 28 19:33:34 2022 +
Commit: Sam James gentoo org>
CommitDate: Sun Jan 1 21:16:42 2023 +
URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=469c078b
2023-01-01-hardening-fortify-assertions: add item
Bug: https://bugs.gentoo.org/876893
Bug: https://bugs.gentoo.org/876895
Signed-off-by: Sam James gentoo.org>
.../2023-01-01-hardening-fortify-assertions.en.txt | 57 ++
1 file changed, 57 insertions(+)
diff --git
a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt
b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt
new file mode 100644
index 000..dfe9127
--- /dev/null
+++
b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt
@@ -0,0 +1,57 @@
+Title: Hardened profiles improvements
+Author: Sam James
+Posted: 2023-01-01
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Profile: features/hardened
+Display-If-Profile: default/linux/ppc64le/17.0/musl/hardened
+Display-If-Profile: default/linux/ppc/17.0/musl/hardened
+Display-If-Profile: default/linux/amd64/17.0/no-multilib/hardened
+Display-If-Profile: default/linux/amd64/17.0/hardened
+Display-If-Profile: default/linux/amd64/17.0/musl/hardened
+Display-If-Profile: default/linux/amd64/17.1/hardened
+Display-If-Profile: default/linux/amd64/17.1/no-multilib/hardened
+Display-If-Profile: default/linux/x86/17.0/hardened
+Display-If-Profile: default/linux/arm/17.0/musl/armv7a/hardened
+Display-If-Profile: default/linux/arm/17.0/musl/armv6j/hardened
+Display-If-Profile: default/linux/arm/17.0/armv7a/hardened
+Display-If-Profile: default/linux/arm/17.0/armv6j/hardened
+Display-If-Profile: default/linux/ppc64/17.0/musl/hardened
+Display-If-Profile: default/linux/arm64/17.0/hardened
+Display-If-Profile: default/linux/arm64/17.0/musl/hardened
+
+Gentoo's hardened profiles are adopting two new modern toolchain hardening
+techniques:
+1. Level 3 fortification (-D_FORTIFY_SOURCE=3) [0]
+2. libstdc++ assertions (-D_GLIBCXX_ASSERTIONS) [1]
+
+These will both be enabled by default with USE=hardened on sys-devel/gcc
+for >=sys-devel/gcc-12.2.1_p20221224-r1.
+
+To view the existing list of hardening changes applied by the profiles,
+see the wiki [2].
+
+Stable users may wish to add sys-devel/gcc-12.2.1_p20221224-r1 into
+/etc/portage/package.accept_keywords if they wish to take advantage
+of these improvements early, before GCC 12 is marked stable.
+
+## Migration
+
+To fully take advantage of these new settings, GCC must first
+be upgraded, and then all packages must be re-emerged:
+1. emerge --sync
+2. emerge --verbose --oneshot ">=sys-devel/gcc-12.2.1_p20221224-r1"
+3. emerge --verbose --emptytree @world
+
+## Troubleshooting
+
+In the event that some packages fail at runtime, please file a bug
+with the full details. To temporarily workaround the problem,
+it should be possible to recompile broken packages with the
+following *FLAGS:
+CFLAGS="${CFLAGS} -D_FORTIFY_SOURCE=2"
+CXXFLAGS="${CXXFLAGS} -D_FORTIFY_SOURCE=2 -U_GLIBCXX_ASSERTIONS"
+
+[0] https://bugs.gentoo.org/876893
+[1] https://bugs.gentoo.org/876895
+[2] https://wiki.gentoo.org/wiki/Hardened/Toolchain#Changes
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-27-alternatives-introduction/
commit: 577cef52c20b850057e0ab863cc7b38b14e6e6c2 Author: Sam James gentoo org> AuthorDate: Fri Dec 30 06:47:50 2022 + Commit: Sam James gentoo org> CommitDate: Fri Dec 30 06:48:11 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=577cef52 2022-12-27-alternatives-introduction: note it's ok if nothing to depclean Signed-off-by: Sam James gentoo.org> .../2022-12-27-alternatives-introduction.en.txt| 3 +++ 1 file changed, 3 insertions(+) diff --git a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt index 924413d..38a31fb 100644 --- a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt +++ b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt @@ -66,6 +66,9 @@ deselecting eselect-awk and eselect-sh: 2. # emerge --depclean app-eselect/eselect-awk app-eselect/eselect-sh 3. # emerge --sync 4. # emerge -a -uvDU @world (or other similar standard world upgrade command) +5. # emerge --ask --depclean + +It's okay if nothing happens in Step 1 and Step 2 (no atoms to remove). ## Configuration
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-27-alternatives-introduction/
commit: 01cbad32e507e44c39713810c40d5bdbbd5214c0 Author: Sam James gentoo org> AuthorDate: Fri Dec 30 06:40:19 2022 + Commit: Sam James gentoo org> CommitDate: Fri Dec 30 06:40:34 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=01cbad32 2022-12-27-alternatives-introduction: explicitly state update now... Signed-off-by: Sam James gentoo.org> .../2022-12-27-alternatives-introduction.en.txt| 3 +++ 1 file changed, 3 insertions(+) diff --git a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt index 021bf53..924413d 100644 --- a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt +++ b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt @@ -57,6 +57,9 @@ orphaned files where no package owns the file. ## Migrating +When receiving this news item, please follow the step below as soon +as possible to ensure a smooth transition. + To migrate your system, a standard world upgrade will suffice after deselecting eselect-awk and eselect-sh: 1. # emerge --deselect app-eselect/eselect-awk app-eselect/eselect-sh
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-27-alternatives-introduction/
commit: 3abe780d4ba69135d9df7889532e440b40cd54c0 Author: Sam James gentoo org> AuthorDate: Fri Dec 30 06:38:36 2022 + Commit: Sam James gentoo org> CommitDate: Fri Dec 30 06:39:00 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=3abe780d 2022-12-27-alternatives-introduction: note that stabliization is complete Signed-off-by: Sam James gentoo.org> .../2022-12-27-alternatives-introduction.en.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt index cb0b0ed..021bf53 100644 --- a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt +++ b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt @@ -30,7 +30,7 @@ The initial list of packages which support alternatives is as follows: - app-alternatives/yacc The stabilization of these new ebuilds and packages depending -on them is ongoing in bug 886017 [1]. +on them occurred on 2022-12-27 in bug 886017 [1]. ## Pre-upgrade requirements
[gentoo-commits] data/gentoo-news:master commit in: 2017-11-21-old-wine-versions-moving-to-overlay/
commit: 68558668b132039a1b6fd4e6f5b4a1c8b58e8182 Author: Nick Sarnie gentoo org> AuthorDate: Fri Dec 30 02:57:44 2022 + Commit: Nick Sarnie gentoo org> CommitDate: Fri Dec 30 02:57:44 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=68558668 2017-11-21-old-wine-versions-moving-to-overlay: Remove Signed-off-by: Nick Sarnie gentoo.org> ...1-21-old-wine-versions-moving-to-overlay.en.txt | 37 -- 1 file changed, 37 deletions(-) diff --git a/2017-11-21-old-wine-versions-moving-to-overlay/2017-11-21-old-wine-versions-moving-to-overlay.en.txt b/2017-11-21-old-wine-versions-moving-to-overlay/2017-11-21-old-wine-versions-moving-to-overlay.en.txt deleted file mode 100644 index ff28b96..000 --- a/2017-11-21-old-wine-versions-moving-to-overlay/2017-11-21-old-wine-versions-moving-to-overlay.en.txt +++ /dev/null @@ -1,37 +0,0 @@ -Title: Old Wine versions moving to wine-overlay -Author: NP-Hardass -Posted: 2017-11-21 -Revision: 1 -News-Item-Format: 2.0 -Display-If-Installed: app-emulation/wine:0 -Display-If-Installed: app-emulation/wine-vanilla -Display-If-Installed: app-emulation/wine-staging -Display-If-Installed: app-emulation/wine-d3d9 -Display-If-Installed: app-emulation/wine-any - -To reduce the burden on main Gentoo repository, older versions of Wine -will be available only in the wine overlay. These ebuilds will still be -fully supported by the Gentoo Wine Project. This will result in -upstream stable releases and the several most recent upstream devel -releases being the only versions in ::gentoo; all versions meeting the -criteria for support within Gentoo [1] will be available in ::wine. - -To install the overlay you can either add the repos.conf file to your -portage configuration directory, add the repository via layman, or add the -repository via eselect-repository. - -* To add the repos.conf file: -# wget https://dev.gentoo.org/~np-hardass/proj/wine/wine.conf -O \ -/etc/portage/repos.conf/wine.conf - -Edit the /etc/portage/repos.conf/wine.conf file so that "location" -points to your desired folder to install the overlay. -# emaint sync --repo wine - -* To install the overlay via layman: -# layman -a wine - -* To install the overlay via eselect-repository: -# eselect repository enable wine - -[1] https://wiki.gentoo.org/wiki/Project:Wine/Policies_and_Procedures#Supported_versions
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-27-alternatives-introduction/
commit: 1d5fe72fedb4ff8359b6926e8e6a69d7f4c34c8e Author: Sam James gentoo org> AuthorDate: Thu Dec 29 23:40:24 2022 + Commit: Sam James gentoo org> CommitDate: Thu Dec 29 23:40:47 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=1d5fe72f 2022-12-27-alternatives-introduction: fix Posted date Signed-off-by: Sam James gentoo.org> .../2022-12-27-alternatives-introduction.en.txt | 2 +- .../2022-12-27-alternatives-introduction.ru.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt index 0fb8785..cb0b0ed 100644 --- a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt +++ b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt @@ -1,6 +1,6 @@ Title: Introduction of app-alternatives ebuilds Author: Sam James -Posted: 2022-12-24 +Posted: 2022-12-27 Revision: 1 News-Item-Format: 2.0 diff --git a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt index 25a989f..6bf10ac 100644 --- a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt +++ b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt @@ -1,7 +1,7 @@ Title: Нововведение: пакеты app-alternatives Author: Sam James Translator: Alexey Sokolov -Posted: 2022-12-24 +Posted: 2022-12-27 Revision: 1 News-Item-Format: 2.0
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-27-alternatives-introduction/
commit: 438d35b13f626ee69e26033c5f9cf829429fecc4 Author: Sam James gentoo org> AuthorDate: Wed Dec 28 16:17:33 2022 + Commit: Sam James gentoo org> CommitDate: Wed Dec 28 16:17:33 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=438d35b1 2022-12-27-alternatives-introduction: mention /bin/gzip instead of /usr/bin/gzip Prompted by comment at https://wiki.gentoo.org/wiki/Talk:Gzip wrt split-usr systems. Signed-off-by: Sam James gentoo.org> .../2022-12-27-alternatives-introduction.en.txt | 4 ++-- .../2022-12-27-alternatives-introduction.ru.txt | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt index 0f56518..0fb8785 100644 --- a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt +++ b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt @@ -78,11 +78,11 @@ Going forward, /etc/portage/package.use will be used for this purpose. Users should review the USE flags available for the various app-alternatives ebuilds like app-alternatives/sh and adjust their configuration as desired. -For example, to have /usr/bin/gzip be provided by app-arch/pigz for automatic +For example, to have /bin/gzip be provided by app-arch/pigz for automatic parallelization of 'gzip', one would have the following in /etc/portage/package.use: ``` # https://wiki.gentoo.org/wiki/Gzip#Parallelization -# Make /usr/bin/gzip be a symlink to pigz for a speedup in compression +# Make /bin/gzip be a symlink to pigz for a speedup in compression app-alternatives/gzip -reference pigz ``` diff --git a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt index ec3999a..25a989f 100644 --- a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt +++ b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt @@ -82,11 +82,11 @@ FEATURES="-collision-protect". collision-protect находит конфликт app-alternatives, таких как app-alternatives/sh, и настройте их на ваше усмотрение. -Например, чтобы /usr/bin/gzip был предоставлен пакетом app-arch/pigz, это +Например, чтобы /bin/gzip был предоставлен пакетом app-arch/pigz, это автоматически параллелизует gzip, нужен такой текст в /etc/portage/package.use: ``` # https://wiki.gentoo.org/wiki/Gzip#Parallelization -# Пусть /usr/bin/gzip будет ссылкой на pigz для ускорения сжатия +# Пусть /bin/gzip будет ссылкой на pigz для ускорения сжатия app-alternatives/gzip -reference pigz ```
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-27-alternatives-introduction/
commit: 8eb95c2d84d4f678763c1f7bd59fbea84dbaad3d Author: Sam James gentoo org> AuthorDate: Wed Dec 28 16:08:44 2022 + Commit: Sam James gentoo org> CommitDate: Wed Dec 28 16:08:44 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=8eb95c2d 2022-12-27-alternatives-introduction: fix typo Thanks to kurly. Signed-off-by: Sam James gentoo.org> .../2022-12-27-alternatives-introduction.en.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt index b9c9f59..0f56518 100644 --- a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt +++ b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt @@ -32,7 +32,7 @@ The initial list of packages which support alternatives is as follows: The stabilization of these new ebuilds and packages depending on them is ongoing in bug 886017 [1]. -## Per-upgrade requirements +## Pre-upgrade requirements The default configuration on Gentoo systems is FEATURES="protect-owned" which works similarly to FEATURES="collision-protect" but it allows
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-27-alternatives-introduction/
commit: 57fad3e0aa195ea1011f1bbce59d79e7a52ee474
Author: Sam James gentoo org>
AuthorDate: Wed Dec 28 16:08:24 2022 +
Commit: Sam James gentoo org>
CommitDate: Wed Dec 28 16:08:24 2022 +
URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=57fad3e0
2022-12-27-alternatives-introduction: mention depcleaning eselect-{sh,awk}
Needed because of hard blockers.
Signed-off-by: Sam James gentoo.org>
.../2022-12-27-alternatives-introduction.en.txt | 5 +++--
.../2022-12-27-alternatives-introduction.ru.txt | 5 +++--
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git
a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt
b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt
index 601142f..b9c9f59 100644
---
a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt
+++
b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt
@@ -60,8 +60,9 @@ orphaned files where no package owns the file.
To migrate your system, a standard world upgrade will suffice after
deselecting eselect-awk and eselect-sh:
1. # emerge --deselect app-eselect/eselect-awk app-eselect/eselect-sh
-2. # emerge --sync
-3. # emerge -a -uvDU @world (or other similar standard world upgrade command)
+2. # emerge --depclean app-eselect/eselect-awk app-eselect/eselect-sh
+3. # emerge --sync
+4. # emerge -a -uvDU @world (or other similar standard world upgrade command)
## Configuration
diff --git
a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt
b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt
index 254bb40..ec3999a 100644
---
a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt
+++
b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt
@@ -62,8 +62,9 @@ FEATURES="-collision-protect". collision-protect находит
конфликт
Для миграции достаточно убрать eselect-awk и eselect-sh из world, и обновить
систему как обычно:
1. # emerge --deselect app-eselect/eselect-awk app-eselect/eselect-sh
-2. # emerge --sync
-3. # emerge -a -uvDU @world (или похожая команда для стандартного обновления
+2. # emerge --depclean app-eselect/eselect-awk app-eselect/eselect-sh
+3. # emerge --sync
+4. # emerge -a -uvDU @world (или похожая команда для стандартного обновления
системы)
## Конфигурация
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-27-alternatives-introduction/
commit: e9411435f572e21fb37e58f9560ae1f733d36f8b Author: Alexey Sokolov asokolov org> AuthorDate: Tue Dec 27 12:51:25 2022 + Commit: Sam James gentoo org> CommitDate: Wed Dec 28 00:49:37 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=e9411435 2022-12-27-alternatives-introduction: add Ru translation Signed-off-by: Alexey Sokolov asokolov.org> Signed-off-by: Sam James gentoo.org> .../2022-12-27-alternatives-introduction.ru.txt| 98 ++ 1 file changed, 98 insertions(+) diff --git a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt new file mode 100644 index 000..254bb40 --- /dev/null +++ b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.ru.txt @@ -0,0 +1,98 @@ +Title: Нововведение: пакеты app-alternatives +Author: Sam James +Translator: Alexey Sokolov +Posted: 2022-12-24 +Revision: 1 +News-Item-Format: 2.0 + +В Gentoo будет новая категория пакетов под названием «app-alternatives» для +случаев, когда пользователь хочет поменять символическую ссылку, указывающую +на распространённую программу, доступную в разных пакетах. + +По традиции, для этого использовался eselect, но, хотя eselect всё ещё бывает +нужен, он плохо подходит для случаев, таких как /bin/awk и /bin/sh, потому что +а) он предотвращает использование корневой файловой системы в режиме только +для чтения, б) что более важно с точки зрения системы управления пакетами, он +зависит от осиротевших символических ссылок: ни один пакет не владеет файлами +/bin/awk, /bin/sh и т. д. Это не надёжно, и в некоторых случаях может привести +к мёртвой ссылке или даже к отсутствию ссылки [0]. + +При использовании для этих целей пакетного менеджера вместо ручной +конфигурации вовне система станет более надёжной. + +Начальный список пакетов с поддержкой альтернатив такой: +- app-alternatives/awk +- app-alternatives/bzip2 +- app-alternatives/bc +- app-alternatives/cpio +- app-alternatives/gzip +- app-alternatives/lex +- app-alternatives/sh +- app-alternatives/tar +- app-alternatives/yacc + +Стабилизация этих пакетов, а также пакетов, от них зависящих, происходит в +баге 886017 [1]. + +## Требования для обновления + +Настройка по умолчанию для систем Gentoo выглядит так: +FEATURES="protect-owned"; это работает подобно FEATURES="collision-protect", +но позволяет конфликты между файлами-сиротами. В этом случае возникнет +одноразовый конфликт, когда пакет из app-alternatives/ присвоит себе +символическую ссылку, которая до этого не принадлежала ни одному пакету. + +Похожая ситуация была при миграции на libxcrypt, когда обновления ломались у +пользователей при использовании старой, более агрессивной настройки +FEATURES="collision-protect". + +Мы рекомендуем вам обновить свою конфигурацию, и убрать «collision-protect» из +FEATURES. Вместо этого можете явно включить «protect-owned» или не указывать +там ничего, потому что это итак настройка по умолчанию. Также можно выключить +«collision-protect» временно, только для этого обновления, и затем включить +обратно. + +ВНИМАНИЕ: Пользователи, использующие collision-protect, должны убрать его из +FEATURES в /etc/portage/make.conf, либо установить +FEATURES="-collision-protect". collision-protect находит конфликты между +файлами, даже когда ни один пакет не владеет файлом. + +## Миграция + +Для миграции достаточно убрать eselect-awk и eselect-sh из world, и обновить +систему как обычно: +1. # emerge --deselect app-eselect/eselect-awk app-eselect/eselect-sh +2. # emerge --sync +3. # emerge -a -uvDU @world (или похожая команда для стандартного обновления +системы) + +## Конфигурация + +Если вы не заинтересованны в использовании разных реализаций перечисленных +выше инструментов, эту секцию можно пропустить. + +По умолчанию никакая конфигурация не требуется, но вы можете настраивать +поведение пакетов из app-alternatives/, как раньше использовали для этого, +например, eselect-sh и eselect-awk. + +Теперь для этого будет использоваться /etc/portage/package.use. + +Пожалуйста, просмотрите USE-флаги, доступные для различных пакетов из +app-alternatives, таких как app-alternatives/sh, и настройте их на ваше +усмотрение. + +Например, чтобы /usr/bin/gzip был предоставлен пакетом app-arch/pigz, это +автоматически параллелизует gzip, нужен такой текст в /etc/portage/package.use: +``` +# https://wiki.gentoo.org/wiki/Gzip#Parallelization +# Пусть /usr/bin/gzip будет ссылкой на pigz для ускорения сжатия +app-alternatives/gzip -reference pigz +``` + +## Дополнительные материалы + +Больше технических подробностей описано в вики [2]. + +[0] https://wiki.gentoo.org/wiki/Project:Base/Alternatives#Why.3F +[1] https://bugs.gentoo.org/886017 +[2] https://wiki.gentoo.org/wiki/Project:Base/Alternatives
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-27-alternatives-introduction/
commit: efcbc0f5a17ac5eb27f459b7634ad8794904e6c6 Author: Sam James gentoo org> AuthorDate: Sat Dec 24 05:08:21 2022 + Commit: Sam James gentoo org> CommitDate: Tue Dec 27 10:48:09 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=efcbc0f5 2022-12-27-alternatives-introduction: add news item Bug: https://bugs.gentoo.org/886247 Bug: https://bugs.gentoo.org/886017 Signed-off-by: Sam James gentoo.org> .../2022-12-27-alternatives-introduction.en.txt| 94 ++ 1 file changed, 94 insertions(+) diff --git a/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt new file mode 100644 index 000..601142f --- /dev/null +++ b/2022-12-27-alternatives-introduction/2022-12-27-alternatives-introduction.en.txt @@ -0,0 +1,94 @@ +Title: Introduction of app-alternatives ebuilds +Author: Sam James +Posted: 2022-12-24 +Revision: 1 +News-Item-Format: 2.0 + +Gentoo is introducing a new category of ebuilds called 'app-alternatives' +to handle cases where a symlink for a common binary may want to be switched +between different packages by a user. + +Traditionally, eselect was used for this, and while eselect still has its +place, it's unsuitable for cases like /bin/awk and /bin/sh because it +prevents immutable system directories and (more importantly +from a package management perspective) relies on orphaned symlinks which +means no package owns /bin/awk, /bin/sh, etc. This is not reliable and +can lead to dead symlinks (or no symlink at all) in some edge cases [0]. + +Systems will be more robust and desired system configuration +can be achieved using the package manager rather than manual steps outside of it. + +The initial list of packages which support alternatives is as follows: +- app-alternatives/awk +- app-alternatives/bzip2 +- app-alternatives/bc +- app-alternatives/cpio +- app-alternatives/gzip +- app-alternatives/lex +- app-alternatives/sh +- app-alternatives/tar +- app-alternatives/yacc + +The stabilization of these new ebuilds and packages depending +on them is ongoing in bug 886017 [1]. + +## Per-upgrade requirements + +The default configuration on Gentoo systems is FEATURES="protect-owned" +which works similarly to FEATURES="collision-protect" but it allows +collisions between orphaned files. In this case, a one-off collision +occurs as the app-alternatives/ ebuilds begin to claim once-orphaned +symlinks. + +A similar issue occurred during the libxcrypt migration where users +had upgrades interrupted by using the older, more aggressive +FEATURES="collision-protect". + +It is recommended that users alter their configuration to +remove references to 'collision-protect' in FEATURES and instead either +explicitly enable 'protect-owned' in FEATURES or rely on the default +(equivalent). It is also acceptable to simply disable collision-protect +temporarily for the purposes of this news item. + +WARNING: Users with collision-protect enabled must disable FEATURES="collision-protect" +in /etc/portage/make.conf by removing it or setting FEATURES="-collision-protect" +if they have enabled it. collision-protect detects collisions between files including +orphaned files where no package owns the file. + +## Migrating + +To migrate your system, a standard world upgrade will suffice after +deselecting eselect-awk and eselect-sh: +1. # emerge --deselect app-eselect/eselect-awk app-eselect/eselect-sh +2. # emerge --sync +3. # emerge -a -uvDU @world (or other similar standard world upgrade command) + +## Configuration + +Users who are not interested in using different implementations for +various tools listed above can ignore this section. + +No configuration should be required by default, but users may wish +to configure the new app-alternatives/ ebuilds to their tastes as they +used to do via e.g. eselect-sh and eselect-awk. + +Going forward, /etc/portage/package.use will be used for this purpose. + +Users should review the USE flags available for the various app-alternatives +ebuilds like app-alternatives/sh and adjust their configuration as desired. + +For example, to have /usr/bin/gzip be provided by app-arch/pigz for automatic +parallelization of 'gzip', one would have the following in /etc/portage/package.use: +``` +# https://wiki.gentoo.org/wiki/Gzip#Parallelization +# Make /usr/bin/gzip be a symlink to pigz for a speedup in compression +app-alternatives/gzip -reference pigz +``` + +## Further reading + +For more details, please see the technical documentation on the wiki [2]. + +[0] https://wiki.gentoo.org/wiki/Project:Base/Alternatives#Why.3F +[1] https://bugs.gentoo.org/886017 +[2] https://wiki.gentoo.org/wiki/Project:Base/Alternatives
[gentoo-commits] data/gentoo-news:master commit in: 2022-11-19-lvm2-default-USE-flags/
commit: 6ce13f51e67b46a941ecda627a2d53f999575ee0 Author: Sam James gentoo org> AuthorDate: Tue Dec 20 20:40:17 2022 + Commit: Sam James gentoo org> CommitDate: Tue Dec 20 20:40:17 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=6ce13f51 2022-11-19-lvm2-default-USE-flags: explicitly mention partitions for USE=lvm Prompted by forums discussion at https://forums.gentoo.org/viewtopic-t-1159925.html. Signed-off-by: Sam James gentoo.org> .../2022-11-19-lvm2-default-USE-flags.en.txt | 4 1 file changed, 4 insertions(+) diff --git a/2022-11-19-lvm2-default-USE-flags/2022-11-19-lvm2-default-USE-flags.en.txt b/2022-11-19-lvm2-default-USE-flags/2022-11-19-lvm2-default-USE-flags.en.txt index b3edf5d..9be2830 100644 --- a/2022-11-19-lvm2-default-USE-flags/2022-11-19-lvm2-default-USE-flags.en.txt +++ b/2022-11-19-lvm2-default-USE-flags/2022-11-19-lvm2-default-USE-flags.en.txt @@ -19,6 +19,9 @@ you will lose LVM2 (but not device-mapper!) functionality, so enable it in your config if your boot configuration depends on it or if you depend on any of the lvm2-* daemons. +If you use LVM2 for any partitions, or if you use tools like 'lvchange', you +should enable USE=lvm. + Furthermore, we have considered other default enabled USE flags too, and have come to the conclusion that USE=+thin makes even less sense than USE=+lvm. Thin-provisioned LVM volumes are an important use case in certain VM hosting @@ -26,5 +29,6 @@ scenarios, but unlikely to be relevant for the large majority of Gentoo users. In summary: - Enable USE="lvm" if you use lvm2 (but not needed for device-mapper) as described above. + This includes using LVM for any partitions. - Enable USE="lvm thin" if you use thin as described above. - If you don't know what LVM2 is, you don't need to take any action.
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-01-systemd-usrmerge/
commit: 5d869a12d47362055873f519a82313c6f40fdbdb Author: Mike Gilbert gentoo org> AuthorDate: Thu Dec 8 16:44:33 2022 + Commit: Mike Gilbert gentoo org> CommitDate: Thu Dec 8 16:54:42 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=5d869a12 2022-12-01-systemd-usrmerge: rework steps based on feedback Bug: https://bugs.gentoo.org/884655 Signed-off-by: Mike Gilbert gentoo.org> .../2022-12-01-systemd-usrmerge.en.txt | 17 +++-- 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt index 4bf3e05..be1870c 100644 --- a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt +++ b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt @@ -1,7 +1,7 @@ Title: /usr merge for systemd users Author: Mike Gilbert Posted: 2022-12-01 -Revision: 2 +Revision: 3 News-Item-Format: 2.0 Display-If-Installed: sys-apps/systemd @@ -22,14 +22,19 @@ To migrate a system to merged-usr, follow this procedure: 2. Install sys-apps/merge-usr. -3. Run the merge-usr script in a root shell (not using 'sudo', as a precautionary - measure). The --dryrun option may be used to check for error conditions - before running the script for real. +3. Run "merge-usr --dryrun" as root to check for conflicts. These will + appear with the word ERROR at the start of the line. -4. Switch to a merged-usr profile. +4. Resolve any conflicts. This may involve deleting duplicate files. If + in doubt, seek support in a Gentoo support channel. + +5. Run the merge-usr script from a root shell. Avoid running it via sudo + directly to avoid locking yourself out if an unexpected error occurs. + +6. Switch to a merged-usr profile. eg. eselect profile set default/linux/amd64/17.1/systemd/merged-usr -5. Run emerge with the --newuse or --changed-use option to rebuild +7. Run emerge with the --newuse or --changed-use option to rebuild any packages that have a "split-usr" USE flag. eg. emerge -uDN @world
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-01-systemd-usrmerge/
commit: e6bd58b5ea5c1ba189359ff10b71b9e64005ca42 Author: Sam James gentoo org> AuthorDate: Mon Dec 5 08:42:24 2022 + Commit: Sam James gentoo org> CommitDate: Mon Dec 5 08:42:24 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=e6bd58b5 2022-12-01-systemd-usrmerge: note need to use a root shell We don't want people to use 'sudo' and then possibly somehow get locked out if something goes wrong. Better to use a proper root shell. Signed-off-by: Sam James gentoo.org> 2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt index 87ec4af..4bf3e05 100644 --- a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt +++ b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt @@ -22,8 +22,9 @@ To migrate a system to merged-usr, follow this procedure: 2. Install sys-apps/merge-usr. -3. Run the merge-usr script. The --dryrun option may be used to - check for error conditions before running the script for real. +3. Run the merge-usr script in a root shell (not using 'sudo', as a precautionary + measure). The --dryrun option may be used to check for error conditions + before running the script for real. 4. Switch to a merged-usr profile. eg. eselect profile set default/linux/amd64/17.1/systemd/merged-usr
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-01-systemd-usrmerge/
commit: b333b4666182bd4dbfe37df6d3b8010d39d8fded Author: Mike Gilbert gentoo org> AuthorDate: Thu Dec 1 20:28:45 2022 + Commit: Mike Gilbert gentoo org> CommitDate: Thu Dec 1 20:28:45 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=b333b466 2022-12-01-systemd-usrmerge: add missing colon Signed-off-by: Mike Gilbert gentoo.org> 2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt index 78f2871..87ec4af 100644 --- a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt +++ b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt @@ -1,8 +1,8 @@ Title: /usr merge for systemd users Author: Mike Gilbert Posted: 2022-12-01 -Revision: 1 -News-Item-Format 2.0 +Revision: 2 +News-Item-Format: 2.0 Display-If-Installed: sys-apps/systemd In the latter half of 2023, systemd will drop support for
[gentoo-commits] data/gentoo-news:master commit in: 2022-12-01-systemd-usrmerge/
commit: 9f63c1abfa9f97dc06e21565958c13e58b1b76fb Author: Mike Gilbert gentoo org> AuthorDate: Thu Dec 1 18:07:41 2022 + Commit: Mike Gilbert gentoo org> CommitDate: Thu Dec 1 18:07:41 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=9f63c1ab 2022-12-01-systemd-usrmerge: add news item Signed-off-by: Mike Gilbert gentoo.org> .../2022-12-01-systemd-usrmerge.en.txt | 38 ++ 1 file changed, 38 insertions(+) diff --git a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt new file mode 100644 index 000..78f2871 --- /dev/null +++ b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt @@ -0,0 +1,38 @@ +Title: /usr merge for systemd users +Author: Mike Gilbert +Posted: 2022-12-01 +Revision: 1 +News-Item-Format 2.0 +Display-If-Installed: sys-apps/systemd + +In the latter half of 2023, systemd will drop support for +split-usr/unmerged-usr systems [1]. All Gentoo systems running systemd +will need to be migrated to merged-usr. + +Migrating to merged-usr will move all data from /bin, /sbin, and /lib +into the /usr/bin and /usr/lib directories. The directories in / are +replaced with symlinks. + +To facilitate this, a new set of sub-profiles has been created, and a +script is available to perform the actual migration. + +To migrate a system to merged-usr, follow this procedure: + +1. Ensure your system backups are up to date. + +2. Install sys-apps/merge-usr. + +3. Run the merge-usr script. The --dryrun option may be used to + check for error conditions before running the script for real. + +4. Switch to a merged-usr profile. + eg. eselect profile set default/linux/amd64/17.1/systemd/merged-usr + +5. Run emerge with the --newuse or --changed-use option to rebuild + any packages that have a "split-usr" USE flag. + eg. emerge -uDN @world + +For new installs, new "mergedusr" stage3 tarballs are being produced for +commonly used profiles. + +[1] https://lists.freedesktop.org/archives/systemd-devel/2022-September/048352.html
[gentoo-commits] data/gentoo-news:master commit in: 2022-11-21-tmpfiles-clean/
commit: 2029c60e054511cd64f633c4acba101b781caa83 Author: Mike Gilbert gentoo org> AuthorDate: Mon Nov 21 16:04:58 2022 + Commit: Mike Gilbert gentoo org> CommitDate: Mon Nov 21 16:05:40 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=2029c60e 2022-11-21-tmpfiles-clean: add item Signed-off-by: Mike Gilbert gentoo.org> .../2022-11-21-tmpfiles-clean.en.txt | 16 1 file changed, 16 insertions(+) diff --git a/2022-11-21-tmpfiles-clean/2022-11-21-tmpfiles-clean.en.txt b/2022-11-21-tmpfiles-clean/2022-11-21-tmpfiles-clean.en.txt new file mode 100644 index 000..c4038ea --- /dev/null +++ b/2022-11-21-tmpfiles-clean/2022-11-21-tmpfiles-clean.en.txt @@ -0,0 +1,16 @@ +Title: systemd-tmpfiles --clean enabled by default +Author: Mike Gilbert +Posted: 2022-11-21 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: sys-apps/systemd-utils[tmpfiles] + +Starting with sys-apps/systemd-utils-251.8-r1, a script is installed in +/etc/cron.daily to run "systemd-tmpfiles --clean" once per day. This +will remove stale temp files based on settings specified in tmpfiles.d. + +This change is meant to mimic the behavior of +systemd-tmpfiles-clean.timer from systemd on systems running OpenRC. + +If you wish to opt-out, simply comment out the command in +/etc/cron.daily/systemd-tmpfiles-clean.
[gentoo-commits] data/gentoo-news:master commit in: 2022-11-19-lvm2-default-USE-flags/
commit: 3fb914ae4aeea01e3ab241683ca2bebc3416f50b Author: David Seifert gentoo org> AuthorDate: Sat Nov 19 15:20:03 2022 + Commit: David Seifert gentoo org> CommitDate: Sat Nov 19 15:20:03 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=3fb914ae 2022-11-19-lvm2-default-USE-flags: add item Signed-off-by: David Seifert gentoo.org> .../2022-11-19-lvm2-default-USE-flags.en.txt | 30 ++ 1 file changed, 30 insertions(+) diff --git a/2022-11-19-lvm2-default-USE-flags/2022-11-19-lvm2-default-USE-flags.en.txt b/2022-11-19-lvm2-default-USE-flags/2022-11-19-lvm2-default-USE-flags.en.txt new file mode 100644 index 000..b3edf5d --- /dev/null +++ b/2022-11-19-lvm2-default-USE-flags/2022-11-19-lvm2-default-USE-flags.en.txt @@ -0,0 +1,30 @@ +Title: LVM2 default USE flag change +Author: David Seifert +Posted: 2022-11-19 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: sys-fs/lvm2 + +The Gentoo Base System team has recently switched from the disabling +"device-mapper-only" flag to the enabling "lvm" (bug #718910). + +After considering most reverse dependencies of sys-fs/lvm2, the Base System Team +has decided that the majority of Gentoo users are unlikely to use the LVM2 +components of sys-fs/lvm2, instead relying solely on it providing device-mapper +functionality. + +To this end, we will disable the default enabled flag "+lvm" on sys-fs/lvm2 +on 2023-01-01. If you do not have USE=lvm somehow globally enabled, this means +you will lose LVM2 (but not device-mapper!) functionality, so enable it in your +config if your boot configuration depends on it or if you depend on any of the +lvm2-* daemons. + +Furthermore, we have considered other default enabled USE flags too, and have +come to the conclusion that USE=+thin makes even less sense than USE=+lvm. +Thin-provisioned LVM volumes are an important use case in certain VM hosting +scenarios, but unlikely to be relevant for the large majority of Gentoo users. + +In summary: +- Enable USE="lvm" if you use lvm2 (but not needed for device-mapper) as described above. +- Enable USE="lvm thin" if you use thin as described above. +- If you don't know what LVM2 is, you don't need to take any action.
[gentoo-commits] data/gentoo-news:master commit in: 2022-07-29-pipewire-sound-server/
commit: 48eabb9f21b21b35ec6e71d935e7d724644fb3b7 Author: Pacho Ramos gentoo org> AuthorDate: Fri Aug 5 10:54:37 2022 + Commit: Pacho Ramos gentoo org> CommitDate: Fri Aug 5 10:54:37 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=48eabb9f 2022-07-29-pipewire-sound-server: fix typos Closes: https://bugs.gentoo.org/862867 Signed-off-by: Pacho Ramos gentoo.org> .../2022-07-29-pipewire-sound-server.en.txt | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt index d41cca1..81b31f6 100644 --- a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt +++ b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt @@ -83,6 +83,9 @@ There are several options available: $ systemctl --user --now enable pipewire.socket pipewire-pulse.socket $ systemctl --user --now disable pipewire-media-session.service $ systemctl --user --force enable wireplumber.service + + Root user may replace --user with --global to change system default + configuration for all of the above commands. 2. To use PulseAudio's daemon for sound, users should disable USE=sound-server for PipeWire, enable USE=daemon on media-sound/pulseaudio, and add @@ -118,8 +121,8 @@ There are several options available: Alternatively, systemd users can run the following commands as root to change the default for all users: - # systemctl --user --global --enable pulseaudio.service pulseaudio.socket - # systemctl --user --global --force enable pipewire.socket pipewire-pulse.socket + # systemctl --global enable pulseaudio.service pulseaudio.socket + # systemctl --global --force disable pipewire.socket pipewire-pulse.socket (If taking this option, the services must be started manually as a one-off as a user.) @@ -154,8 +157,8 @@ There are several options available: Alternatively, systemd users can run the following commands as root to change the default for all users, again for the purposes of non-audio PipeWire use: - # systemctl --user --global --enable pipewire.socket - # systemctl --user --global --force enable wireplumber.service + # systemctl --global enable pipewire.socket + # systemctl --global --force enable wireplumber.service (If taking this option, the services must be started manually as a one-off as a user.)
[gentoo-commits] data/gentoo-news:master commit in: 2022-07-29-pipewire-sound-server/
commit: 6f193859d252b4d7f8cd1ccf5ae875a6049aeed8 Author: Sam James gentoo org> AuthorDate: Wed Aug 3 03:03:59 2022 + Commit: Sam James gentoo org> CommitDate: Wed Aug 3 03:03:59 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=6f193859 2022-07-29-pipewire-sound-server: mention systemd --global Closes: https://bugs.gentoo.org/862867 Signed-off-by: Sam James gentoo.org> .../2022-07-29-pipewire-sound-server.en.txt | 17 - 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt index 31283c0..d41cca1 100644 --- a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt +++ b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt @@ -116,6 +116,14 @@ There are several options available: $ systemctl --user --now enable pulseaudio.service pulseaudio.socket $ systemctl --user --now disable pipewire.socket pipewire-pulse.socket + Alternatively, systemd users can run the following commands as root to change + the default for all users: + # systemctl --user --global --enable pulseaudio.service pulseaudio.socket + # systemctl --user --global --force enable pipewire.socket pipewire-pulse.socket + + (If taking this option, the services must be started manually as a one-off as + a user.) + 3. For users without sound on their system, those using JACK without PipeWire, or those using pure ALSA without PipeWire, the following steps are recommended: @@ -139,11 +147,18 @@ There are several options available: files will need to run `gentoo-pipewire-launcher &` in e.g. `~/.xprofile`. - systemd users will also likely want to run the following commands, again + systemd users will also likely want to run the following commands as a user, again for the purposes of non-audio PipeWire use: $ systemctl --user --now enable pipewire.socket $ systemctl --user --now --force enable wireplumber.service + Alternatively, systemd users can run the following commands as root to change + the default for all users, again for the purposes of non-audio PipeWire use: + # systemctl --user --global --enable pipewire.socket + # systemctl --user --global --force enable wireplumber.service + + (If taking this option, the services must be started manually as a one-off as + a user.) Further resources: * https://wiki.gentoo.org/wiki/PipeWire
[gentoo-commits] data/gentoo-news:master commit in: 2022-07-29-pipewire-sound-server/
commit: 3d02b63c95ffb0e230fddfea4741c1067b5a7e3c Author: Sam James gentoo org> AuthorDate: Sun Jul 31 03:19:19 2022 + Commit: Sam James gentoo org> CommitDate: Sun Jul 31 03:19:19 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=3d02b63c 2022-07-29-pipewire-sound-server: mention adding PipeWire to world Closes: https://bugs.gentoo.org/861956 Signed-off-by: Sam James gentoo.org> .../2022-07-29-pipewire-sound-server.en.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt index 0cb4a2d..8d81d95 100644 --- a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt +++ b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt @@ -46,8 +46,9 @@ There are several options available: Deselect media-sound/pulseaudio-daemon: # emerge --deselect media-sound/pulseaudio-daemon - Then perform a world upgrade: - # emerge --ask --update --changed-use --deep @world + Then perform a world upgrade with PipeWire on the command line to add + it to the world file: + # emerge --ask --update --changed-use --deep @world media-video/pipewire Then depclean: # emerge --ask --depclean
[gentoo-commits] data/gentoo-news:master commit in: 2022-07-29-pipewire-sound-server/
commit: fbf0d8c39742d6bcedb75f94b9c94216f57ce888 Author: Sam James gentoo org> AuthorDate: Sun Jul 31 03:23:58 2022 + Commit: Sam James gentoo org> CommitDate: Sun Jul 31 03:23:58 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=fbf0d8c3 2022-07-29-pipewire-sound-server: give advice re pulseaudio-daemon only pkgs Closes: https://bugs.gentoo.org/862402 Signed-off-by: Sam James gentoo.org> .../2022-07-29-pipewire-sound-server.en.txt| 18 ++ 1 file changed, 18 insertions(+) diff --git a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt index 8d81d95..31283c0 100644 --- a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt +++ b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt @@ -60,6 +60,24 @@ There are several options available: files will need to run `gentoo-pipewire-launcher &` in e.g. `~/.xprofile`. + Users who want to switch to PipeWire providing a PulseAudio daemon + may need to `emerge --deselect` packages in their world file which + hard-require media-sound/pulseaudio-daemon. There are only a handful + of these. A non-exhaustive list: + * media-sound/paprefs + * media-sound/pasystray + * media-sound/pulseaudio-modules-bt (shouldn't be needed anyway) + * net-misc/pulseaudio-dlna + + If not using any of those packages anymore, please emerge --deselect + them. If still using these, PipeWire as a PulseAudio is not an + option at this time. + + (Note that media-libs/libpulse (which PipeWire will be using, don't emerge + libpulse manually) provides 'pactl' which can be used as a replacement for + e.g. media-sound/pulseaudio-ctl, so personal scripts can be adapted to this + if desired.) + systemd users will also need to run the following commands: $ systemctl --user --now disable pulseaudio.service pulseaudio.socket $ systemctl --user --now enable pipewire.socket pipewire-pulse.socket
[gentoo-commits] data/gentoo-news:master commit in: 2022-07-29-pipewire-sound-server/
commit: 1d217ffd5deca9d20b61acd2a7832272d036a0e0 Author: Sam James gentoo org> AuthorDate: Fri Jul 29 01:44:47 2022 + Commit: Sam James gentoo org> CommitDate: Fri Jul 29 01:44:47 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=1d217ffd 2022-07-29-pipewire-sound-server: add item Bug: https://bugs.gentoo.org/744622 Bug: https://bugs.gentoo.org/859280 Signed-off-by: Sam James gentoo.org> .../2022-07-29-pipewire-sound-server.en.txt| 130 + 1 file changed, 130 insertions(+) diff --git a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt new file mode 100644 index 000..0cb4a2d --- /dev/null +++ b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt @@ -0,0 +1,130 @@ +Title: PipeWire sound server migration +Author: Sam James +Posted: 2022-07-29 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: media-video/pipewire +Display-If-Installed: media-sound/pulseaudio +Display-If-Installed: media-sound/pulseaudio-daemon +Display-If-Installed: media-libs/libpulse + +PipeWire has gained a new USE flag "sound-server" for enabling/disabling its +sound server capabilities. + +This change is needed to avoid PipeWire and PulseAudio conflicting over control +of audio devices. Before this change, OpenRC users were in some cases +accidentally migrated to PipeWire which was difficult to override without +manually editing launcher files. + +For non-audio purposes, PipeWire is installed in many configurations as more +and more software depends on it for e.g. screensharing, sandboxing, +and window previews, so users will need to act based on their preferred +setup rather than simply avoiding installing PipeWire, as it is +increasingly required as a dependency. + +Packages needing PulseAudio's APIs will be migrated from the now-meta package +media-sound/pulseaudio to depending on media-libs/libpulse. The runtime +PulseAudio server can be provided by either PipeWire (media-video/pipewire) +or the original PulseAudio (media-sound/pulseaudio-daemon). + +The new sound-server USE flag for PipeWire allows easily controlling +this behavior. + +There are several options available: + +1. To use PipeWire for sound, users should enable USE=sound-server for PipeWire: + + Place the following entries in /etc/portage/package.use: + ``` + media-video/pipewire sound-server + media-sound/pulseaudio -daemon + ``` + + First, sync: + # emerge --sync + + Deselect media-sound/pulseaudio-daemon: + # emerge --deselect media-sound/pulseaudio-daemon + + Then perform a world upgrade: + # emerge --ask --update --changed-use --deep @world + + Then depclean: + # emerge --ask --depclean + + OpenRC users on an XDG-compliant desktop which respects autostart files + will not need to take any further action. + + OpenRC users using a minimal desktop which does not respect autostart + files will need to run `gentoo-pipewire-launcher &` in e.g. + `~/.xprofile`. + + systemd users will also need to run the following commands: + $ systemctl --user --now disable pulseaudio.service pulseaudio.socket + $ systemctl --user --now enable pipewire.socket pipewire-pulse.socket + $ systemctl --user --now disable pipewire-media-session.service + $ systemctl --user --force enable wireplumber.service + +2. To use PulseAudio's daemon for sound, users should disable USE=sound-server + for PipeWire, enable USE=daemon on media-sound/pulseaudio, and add + media-sound/pulseaudio-daemon to their world file: + + Place the following entries in /etc/portage/package.use: + ``` + media-video/pipewire -sound-server + media-sound/pulseaudio daemon + ``` + + Add media-sound/pulseaudio-daemon to @world: + # emerge --noreplace media-sound/pulseaudio-daemon + + Then perform a world upgrade: + # emerge --ask --update --changed-use --deep @world + + Then depclean: + # emerge --ask --depclean + + OpenRC users on an XDG-compliant desktop which respects autostart files + will not need to take any further action. + + OpenRC users using a minimal desktop which does not respect autostart + files should consider adding `gentoo-pipewire-launcher &` in e.g. + `~/.xprofile` but it's not strictly required in terms of audio + handling. It may be required in future for the non-audio usecases + described above. + + systemd users will also need to run the following commands: + $ systemctl --user --now enable pulseaudio.service pulseaudio.socket + $ systemctl --user --now disable pipewire.socket pipewire-pulse.socket + +3. For users without sound on their system, those using JACK without + PipeWire, or those using pure ALSA without PipeWire, the following steps + are recommended: + + Place the following entries in /etc/portage/package.use: + ``` + media-video/pipewire -sound-server + media-sound/pulseaudio -daemon + ``` + + Then perform a world
[gentoo-commits] data/gentoo-news:master commit in: 2017-01-15-kde-plasma-4-removal/
commit: 8c8dc9f31a085eedd1fc8b96bba8d883f3239310 Author: Michał Górny gentoo org> AuthorDate: Mon Jul 25 14:06:12 2022 + Commit: Michał Górny gentoo org> CommitDate: Mon Jul 25 16:15:25 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=8c8dc9f3 Remove old news item related to plasma 4 removal Signed-off-by: Michał Górny gentoo.org> .../2017-01-15-kde-plasma-4-removal.en.txt | 50 -- 1 file changed, 50 deletions(-) diff --git a/2017-01-15-kde-plasma-4-removal/2017-01-15-kde-plasma-4-removal.en.txt b/2017-01-15-kde-plasma-4-removal/2017-01-15-kde-plasma-4-removal.en.txt deleted file mode 100644 index d07bca7..000 --- a/2017-01-15-kde-plasma-4-removal/2017-01-15-kde-plasma-4-removal.en.txt +++ /dev/null @@ -1,50 +0,0 @@ -Title: KDE Plasma 4 and KDE profile removal -Author: Andreas Sturmlechner -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
[gentoo-commits] data/gentoo-news:master commit in: 2016-05-23-lastpass-changes/, 2016-12-06-ruby-20-removal/, ...
commit: 94c326535a4a2ab56f2ccd30fbc54b5aa501 Author: Ulrich Müller gentoo org> AuthorDate: Mon Jul 25 16:07:45 2022 + Commit: Ulrich Müller gentoo org> CommitDate: Mon Jul 25 16:07:45 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=94c32653 Remove old news items up to 2016 Signed-off-by: Ulrich Müller gentoo.org> ...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 11 files changed, 342 deletions(-) diff --git a/2016-01-08-some-dhcpcd-hooks-are-now-examples/2016-01-08-some-dhcpcd-hooks-are-now-examples.en.txt b/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 848a842..000 --- a/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/2016-01-27-upgrading-to-apache-2_4/2016-01-27-upgrading-to-apache-2_4.en.txt b/2016-01-27-upgrading-to-apache-2_4/2016-01-27-upgrading-to-apache-2_4.en.txt deleted file mode 100644 index bff0e7d..000 --- a/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/2016-04-07-kde-plasma5-stable/2016-04-07-kde-plasma5-stable.en.txt b/2016-04-07-kde-plasma5-stable/2016-04-07-kde-plasma5-stable.en.txt deleted file mode 100644 index c9302f0..000 --- a/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
[gentoo-commits] data/gentoo-news:master commit in: 2016-10-25-llvm_3_9_with_llvm_targets/
commit: 7dc22525e5170f646a8019f555d950276c4f208a Author: Michał Górny gentoo org> AuthorDate: Sun Jul 24 13:55:55 2022 + Commit: Michał Górny gentoo org> CommitDate: Sun Jul 24 13:55:55 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=7dc22525 Remove old LLVM_TARGETS news item Signed-off-by: Michał Górny gentoo.org> .../2016-10-25-llvm_3_9_with_llvm_targets.en.txt | 41 -- 1 file changed, 41 deletions(-) diff --git a/2016-10-25-llvm_3_9_with_llvm_targets/2016-10-25-llvm_3_9_with_llvm_targets.en.txt b/2016-10-25-llvm_3_9_with_llvm_targets/2016-10-25-llvm_3_9_with_llvm_targets.en.txt deleted file mode 100644 index d5656db..000 --- a/2016-10-25-llvm_3_9_with_llvm_targets/2016-10-25-llvm_3_9_with_llvm_targets.en.txt +++ /dev/null @@ -1,41 +0,0 @@ -Title: LLVM 3.9 with LLVM_TARGETS -Author: Michał Górny -Content-Type: text/plain -Posted: 2016-10-25 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed:
[gentoo-commits] data/gentoo-news:master commit in: 2020-09-28-python-2-7-cleanup/, 2018-05-22-python3-6/, 2021-05-05-python3-9/, ...
commit: b70041126763adc2f9e10a9e01cb3b0ffa25aaad Author: Michał Górny gentoo org> AuthorDate: Sun Jul 24 13:55:38 2022 + Commit: Michał Górny gentoo org> CommitDate: Sun Jul 24 13:55:38 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=b7004112 Remove old Python-related news items Signed-off-by: Michał Górny gentoo.org> ...python-exec-2-3-reclaims-python-symlinks.en.txt | 40 --- 2018-05-22-python3-6/2018-05-22-python3-6.en.txt | 61 --- 2020-04-22-python3-7/2020-04-22-python3-7.en.txt | 70 .../2020-09-28-python-2-7-cleanup.en.txt | 59 -- ...thon-preference-to-follow-python-targets.en.txt | 48 ...thon-preference-to-follow-python-targets.ru.txt | 49 - 2021-05-05-python3-9/2021-05-05-python3-9.en.txt | 119 2021-05-05-python3-9/2021-05-05-python3-9.ru.txt | 121 - 8 files changed, 567 deletions(-) diff --git a/2017-01-21-python-exec-2-3-reclaims-python-symlinks/2017-01-21-python-exec-2-3-reclaims-python-symlinks.en.txt b/2017-01-21-python-exec-2-3-reclaims-python-symlinks/2017-01-21-python-exec-2-3-reclaims-python-symlinks.en.txt deleted file mode 100644 index 4aa3415..000 --- a/2017-01-21-python-exec-2-3-reclaims-python-symlinks/2017-01-21-python-exec-2-3-reclaims-python-symlinks.en.txt +++ /dev/null @@ -1,40 +0,0 @@ -Title: python-exec 2.3 reclaims python* symlinks -Author: Michał Górny -Content-Type: text/plain -Posted: 2017-01-21 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: https://wiki.gentoo.org/wiki/Project:Python/python-exec diff --git a/2018-05-22-python3-6/2018-05-22-python3-6.en.txt b/2018-05-22-python3-6/2018-05-22-python3-6.en.txt deleted file mode 100644 index c8901e9..000 --- a/2018-05-22-python3-6/2018-05-22-python3-6.en.txt +++ /dev/null @@ -1,61 +0,0 @@ -Title: Python 3.6 to become the default target -Author: Michał Górny -Posted: 2018-05-22 -Revision: 1 -News-Item-Format: 2.0 -Display-If-Installed: dev-lang/python:3.4 -Display-If-Installed: dev-lang/python:3.5 - -On 2018-06-22, Python 3.6 will replace Python 3.5 in the default Python -targets for Gentoo systems. The new default targets will be: - -PYTHON_TARGETS="python2_7 python3_6" -PYTHON_SINGLE_TARGET="python3_6" - -If you have not overriden the value of those variables on your system, -then your package manager will want to use the new targets immediately. -In order to prevent dependency conflicts, please clean stray packages -and rebuild/upgrade all packages with USE flag changes after the change, -e.g.: - -emerge --depclean -emerge -1vUD @world -emerge --depclean - -Please note that upgrading dependencies in place may cause some -of the package dependencies to be temporarily missing. While this -should not affect scripts that are already fully loaded, it may cause -ImportErrors while starting Python scripts or loading additional -modules (only scripts running Python 3.5 are affected). - -In order to improve stability of the upgrade, you may choose to -temporarily enable both targets, i.e. set in /etc/portage/make.conf -or its equivalent: - -PYTHON_TARGETS="python2_7 python3_5 python3_6" -PYTHON_SINGLE_TARGET="python3_5" - -This will cause the dependencies to include both Python 3.5 and 3.6 -support on the next system upgrade. Once all packages are updated, -you can restart your scripts, remove the custom setting and run another -upgrade to remove support for Python 3.5. - -If you would like to postpone the switch to Python 3.6, you can copy -the current value of PYTHON_TARGETS and/or PYTHON_SINGLE_TARGET -to /etc/portage/make.conf or its equivalent: - -PYTHON_TARGETS="python2_7 python3_5" -PYTHON_SINGLE_TARGET="python3_5" - -If you would like to migrate your systems earlier, you can do the same -with the new value. - -If you are still using Python 3.4, please consider switching to a newer -version as it is reaching its end-of-life. The end-of-life dates -for the currently used versions are: - - Python 3.42019-03-16 - Python 2.72020-01-01 - Python 3.52020-09-13 [1] - -[1]:https://devguide.python.org/#status-of-python-branches diff --git a/2020-04-22-python3-7/2020-04-22-python3-7.en.txt b/2020-04-22-python3-7/2020-04-22-python3-7.en.txt deleted file mode 100644 index c933ca6..000 --- a/2020-04-22-python3-7/2020-04-22-python3-7.en.txt +++ /dev/null @@ -1,70 +0,0 @@ -Title: Python 3.7 to become the default target -Author: Michał Górny -Posted: 2020-04-22 -Revision: 1 -News-Item-Format: 2.0 -Display-If-Installed: dev-lang/python:3.6 -Display-If-Installed: dev-lang/python:3.7 - -On 2020-05-06 (or later), Python 3.7 will replace Python 3.6 as one -of the default Python targets for Gentoo systems. The new default -values will be: - -PYTHON_TARGETS="python2_7 python3_7" -PYTHON_SINGLE_TARGET="python3_7" - -If you have not overriden these variables on your
[gentoo-commits] data/gentoo-news:master commit in: 2022-06-26-mu-corruption/
commit: 3acbe0b422cb85f2895c0d825d272e37edae41f1 Author: Sam James gentoo org> AuthorDate: Fri Jul 1 09:23:00 2022 + Commit: Sam James gentoo org> CommitDate: Fri Jul 1 09:23:00 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=3acbe0b4 2022-06-26-mu-corruption: clarify only 1 affected version Signed-off-by: Sam James gentoo.org> 2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt b/2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt index 40a8ab2..4b4b1b9 100644 --- a/2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt +++ b/2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt @@ -5,10 +5,10 @@ Revision: 1 News-Item-Format: 2.0 Display-If-Installed: =net-mail/mu-1.7.23 -Development versions of mu between 1.7.18 and 1.7.25 have a bug causing -mail file names to sometimes get mangled after moving messages between -directories. Symptoms include unread messages never being marked as -read. +Development versions of mu between 1.7.18 and 1.7.25 (only 1.7.23 was ever +packaged in Gentoo) have a bug causing mail file names to sometimes get mangled +after moving messages between directories. Symptoms include unread messages +never being marked as read. Affected messages have the ':2,' flag appended multiple times. Using the following commands, users can remove the extra flags.
[gentoo-commits] data/gentoo-news:master commit in: 2022-06-26-mu-corruption/
commit: cb0c02adfb11edd106b87c9e20dcefd47cf9c16d Author: Sam James gentoo org> AuthorDate: Fri Jul 1 09:21:00 2022 + Commit: Sam James gentoo org> CommitDate: Fri Jul 1 09:21:00 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=cb0c02ad 2022-06-26-mu-corruption: fix Display-If-Installed Signed-off-by: Sam James gentoo.org> 2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt b/2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt index 2108c99..40a8ab2 100644 --- a/2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt +++ b/2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt @@ -3,7 +3,7 @@ Author: Matthew Smith Posted: 2022-06-26 Revision: 1 News-Item-Format: 2.0 -Display-If-Installed: net-mail/mu-1.7.23 +Display-If-Installed: =net-mail/mu-1.7.23 Development versions of mu between 1.7.18 and 1.7.25 have a bug causing mail file names to sometimes get mangled after moving messages between
[gentoo-commits] data/gentoo-news:master commit in: 2022-06-26-mu-corruption/
commit: 80f381eec461fea7918b6606b60128741a1154d5
Author: Matthew Smith gentoo org>
AuthorDate: Fri Jul 1 08:03:23 2022 +
Commit: Matthew Smith gentoo org>
CommitDate: Fri Jul 1 08:03:23 2022 +
URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=80f381ee
2022-06-06-mu-corruption: correct file name
Oops!
Signed-off-by: Matthew Smith gentoo.org>
.../{2022-06-06-mu-corruption.en.txt => 2022-06-26-mu-corruption.en.txt} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
diff --git a/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt
b/2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt
similarity index 100%
rename from 2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt
rename to 2022-06-26-mu-corruption/2022-06-26-mu-corruption.en.txt
[gentoo-commits] data/gentoo-news:master commit in: 2022-06-26-mu-corruption/
commit: bc0bf470ba2e27748ef266e7bd0e97bebbbd0c23
Author: Matthew Smith gentoo org>
AuthorDate: Sun Jun 26 08:25:30 2022 +
Commit: Matthew Smith gentoo org>
CommitDate: Fri Jul 1 07:54:15 2022 +
URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=bc0bf470
2022-06-26-mu-corruption: new entry
Add a news item explaining a maildir corruption bug in the mu/mu4e
mail reader.
Signed-off-by: Matthew Smith gentoo.org>
.../2022-06-06-mu-corruption.en.txt| 22 ++
1 file changed, 22 insertions(+)
diff --git a/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt
b/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt
new file mode 100644
index 000..2108c99
--- /dev/null
+++ b/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt
@@ -0,0 +1,22 @@
+Title: Mu 1.7.23 Causing Maildir Corruption
+Author: Matthew Smith
+Posted: 2022-06-26
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: net-mail/mu-1.7.23
+
+Development versions of mu between 1.7.18 and 1.7.25 have a bug causing
+mail file names to sometimes get mangled after moving messages between
+directories. Symptoms include unread messages never being marked as
+read.
+
+Affected messages have the ':2,' flag appended multiple times. Using the
+following commands, users can remove the extra flags.
+
+find ~/Maildir -name '*:2,*:*' |
+ sed "s/\(\([^:]*\)\(:2,\)\{1,\}\(:2,.*$\)\)/mv '\0' '\2\4'/" \
+ > rename.sh
+# review rename.sh. empty file indicates that you are unaffected
+sh rename.sh
+
+Upstream issue: https://github.com/djcb/mu/issues/2268
[gentoo-commits] data/gentoo-news:master commit in: 2022-06-13-python3-10/
commit: 77bf856baf0a12f6ad954c797bc1d566254c769a Author: Michał Górny gentoo org> AuthorDate: Fri Jun 10 10:00:11 2022 + Commit: Michał Górny gentoo org> CommitDate: Fri Jun 10 10:00:11 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=77bf856b 2022-06-13-python3-10: Add .ru translation Thanks to Alexey Sokolov! Signed-off-by: Michał Górny gentoo.org> 2022-06-13-python3-10/2022-06-13-python3-10.ru.txt | 120 + 1 file changed, 120 insertions(+) diff --git a/2022-06-13-python3-10/2022-06-13-python3-10.ru.txt b/2022-06-13-python3-10/2022-06-13-python3-10.ru.txt new file mode 100644 index 000..cc92b92 --- /dev/null +++ b/2022-06-13-python3-10/2022-06-13-python3-10.ru.txt @@ -0,0 +1,120 @@ +Title: Python 3.10 станет базовым с 2022-07-01 +Author: Michał Górny +Translator: Alexey Sokolov +Posted: 2022-06-13 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: dev-lang/python:3.8 +Display-If-Installed: dev-lang/python:3.9 + +1 июля 2022 года мы собираемся переключить Python target, используемый +по умолчанию на системах Gentoo, с версии 3.9 на версию 3.10. +Если вы не меняли значения переменных PYTHON_TARGETS или +PYTHON_SINGLE_TARGET, то упомянутое изменение затронет систему сразу, +и пакетный менеджер попытается переключиться на новый Python target +автоматически при следующем обновлении системы. + +Если вы изменили значения этих переменных, предпочитаете более +безопасный подход или при обновлении возникли проблемы, то +продолжайте читать далее. + +Пожалуйста, обратите внимание, что метод обновления по умолчанию +переключает пакеты на новую версию Python при их пересборки. +Это означает, что все зависящие друг от друга пакеты должны поддерживать +новую версию Python для продолжения обновления и некоторые программы +временно могут не находить свои зависимости во время обновления +(однако, запущенные программы, вероятно, не будут подвержены проблеме). + +Если переменные PYTHON_TARGETS или PYTHON_SINGLE_TARGET объявлены +в вашем файле make.conf, пожалуйста, удалите их, так как они будут +конфликтовать с представленными ниже примерами конфигурации package.use. +Мы не рекомендуем использовать файл make.conf для задания значений +переменных Python target, так как это препятствует применению +значений по умолчанию для пакетов, когда это необходимо. В этой новости +мы предполагаем, что вы используете файл /etc/portage/package.use +или ваш эквивалент этого файла конфигурации пакетного менеджера. + +С этого момента у вас есть выбор из следующих вариантов настройки: + +1. Если вы хотите, чтобы Python обновлялся автоматически, вы можете + удалить объявленные переменные PYTHON_TARGETS и PYTHON_SINGLE_TARGET. + Когда их значения по умолчанию изменятся, пакетный менеджер должен + самостоятельно всё обновить. Но если возникнут проблемы, вам всё ещё + может понадобиться запустить команды обновления. + +2. Если вы хотите пока отложить обновление, вы можете явно указать + старые значения в файле package.use. + +3. Если вы хотите обновиться раньше, вы можете явно задать новые + значения и запустить команды обновления. + +4. Если вы хотите использовать более безопасный подход (т.е. с меньшей + вероятностью временной поломки пакетов во время обновления), + вы можете выполнить последовательное обновление, описанное ниже. + +5. Наконец, вы можете произвольным образом комбинировать значения + переменных PYTHON_TARGETS и PYTHON_SINGLE_TARGET. + + +Откладывание обновления +=== +Чтобы отложить обновление, явно укажите старые значения: + +*/* PYTHON_TARGETS: -* python3_9 +*/* PYTHON_SINGLE_TARGET: -* python3_9 + +Это заставит систему использовать Python 3.9 и предотвратит последующие +обновления. Однако, учтите, что такое решение временное, +и в конце концов вам всё-таки придётся провести обновление. + + +Принудительное обновление += +Чтобы обновиться до Python 3.10 раньше, явно укажите новые значения: + +*/* PYTHON_TARGETS: -* python3_10 +*/* PYTHON_SINGLE_TARGET: -* python3_10 + +При этом важно не забыть удалить эти строки после изменения значений +по умолчанию, иначе они помешают последующим автоматическим обновлениям +на следующие версии Python. + + +Процедура безопасного обновления + +Более безопасный подход такой: сначала добавляется в систему поддержка +Python 3.10, а затем удаляется поддержка Python 3.9. Однако, учтите, +что все затронутые пакеты будут пересобраны дважды, что заметно дольше. + +Сначала включите Python 3.9 и Python 3.10 и запустите команды обновления: + +*/* PYTHON_TARGETS: -* python3_9 python3_10 +*/* PYTHON_SINGLE_TARGET: -* python3_9 + +Затем замените PYTHON_SINGLE_TARGET и ещё раз запустите обновление: + +*/* PYTHON_TARGETS: -* python3_9 python3_10 +*/* PYTHON_SINGLE_TARGET: -* python3_10 + +Наконец, переключитесь на окончательную версию и запустите обновление: + +*/* PYTHON_TARGETS: -*
[gentoo-commits] data/gentoo-news:master commit in: 2022-06-13-python3-10/
commit: 899175e0d2e523bc98386887f2f707469b977e3e Author: Michał Górny gentoo org> AuthorDate: Fri Jun 10 07:57:51 2022 + Commit: Michał Górny gentoo org> CommitDate: Fri Jun 10 09:59:57 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=899175e0 2022-06-13-python3-10: new entry Add a news item for the switch to Python 3.10. The text is roughly the same as for 3.9, with some minor grammar fixes. Signed-off-by: Michał Górny gentoo.org> 2022-06-13-python3-10/2022-06-13-python3-10.en.txt | 120 + 1 file changed, 120 insertions(+) diff --git a/2022-06-13-python3-10/2022-06-13-python3-10.en.txt b/2022-06-13-python3-10/2022-06-13-python3-10.en.txt new file mode 100644 index 000..cbf5df7 --- /dev/null +++ b/2022-06-13-python3-10/2022-06-13-python3-10.en.txt @@ -0,0 +1,120 @@ +Title: Python 3.10 to become the default on 2022-07-01 +Author: Michał Górny +Posted: 2022-06-13 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: dev-lang/python:3.8 +Display-If-Installed: dev-lang/python:3.9 + +We are planning to switch the default Python target of Gentoo systems +on 2022-07-01, from Python 3.9 to Python 3.10. 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_9 +*/* PYTHON_SINGLE_TARGET: -* python3_9 + +This will enforce Python 3.9 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.10 targets: + +*/* PYTHON_TARGETS: -* python3_10 +*/* PYTHON_SINGLE_TARGET: -* python3_10 + +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.10 support to your system first, +and only then remove Python 3.9. However, note that this involves two +rebuilds of all the affected packages, so it will take noticeably +longer. + +First, enable both Python 3.9 and Python 3.10, and then run the upgrade +commands: + +*/* PYTHON_TARGETS: -* python3_9 python3_10 +*/* PYTHON_SINGLE_TARGET: -* python3_9 + +Then switch PYTHON_SINGLE_TARGET and run the second batch of upgrades: + +*/* PYTHON_TARGETS: -* python3_9 python3_10 +*/* PYTHON_SINGLE_TARGET: -* python3_10 + +Finally, switch to the final version and upgrade: + +*/* PYTHON_TARGETS: -* python3_10 +*/* PYTHON_SINGLE_TARGET: -* python3_10 + +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.11, and upgrade manually then. + + +Upgrade commands + +The Python 3.9
[gentoo-commits] data/gentoo-news:master commit in: 2022-06-13-python3-10/
commit: 2df2bdc2eb24979ef17520910e1eb5e9fbd3d898 Author: Michał Górny gentoo org> AuthorDate: Fri Jun 10 16:44:18 2022 + Commit: Michał Górny gentoo org> CommitDate: Sat Jun 11 06:16:13 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=2df2bdc2 2022-06-13-python3-10: Add .pl translation Signed-off-by: Michał Górny gentoo.org> 2022-06-13-python3-10/2022-06-13-python3-10.pl.txt | 133 + 1 file changed, 133 insertions(+) diff --git a/2022-06-13-python3-10/2022-06-13-python3-10.pl.txt b/2022-06-13-python3-10/2022-06-13-python3-10.pl.txt new file mode 100644 index 000..684ff32 --- /dev/null +++ b/2022-06-13-python3-10/2022-06-13-python3-10.pl.txt @@ -0,0 +1,133 @@ +Title: Python 3.10 stanie się domyślną wersją począwszy od 2022-07-01 +Author: Michał Górny +Translator: Michał Górny +Posted: 2022-06-13 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: dev-lang/python:3.8 +Display-If-Installed: dev-lang/python:3.9 + +Gentoo planuje zmienić domyślną wersję Pythona z 3.9 na 3.10 w dniu +1. lipca 2022 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_9 +*/* PYTHON_SINGLE_TARGET: -* python3_9 + +W ten sposób Python 3.9 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.10: + +*/* PYTHON_TARGETS: -* python3_10 +*/* PYTHON_SINGLE_TARGET: -* python3_10 + +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.10 w pierwszym kroku, a następnie usunięcie Pythona +3.9. 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_9 python3_10 +*/* PYTHON_SINGLE_TARGET: -* python3_9 + +Następnie przełączyć należy wartość PYTHON_SINGLE_TARGET i przebudować +pakiety używające tych flag: + +*/* PYTHON_TARGETS: -* python3_9
[gentoo-commits] data/gentoo-news:master commit in: 2022-04-19-systemd-utils/
commit: 6e976b2854be2c5492025489dacba2158872a768 Author: Sam James gentoo org> AuthorDate: Mon May 30 23:36:38 2022 + Commit: Sam James gentoo org> CommitDate: Mon May 30 23:36:38 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=6e976b28 2022-04-19-systemd-utils: mention carrying over USE flags if needed more explicitly It's been a problem w/ some people not carrying over ABI_X86_32 in particular. Thanks-to: kurly Signed-off-by: Sam James gentoo.org> 2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt | 5 + 1 file changed, 5 insertions(+) diff --git a/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt b/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt index 799fad1..5224564 100644 --- a/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt +++ b/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt @@ -43,3 +43,8 @@ Possible problems when upgrading: 2. The 'boot' USE flag on sys-apps/systemd-utils is disabled by default. Users migrating from sys-boot/systemd-boot will need to enable the 'boot' USE flag (in package.use) to continue receiving updates. + +3. If you have package.use entries for any of sys-apps/systemd-tmpfiles, + sys-boot/systemd-boot, or sys-fs/udev, please update the relevant lines + to refer to sys-apps/systemd-utils instead. This might include + ABI_X86_32 for some users!
[gentoo-commits] data/gentoo-news:master commit in: 2022-04-19-systemd-utils/
commit: cfa8603a631b0e72c3e8d081e0b6522c8e516e66 Author: Sam James gentoo org> AuthorDate: Mon May 30 23:28:03 2022 + Commit: Sam James gentoo org> CommitDate: Mon May 30 23:28:03 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=cfa8603a 2022-04-19-systemd-utils: clarify purpose is for OpenRC users Signed-off-by: Sam James gentoo.org> 2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt b/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt index ed11880..570c1e8 100644 --- a/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt +++ b/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt @@ -10,10 +10,10 @@ Display-If-Installed: sys-fs/udev The sys-apps/systemd-utils package was recently added to the gentoo repository. This replaces sys-apps/systemd-tmpfiles, -sys-boot/systemd-boot, and sys-fs/udev with a single package. USE flags -are provided to allow each component to be enabled or disabled. This -change was made to significantly ease maintenance of tools split out -from systemd. +sys-boot/systemd-boot, and sys-fs/udev with a single package, and is +for OpenRC users. USE flags are provided to allow each component to be enabled +or disabled. This change was made to significantly ease maintenance of tools +split out from systemd. When upgrading to sys-apps/systemd-tmpfiles-250, sys-apps/systemd-utils[tmpfiles] will be pulled in as a dependency.
[gentoo-commits] data/gentoo-news:master commit in: 2022-05-26-apache-nginx-glep-81/
commit: afc52af63aa189f58abcc849b3d64a7f8e3041e7 Author: Agostino Sarubbo gentoo org> AuthorDate: Mon May 30 09:12:56 2022 + Commit: Agostino Sarubbo gentoo org> CommitDate: Mon May 30 09:12:56 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=afc52af6 2022-05-26-apache-nginx-glep-81: typo Signed-off-by: Agostino Sarubbo gentoo.org> 2022-05-26-apache-nginx-glep-81/2022-05-26-apache-nginx-glep-81.en.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2022-05-26-apache-nginx-glep-81/2022-05-26-apache-nginx-glep-81.en.txt b/2022-05-26-apache-nginx-glep-81/2022-05-26-apache-nginx-glep-81.en.txt index d0afab2..195c867 100644 --- a/2022-05-26-apache-nginx-glep-81/2022-05-26-apache-nginx-glep-81.en.txt +++ b/2022-05-26-apache-nginx-glep-81/2022-05-26-apache-nginx-glep-81.en.txt @@ -36,7 +36,7 @@ in make.conf or per package in package.env: for overriding default assigned shell. If being set per package in package.env, it needs to -be set for acct-user/apache or aact-user/nginx, +be set for acct-user/apache or acct-user/nginx, depending on which user should be modified. See [1] for more details on those variables.
[gentoo-commits] data/gentoo-news:master commit in: 2022-05-26-apache-nginx-glep-81/
commit: 1ed1d66b4ccebfbceaa6309ed8ef64747352af3a Author: Conrad Kostecki gentoo org> AuthorDate: Fri May 13 23:29:09 2022 + Commit: Conrad Kostecki gentoo org> CommitDate: Thu May 26 14:56:35 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=1ed1d66b 2022-05-26-apache-nginx-glep-81: add news Bug: https://bugs.gentoo.org/701254 Bug: https://bugs.gentoo.org/802495 Signed-off-by: Conrad Kostecki gentoo.org> .../2022-05-26-apache-nginx-glep-81.en.txt | 66 ++ 1 file changed, 66 insertions(+) diff --git a/2022-05-26-apache-nginx-glep-81/2022-05-26-apache-nginx-glep-81.en.txt b/2022-05-26-apache-nginx-glep-81/2022-05-26-apache-nginx-glep-81.en.txt new file mode 100644 index 000..d0afab2 --- /dev/null +++ b/2022-05-26-apache-nginx-glep-81/2022-05-26-apache-nginx-glep-81.en.txt @@ -0,0 +1,66 @@ +Title: Migration to GLEP-81 enabled webservers +Author: Conrad Kostecki +Posted: 2022-05-20 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: www-servers/apache +Display-If-Installed: www-servers/nginx + +In future, in order to complete the whole GLEP-81 migration, +the packages www-servers/apache and www-servers/nginx +will be migrated to GLEP-81. + +If changes have been made to the default user and group created +by one of the both packages, the configuration needs to be updated, +as otherwise it will be overwritten. + +The following configuration settings can be set +in make.conf or per package in package.env: + +1. ACCT_USER__GROUPS + for overriding all default groups. + +2. ACCT_USER__GROUPS_ADD + for adding additional groups to default groups. + +3. ACCT_USER__HOME + for overriding default home directory. + +4. ACCT_USER__HOME_OWNER + for overriding default owner of home directory. + +5. ACCT_USER__HOME_PERMS + for overriding default permissions of home directory. + +6. ACCT_USER__SHELL + for overriding default assigned shell. + +If being set per package in package.env, it needs to +be set for acct-user/apache or aact-user/nginx, +depending on which user should be modified. + +See [1] for more details on those variables. + +** Package acct-user/apache will use username/group 'apache'. +-> ACCT_USER_APACHE_GROUPS=".." +-> ACCT_USER_APACHE_GROUPS_ADD=".." +-> ACCT_USER_APACHE_HOME=".." +-> ACCT_USER_APACHE_HOME_OWNER=".." +-> ACCT_USER_APACHE_HOME_PERMS=".." +-> ACCT_USER_APACHE_SHELL=".." + +** Package acct-user/nginx will use username/group 'nginx'. +-> ACCT_USER_NGINX_GROUPS=".." +-> ACCT_USER_NGINX_GROUPS_ADD=".." +-> ACCT_USER_NGINX_HOME=".." +-> ACCT_USER_NGINX_HOME_OWNER=".." +-> ACCT_USER_NGINX_HOME_PERMS=".." +-> ACCT_USER_NGINX_SHELL=".." + +Please update configuration parameters before emerging +both GLEP-81 enabled ebuilds, as otherwise configuration +will be overwritten to default. + +Migration to GLEP-81 will start after 2022-07-01. + +[1] https://devmanual.gentoo.org/eclass-reference/acct-user.eclass/index.html
[gentoo-commits] data/gentoo-news:master commit in: 2022-05-23-borgmatic-config-changes/
commit: b12ded38ff333b9cb091c81c1344e62b965426c9 Author: Marek Szuba gentoo org> AuthorDate: Wed May 18 09:42:10 2022 + Commit: Marek Szuba gentoo org> CommitDate: Mon May 23 22:15:40 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=b12ded38 2022-05-23-borgmatic-config-changes: new item Signed-off-by: Marek Szuba gentoo.org> .../2022-05-23-borgmatic-config-changes.en.txt | 14 ++ 1 file changed, 14 insertions(+) diff --git a/2022-05-23-borgmatic-config-changes/2022-05-23-borgmatic-config-changes.en.txt b/2022-05-23-borgmatic-config-changes/2022-05-23-borgmatic-config-changes.en.txt new file mode 100644 index 000..f2374f6 --- /dev/null +++ b/2022-05-23-borgmatic-config-changes/2022-05-23-borgmatic-config-changes.en.txt @@ -0,0 +1,14 @@ +Title: Breaking configuration changes in borgmatic-1.6.0 +Author: Marek Szuba +Posted: 2022-05-23 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: app-backup/borgmatic + +Version 1.6.0 of app-backup/borgmatic has introduced some breaking +changes to the way Borgmatic handles the merging of its configuration +files and executes command hooks. If you use these features, please +review your Borgmatic config files to make sure they continue to work +correctly with >=app-backup/borgmatic-1.6.0. For details, see [1]. + +[1] https://github.com/borgmatic-collective/borgmatic/releases/tag/1.6.0
[gentoo-commits] data/gentoo-news:master commit in: 2022-04-19-systemd-utils/
commit: 7fc944cc8b64a739adac5d62d15b744af1c6ce83 Author: Mike Gilbert gentoo org> AuthorDate: Sun Apr 17 18:26:15 2022 + Commit: Mike Gilbert gentoo org> CommitDate: Tue Apr 19 21:26:29 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=7fc944cc 2022-04-19-systemd-utils: new entry Signed-off-by: Mike Gilbert gentoo.org> .../2022-04-19-systemd-utils.en.txt| 42 ++ 1 file changed, 42 insertions(+) diff --git a/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt b/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt new file mode 100644 index 000..ed11880 --- /dev/null +++ b/2022-04-19-systemd-utils/2022-04-19-systemd-utils.en.txt @@ -0,0 +1,42 @@ +Title: Migration to sys-apps/systemd-utils +Author: Mike Gilbert +Posted: 2022-04-19 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: sys-apps/systemd-tmpfiles +Display-If-Installed: sys-apps/systemd-utils +Display-If-Installed: sys-boot/systemd-boot +Display-If-Installed: sys-fs/udev + +The sys-apps/systemd-utils package was recently added to the gentoo +repository. This replaces sys-apps/systemd-tmpfiles, +sys-boot/systemd-boot, and sys-fs/udev with a single package. USE flags +are provided to allow each component to be enabled or disabled. This +change was made to significantly ease maintenance of tools split out +from systemd. + +When upgrading to sys-apps/systemd-tmpfiles-250, +sys-apps/systemd-utils[tmpfiles] will be pulled in as a dependency. + +When upgrading to sys-boot/systemd-boot-250, +sys-apps/systemd-utils[boot] will be pulled in as a dependency. + +When upgrading to sys-fs/udev-250, sys-apps/systemd-utils[udev] will be +pulled in as a dependency. + +At a later date, sys-apps/systemd-tmpfiles, sys-boot/systemd-boot, and +sys-fs/udev will be masked for removal once a suitable version of +sys-apps/systemd-utils has been marked stable and sufficient time has +been provided for users to migrate. + +Possible problems when upgrading: + +1. If sys-fs/eudev is present in the world file (@selected), emerge will + abort the upgrade with a unsolvable blocker error. To resolve this, + either remove sys-fs/eudev from the world file + (emerge --deselect sys-fs/eudev), or disable the 'udev' USE flag for + sys-apps/systemd-utils. + +2. The 'boot' USE flag on sys-apps/systemd-utils is disabled by default. + Users migrating from sys-boot/systemd-boot will need to enable the + 'boot' USE flag (in package.use) to continue receiving updates.
[gentoo-commits] data/gentoo-news:master commit in: 2022-04-17-systemd-utils-update-needed/
commit: b2f594c5cdfab4e0b7138fa294be29cdae185b21 Author: Mike Gilbert gentoo org> AuthorDate: Sun Apr 17 22:52:31 2022 + Commit: Mike Gilbert gentoo org> CommitDate: Sun Apr 17 23:07:20 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=b2f594c5 2022-04-17-systemd-utils-update-needed: new emergency item Signed-off-by: Mike Gilbert gentoo.org> .../2022-04-17-systemd-utils-update-needed.en.txt| 12 1 file changed, 12 insertions(+) diff --git a/2022-04-17-systemd-utils-update-needed/2022-04-17-systemd-utils-update-needed.en.txt b/2022-04-17-systemd-utils-update-needed/2022-04-17-systemd-utils-update-needed.en.txt new file mode 100644 index 000..22262ed --- /dev/null +++ b/2022-04-17-systemd-utils-update-needed/2022-04-17-systemd-utils-update-needed.en.txt @@ -0,0 +1,12 @@ +Title: sys-apps/systemd-utils update needed +Author: Mike Gilbert +Posted: 2022-04-17 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: =sys-apps/systemd-utils-250.4 + +The currently installed version of sys-apps/systemd-utils may cause +kernel modules to fail to load on boot. + +Please upgrade to >=sys-apps/systemd-utils-250.4-r1 as soon as possible, +and certainly before rebooting your system.
[gentoo-commits] data/gentoo-news:master commit in: 2022-04-12-ccache-4_6-sandbox/
commit: 930b96b94ebad678ef11b1d8aa5fd8aa609f198f Author: Sam James gentoo org> AuthorDate: Tue Apr 12 08:52:57 2022 + Commit: Sam James gentoo org> CommitDate: Tue Apr 12 08:52:57 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=930b96b9 2022-04-12-ccache-4_6-sandbox: add news item Bug: https://bugs.gentoo.org/837362 Signed-off-by: Sam James gentoo.org> .../2022-04-12-ccache-4_6-sandbox.en.txt | 25 ++ 1 file changed, 25 insertions(+) diff --git a/2022-04-12-ccache-4_6-sandbox/2022-04-12-ccache-4_6-sandbox.en.txt b/2022-04-12-ccache-4_6-sandbox/2022-04-12-ccache-4_6-sandbox.en.txt new file mode 100644 index 000..1dabea9 --- /dev/null +++ b/2022-04-12-ccache-4_6-sandbox/2022-04-12-ccache-4_6-sandbox.en.txt @@ -0,0 +1,25 @@ +Title: Sandbox issue with ccache 4.6 +Author: Sam James +Posted: 2022-04-12 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: =dev-util/ccache-4.6 + +Users with ccache enabled for the dev-util/ccache package itself may need +to temporarily disable ccache in order to upgrade the package. + +Users on an earlier version of ccache (<4.6) or newer (>=4.6-r1) are +unaffected. + +For a small window (between 2022-04-09-4:30AM UTC and 2022-04-09-11:27AM UTC), +the ccache ebuild may have caused a sandbox violation [0] in some circumstances. + +To resolve this issue, temporarily re-emerge dev-util/ccache with ccache +disabled: +# FEATURES="-ccache" emerge -v1 ">dev-util/ccache-4.6" + +The sandbox violations occur when trying to use ccache for any package; +users who do not have ccache enabled globally (or at least not for ccache +itself) should also proactively upgrade ccache as above. + +[0] https://bugs.gentoo.org/837362
[gentoo-commits] data/gentoo-news:master commit in: 2022-03-30-qt-5_15_3-bump/
commit: bddd22453dda8fba0e62ba78e32f17fe550a9494 Author: Andreas Sturmlechner gentoo org> AuthorDate: Wed Mar 30 18:40:28 2022 + Commit: Andreas Sturmlechner gentoo org> CommitDate: Wed Mar 30 18:48:02 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=bddd2245 2022-03-30-qt-5_15_3-bump: Add news item Signed-off-by: Andreas Sturmlechner gentoo.org> .../2022-03-30-qt-5_15_3-bump.en.txt | 23 .../2022-03-30-qt-5_15_3-bump.ru.txt | 25 ++ 2 files changed, 48 insertions(+) diff --git a/2022-03-30-qt-5_15_3-bump/2022-03-30-qt-5_15_3-bump.en.txt b/2022-03-30-qt-5_15_3-bump/2022-03-30-qt-5_15_3-bump.en.txt new file mode 100644 index 000..ad4db1d --- /dev/null +++ b/2022-03-30-qt-5_15_3-bump/2022-03-30-qt-5_15_3-bump.en.txt @@ -0,0 +1,23 @@ +Title: Qt 5.15.3 version bump with binary path changes +Author: Andreas Sturmlechner +Posted: 2022-03-30 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: >=dev-qt/qtcore-5.15.3 + +Up until Qt 5.15.2 we were using qtchooser to provide unversioned links to Qt +binaries in PATH, like qmake, moc, qmljs etc. Starting with 5.15.3 [1] such +links will be installed by each respective Qt package and '5'-version-suffixed, +e.g. qmake becomes qmake5, qml becomes qml5 etc., mirroring Qt6. + +If you develop with Qt5 and rely on unversioned binaries for your workflow, +dev-qt/qtchooser as a tool for quickly switching between multiple Qt +installations (e.g. Qt3, Qt4 and Qt5) can still be manually installed. The +'default' Qt version in PATH is then controlled via config in +/etc/xdg/qtchooser. + +Otherwise, dev-qt/qtchooser will be slated for cleanup on your next +emerge --depclean run. + +[1] https://archives.gentoo.org/gentoo-dev/message/ +5f3681b5b28dabeb5339d44e9585d29f diff --git a/2022-03-30-qt-5_15_3-bump/2022-03-30-qt-5_15_3-bump.ru.txt b/2022-03-30-qt-5_15_3-bump/2022-03-30-qt-5_15_3-bump.ru.txt new file mode 100644 index 000..4c5fa16 --- /dev/null +++ b/2022-03-30-qt-5_15_3-bump/2022-03-30-qt-5_15_3-bump.ru.txt @@ -0,0 +1,25 @@ +Title: Новая версия Qt 5.15.3 меняет имена исполняемых файлов +Author: Andreas Sturmlechner +Translator: Alexey Sokolov +Posted: 2022-03-30 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: >=dev-qt/qtcore-5.15.3 + +В версиях Qt по 5.15.2 мы использовали qtchooser, чтобы устанавливать +исполняемые файлы Qt в PATH без номера версии, такие как qmake, moc, +qmljs и т.д. Начиная с версии 5.15.3 [1] эти файлы будут установлены самим +соответствующим пакетом Qt и будут заканчиваться на "5": например, qmake +станет qmake5, qml станет qml5 и т.д., так же, как это делает Qt 6. + +Если вы используете Qt5 при разработке, и ваш рабочий процесс зависит от +этих файлов без версии, вы всё ещё можете установить dev-qt/qtchooser — +инструмент для быстрого переключения между различными установленными Qt +(например, Qt3, Qt4, Qt5). В таком случае версия Qt в PATH по умолчанию +настраивается в /etc/xdg/qtchooser. + +В противном случае dev-qt/qtchooser будет удалён при следующем запуске +emerge --depclean. + +[1] https://archives.gentoo.org/gentoo-dev/message/ +5f3681b5b28dabeb5339d44e9585d29f
[gentoo-commits] data/gentoo-news:master commit in: 2022-03-05-singularity_to_apptainer/
commit: 2b7edd6d19f027aed15052b08ae113ce7f4f1f6b Author: Marek Szuba gentoo org> AuthorDate: Tue Feb 22 12:43:30 2022 + Commit: Marek Szuba gentoo org> CommitDate: Sat Mar 5 01:29:03 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=2b7edd6d Add 2022-03-05-singularity_to_apptainer Signed-off-by: Marek Szuba gentoo.org> .../2022-03-05-singularity_to_apptainer.en.txt | 26 ++ 1 file changed, 26 insertions(+) diff --git a/2022-03-05-singularity_to_apptainer/2022-03-05-singularity_to_apptainer.en.txt b/2022-03-05-singularity_to_apptainer/2022-03-05-singularity_to_apptainer.en.txt new file mode 100644 index 000..0d9c992 --- /dev/null +++ b/2022-03-05-singularity_to_apptainer/2022-03-05-singularity_to_apptainer.en.txt @@ -0,0 +1,26 @@ +Title: Transition from sys-cluster/singularity to app-containers/apptainer +Author: Marek Szuba +Posted: 2022-03-05 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: sys-cluster/singularity + +In autumn 2021 the Singularity project joined the Linux Foundation +and changed its name to Apptainer [1]. The change has been reflected +in the renaming of files and environment variables, as well as a reset +of version numbers back to 1.0.0. + +Apptainer packages include compatibility symlinks to old Singularity +executables, provide bash-completion rules for both the old and the new +name, continue to honour old environment variables, and will upon +the first run import user data from Singularity directories. Therefore, +for most users it will be sufficient to deselect the old package and +install the new one, e.g.: + +emerge --deselect sys-cluster/singularity +emerge app-containers/apptainer + +However, customisations made to system-wide configuration +in /etc/singularity will have to be applied to /etc/apptainer by hand. + +[1] https://apptainer.org/news/community-announcement-20211130/
[gentoo-commits] data/gentoo-news:master commit in: 2021-10-18-libxcrypt-migration-stable/
commit: 11dac3088fb3e629e0b899248e1228ad723e40f6 Author: Sam James gentoo org> AuthorDate: Tue Feb 8 03:21:38 2022 + Commit: Sam James gentoo org> CommitDate: Tue Feb 8 03:21:38 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=11dac308 2021-10-18-libxcrypt-migration-stable: mention circular dependencies Signed-off-by: Sam James gentoo.org> .../2021-10-18-libxcrypt-migration-stable.en.txt | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt b/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt index d821eac..74e80d5 100644 --- a/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt +++ b/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt @@ -43,7 +43,7 @@ aggressive in protecting even orphaned files. Instead, use FEATURES="unmerge-orphans" which is almost identical in behaviour. -## Delaying the migration +## Delaying the migration *or* circular dependencies If for whatever reason you do *not* wish to switch now - which is only delaying the inevitable - you @@ -53,6 +53,11 @@ need to take the following steps: * mask >=virtual/libcrypt-2 * unmask virtual/libcrypt:0/1 +If hitting circular dependencies involving Python 3.10, +see the wiki for more details [3], but the same steps +listed above must be taken (mask newer libcrypt temporarily, +do a world upgrade, then unmask). + ## Migrating early If you wish to manually migrate now, there are a series @@ -102,3 +107,4 @@ For more information or troubleshooting tips, please see: [0] https://bugs.gentoo.org/802267 [1] https://bugs.gentoo.org/802807 [2] https://bugs.gentoo.org/802210 +[3] https://wiki.gentoo.org/wiki/User:Sam/Portage_help/Circular_dependencies#Python_and_libcrypt
[gentoo-commits] data/gentoo-news:master commit in: 2021-08-24-eudev-retirement/
commit: dd2e0fd1e7031f0d45828f6177b2e3d080d7b438 Author: Sam James gentoo org> AuthorDate: Fri Jan 14 19:05:14 2022 + Commit: Sam James gentoo org> CommitDate: Fri Jan 14 19:06:11 2022 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=dd2e0fd1 2021-08-24-eudev-retirement: update news item re eudev staying Signed-off-by: Sam James gentoo.org> .../2021-08-24-eudev-retirement.en.txt| 11 +++ 1 file changed, 11 insertions(+) diff --git a/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt b/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt index ec6bdc7..750f09d 100644 --- a/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt +++ b/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt @@ -5,6 +5,17 @@ Revision: 1 News-Item-Format: 2.0 Display-If-Installed: sys-fs/eudev +UPDATE (2022-01-14): sys-fs/eudev is now maintained by a new collection +of cross-distribution contributors. It will therefore remain in the +Gentoo repository. + +Help is still welcome with maintaining it within Gentoo if users +are interested. + +The default for new installs will remain sys-fs/udev and the +rest of this news item still applies. +--- + sys-fs/udev is becoming the standard provider of udev on non-systemd (e.g. OpenRC) systems. Users of systemd will continue to use the udev services provided by the sys-apps/systemd package itself.
[gentoo-commits] data/gentoo-news:master commit in: 2021-08-24-eudev-retirement/
commit: 96b008f1c3f64e6550efc18b24e9f44fb1b9ff4e Author: Sam James gentoo org> AuthorDate: Mon Dec 20 23:24:07 2021 + Commit: Sam James gentoo org> CommitDate: Mon Dec 20 23:24:07 2021 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=96b008f1 2021-08-24-eudev-retirement: tweak INSTALL_MASK guidance again Signed-off-by: Sam James gentoo.org> 2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt b/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt index 0fe5df3..ec6bdc7 100644 --- a/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt +++ b/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt @@ -27,8 +27,8 @@ will still have to rely on eudev before also being removed on 2022-01-01. If you happen to have an INSTALL_MASK including "systemd", e.g. a blanket "*systemd*" glob, you will inevitably break your system. sys-fs/udev -contains "systemd" in some of its filenames, hence a blanket filter rule will -likely lead to a non-functional udev installation. +contains "systemd" in some of its directories and filenames, hence a blanket +filter rule will likely lead to a non-functional udev installation. Please also verify you do not have "sys-fs/udev" in package.mask.
[gentoo-commits] data/gentoo-news:master commit in: 2021-08-24-eudev-retirement/
commit: 57d96e215f386c35d837dbb05c2427915d5cf442 Author: Sam James gentoo org> AuthorDate: Mon Dec 20 23:21:54 2021 + Commit: Sam James gentoo org> CommitDate: Mon Dec 20 23:21:54 2021 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=57d96e21 2021-08-24-eudev-retirement: reword INSTALL_MASK guidance Signed-off-by: Sam James gentoo.org> 2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt b/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt index 4b2de2e..0fe5df3 100644 --- a/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt +++ b/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt @@ -25,10 +25,10 @@ will still have to rely on eudev before also being removed on 2022-01-01. **WARNING 1** -If you happen to have an INSTALL_MASK with a blanket "*systemd*" glob, -you will inevitably break your system. sys-fs/udev contains "systemd" in -some of its filenames, hence a blanket filter rule will likely lead to -a non-functional udev installation. +If you happen to have an INSTALL_MASK including "systemd", e.g. a +blanket "*systemd*" glob, you will inevitably break your system. sys-fs/udev +contains "systemd" in some of its filenames, hence a blanket filter rule will +likely lead to a non-functional udev installation. Please also verify you do not have "sys-fs/udev" in package.mask.
[gentoo-commits] data/gentoo-news:master commit in: 2021-08-24-eudev-retirement/
commit: 6f20a2a293fa15be22161e885982fe1e035c5d11 Author: Sam James gentoo org> AuthorDate: Fri Dec 17 10:02:21 2021 + Commit: Sam James gentoo org> CommitDate: Fri Dec 17 10:02:45 2021 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=6f20a2a2 2021-08-24-eudev-retirement: mention sys-fs/udev in package.mask A fair number of users have hit this. Signed-off-by: Sam James gentoo.org> 2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt b/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt index c2b2b76..4b2de2e 100644 --- a/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt +++ b/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt @@ -30,6 +30,7 @@ you will inevitably break your system. sys-fs/udev contains "systemd" in some of its filenames, hence a blanket filter rule will likely lead to a non-functional udev installation. +Please also verify you do not have "sys-fs/udev" in package.mask. **WARNING 2**
[gentoo-commits] data/gentoo-news:master commit in: 2021-10-18-libxcrypt-migration-stable/
commit: b76a1d4a5fa5a0e2a81d93c086d3077da82de89b Author: Sam James gentoo org> AuthorDate: Thu Dec 16 06:25:26 2021 + Commit: Sam James gentoo org> CommitDate: Thu Dec 16 06:25:26 2021 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=b76a1d4a 2021-10-18-libxcrypt-migration-stable: improve readability a bit Bug: https://bugs.gentoo.org/699422 Bug: https://bugs.gentoo.org/809410 Signed-off-by: Sam James gentoo.org> .../2021-10-18-libxcrypt-migration-stable.en.txt | 31 +- 1 file changed, 24 insertions(+), 7 deletions(-) diff --git a/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt b/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt index 1b80f95..d821eac 100644 --- a/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt +++ b/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt @@ -13,7 +13,10 @@ this has been tested for years already) and switching to the external libxcrypt implementation, now also in stable installations. This will be a regular update, and in nearly all cases you -will not have to take any action and not observe any problems. +will not have to take any action and not observe any problems. If +you hit issues, please read on. + +## Upgrades before 2021-11-01 We do recommend, however, that your system is *fully* up to date first. This is a standard recommendation but in this @@ -21,6 +24,14 @@ specific case, it is useful to have a simplified depgraph to ensure that Portage is able to smoothly calculate an upgrade path. +Please take the opportunity to fully upgrade your +systems now, before the migration occurs, to simplify matters + +This change will occur on 2021-11-01 for stable users. +~arch users by default should already have switched. + +## General advice + We also recommend being in a root shell (not via 'sudo' or similar tools) so that if any issues occur during the upgrade, you are not locked out of the console. It is not expected @@ -32,11 +43,7 @@ aggressive in protecting even orphaned files. Instead, use FEATURES="unmerge-orphans" which is almost identical in behaviour. -That is, please take the opportunity to fully upgrade your -systems now, before the migration occurs, to simplify matters. - -This change will occur on 2021-11-01 for stable users. -~arch users by default should already have switched. +## Delaying the migration If for whatever reason you do *not* wish to switch now - which is only delaying the inevitable - you @@ -46,6 +53,8 @@ need to take the following steps: * mask >=virtual/libcrypt-2 * unmask virtual/libcrypt:0/1 +## Migrating early + If you wish to manually migrate now, there are a series of steps described on the wiki (see below), but the outline is: * unforce the crypt USE flag of sys-libs/glibc and disable it @@ -53,12 +62,16 @@ of steps described on the wiki (see below), but the outline is: and enable it * unmask ~virtual/libcrypt-2 +## PAM warning + Please note that if you last changed your password before ~2008, it may be using md5crypt or similar other weak mechanisms in /etc/shadow; a bug in PAM [0][1] may mean that you were unable to login. We recommend using "passwd" to change/refresh your password so it is using modern methods. A new version of PAM has been added to the tree to resolve this issue. +## Build failures + In some cases, Portage may schedule a rebuild of certain packages in an incorrect order [2]. If building a package fails, please try upgrading Python itself to help avoid spurious build failures, and then @@ -69,7 +82,9 @@ libcrypt and libxcrypt first: And then continue the world upgrade with Portage's "--keep-going=y". -If you hit conflicts, please see the wiki page linked below, but +## Blockers/conflicts + +If you hit blockers/conflicts, please see the wiki page linked below, but common helpful tips are: * try more backtracking (e.g. --backtrack=1000) * try --ignore-built-slot-operator-deps=y temporarily on the world upgrade, @@ -77,6 +92,8 @@ then run a world upgrade again without it. Do NOT attempt to unmerge glibc at any point. +## More help + For more information or troubleshooting tips, please see: * https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation * https://bugs.gentoo.org/699422
[gentoo-commits] data/gentoo-news:master commit in: 2021-08-24-eudev-retirement/
commit: eba63773624dd2dbdceefdf8ab2c88aab22dab40 Author: Sam James gentoo org> AuthorDate: Thu Dec 2 01:36:34 2021 + Commit: Sam James gentoo org> CommitDate: Thu Dec 2 01:36:34 2021 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=eba63773 2021-08-24-eudev-retirement: mention options for disabling "predictable naming" Bug: https://bugs.gentoo.org/827937 Signed-off-by: Sam James gentoo.org> .../2021-08-24-eudev-retirement.en.txt | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt b/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt index fd360d7..c2b2b76 100644 --- a/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt +++ b/2021-08-24-eudev-retirement/2021-08-24-eudev-retirement.en.txt @@ -23,13 +23,25 @@ in order for Portage to replace eudev with sys-fs/udev once the package.mask is in place. We fully support udev on musl, whereas uclibc will still have to rely on eudev before also being removed on 2022-01-01. - **WARNING** + **WARNING 1** If you happen to have an INSTALL_MASK with a blanket "*systemd*" glob, you will inevitably break your system. sys-fs/udev contains "systemd" in some of its filenames, hence a blanket filter rule will likely lead to a non-functional udev installation. + + **WARNING 2** + +If you DO NOT want the "predictable interface naming" of newer versions +of udev and instead prefer the old style (e.g. "eth0"), there are several +options available. + +The simplest is to pass 'net.ifnames=0' on the kernel command line. + +See the wiki for more information: +https://wiki.gentoo.org/wiki/Udev#Optional:_Disable_or_override_predictable_network_interface_naming. + Rationale The integration of udev into the systemd git repo introduced numerous
[gentoo-commits] data/gentoo-news:master commit in: 2021-11-23-mariadb-database-restore-maybe-required/
commit: 3f0ab364ee209797955b6a2212d09e2be944562c
Author: Thomas Deutschmann gentoo org>
AuthorDate: Thu Nov 25 03:01:51 2021 +
Commit: Thomas Deutschmann gentoo org>
CommitDate: Thu Nov 25 20:51:28 2021 +
URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=3f0ab364
2021-11-23-mariadb-database-restore-maybe-required: add item
Bug: https://bugs.gentoo.org/825234
Signed-off-by: Thomas Deutschmann gentoo.org>
...-mariadb-database-restore-maybe-required.en.txt | 45 ++
1 file changed, 45 insertions(+)
diff --git
a/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt
b/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt
new file mode 100644
index 000..c977ae7
--- /dev/null
+++
b/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt
@@ -0,0 +1,45 @@
+Title: Full MariaDB database restore maybe required
+Author: Thomas Deutschmann
+Posted: 2021-11-23
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: dev-db/mariadb
+Display-If-Installed: sys-cluster/galera
+
+On 2021-11-21, keywords for dev-db/mariadb:10.6 were removed to
+address a file collision with dev-db/mariadb-connector-c. This
+unintentionally triggered a version downgrade for users who had
+successfully upgraded to dev-db/mariadb:10.6 already. [Link 1].
+
+However, downgrades are not supported in MySQL/MariaDB [Link 2].
+
+In case you already fully upgraded to MariaDB 10.6 (which includes
+executing mysql_upgrade command) and unintentionally downgraded your
+MariaDB instance afterwards during the time window when keywords were
+removed, you maybe experiencing different problems:
+
+At best, your unwanted downgraded MariaDB instance prevented startup
+so all you have to do is upgrade to MariaDB 10.6 again to resume
+services.
+
+In case previous MariaDB version was able to start, you are encouraged
+to do a full backup as soon as possible using mysqldump command and
+manually restore each database ("logical downgrade") to prevent any
+data corruption.
+
+Depending on used feature set and from which version you upgraded,
+it is maybe required to do a full restore from a previous backup before
+MariaDB 10.6 upgrade to restore services and prevent any data loss or
+future runtime errors.
+
+In case you are using MariaDB in a cluster and/or Galera setup you
+probably have to rebuild the entire cluster in case the upgrade to
+MariaDB 10.6 was already replicated (using pt-table-checksum from
+dev-db/percona-toolkit can help you to validate your cluster).
+
+Keep in mind that due to the downgrade, point-in-time recovery may
+not be available to the extent that you are used to.
+
+Link 1: https://bugs.gentoo.org/825234
+
+Link 2:
https://mariadb.com/kb/en/downgrading-between-major-versions-of-mariadb/
[gentoo-commits] data/gentoo-news:master commit in: 2021-07-23-libxcrypt-migration/
commit: 4cd7ab13760667cc70b151cfb592ef9868dcba70 Author: Sam James gentoo org> AuthorDate: Thu Nov 25 00:49:07 2021 + Commit: Sam James gentoo org> CommitDate: Thu Nov 25 00:49:07 2021 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=4cd7ab13 2021-07-23-libxcrypt-migration: delete older version of libxcrypt news item We've updated the "in stable" one (the newer news item) a few times so having this one around is confusing. Bug: https://bugs.gentoo.org/809410 Bug: https://bugs.gentoo.org/699422 Signed-off-by: Sam James gentoo.org> .../2021-07-23-libxcrypt-migration.en.txt | 65 - .../2021-07-23-libxcrypt-migration.ru.txt | 67 -- 2 files changed, 132 deletions(-) diff --git a/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.en.txt b/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.en.txt deleted file mode 100644 index 8249198..000 --- a/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.en.txt +++ /dev/null @@ -1,65 +0,0 @@ -Title: migrating from glibc[crypt] to libxcrypt in ~arch -Author: Andreas K. Hüttel -Author: Sam James -Posted: 2021-07-23 -Revision: 1 -News-Item-Format: 2.0 - -The implementation of libcrypt.so within glibc has been deprecated -for a long time and will be removed in the near future. - -For this reason, we are following other distributions (where -this has been tested for years already) and switching to the -external libxcrypt implementation, starting with ~arch -installations. - -This will be a regular update, and in nearly all cases you -will not have to take any action and not observe any problems. - -We do recommend, however, that your system is *fully* up -to date first. This is a standard recommendation but in this -specific case, it is useful to have a simplified depgraph -to ensure that Portage is able to smoothly calculate -an upgrade path. - -That is, please take the opportunity to fully upgrade your -systems now, before the migration occurs, to simplify matters. - -This change will occur on 2021-07-14 for ~arch users. Stable -users will update at a later date. - -If for whatever reason you do *not* wish to switch now - -which is only delaying the inevitable - you -need to take the following steps: -* unmask and enable the crypt USE flag of sys-libs/glibc -* mask the system USE flag of sys-libs/libxcrypt -* mask >=virtual/libcrypt-2 - -If you wish to manually migrate now, there are a series -of steps described on the wiki (see below), but the outline is: -* unforce the crypt USE flag of sys-libs/glibc and disable it -* unmask the system and split-usr (if applicable) USE flag of sys-libs/libxcrypt -and enable it -* unmask ~virtual/libcrypt-2 - -Please note that if you last changed your password before ~2008, -it may be using md5crypt or similar other weak mechanisms in /etc/shadow; -a bug in PAM [0][1] may mean that you were unable to login. We recommend -using "passwd" to change/refresh your password so it is using modern -methods. A new version of PAM has been added to the tree to resolve this issue. - -In some cases, Portage may schedule a rebuild of certain packages in an -incorrect order [2]. If building a package fails, please try upgrading -libcrypt and libxcrypt first: - -# emerge -v1 virtual/libcrypt sys-libs/libxcrypt - -And then continue the world upgrade with Portage's "--keep-going=y". - -For more information or troubleshooting tips, please see: -* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation -* https://bugs.gentoo.org/699422 - -[0] https://bugs.gentoo.org/802267 -[1] https://bugs.gentoo.org/802807 -[2] https://bugs.gentoo.org/802210 diff --git a/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.ru.txt b/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.ru.txt deleted file mode 100644 index 0aa0b34..000 --- a/2021-07-23-libxcrypt-migration/2021-07-23-libxcrypt-migration.ru.txt +++ /dev/null @@ -1,67 +0,0 @@ -Title: Миграция в ~arch с glibc[crypt] на libxcrypt -Author: Andreas K. Hüttel -Author: Sam James -Translator: Alexey Sokolov -Posted: 2021-07-23 -Revision: 1 -News-Item-Format: 2.0 - -Реализация библиотеки libcrypt.so в glibc давно устарела и скоро -будет удалена. - -Прочие дистрибутивы годы назад уже переключились на внешнюю -реализацию под названием libxcrypt. Мы решили последовать их примеру -и тоже переключиться на libxcrypt. Вначале изменения затронут системы -на ~arch. - -Это будет обычное обновление, и, скорее всего, вам не нужно будет -предпринимать никаких действий, и проблем возникнуть не должно. - -Однако, мы рекомендуем сперва *полностью* обновить систему. -Это стандартная рекомендация, но в этом конкретном случае -более простой граф зависимостей поможет portage вычислить -порядок обновлений. - -Так что, чтобы упростить процесс обновления, пожалуйста, -обновите систему сейчас, до начала самой миграции. - -Для пользователей ~arch
[gentoo-commits] data/gentoo-news:master commit in: 2021-09-29-possible-failure-to-preserve-libraries/
commit: ef0cfc2c0e68299ddfa355732c76cf7d9ed83fcb Author: Sam James gentoo org> AuthorDate: Mon Nov 22 06:30:45 2021 + Commit: Sam James gentoo org> CommitDate: Mon Nov 22 06:31:58 2021 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=ef0cfc2c 2021-09-29-possible-failure-to-preserve-libraries: mention when it's ok to skip -e It should be okay to skip -e @world and instead only rebuild libraries + their consumers in some cases. Bug: https://bugs.gentoo.org/811462 Signed-off-by: Sam James gentoo.org> .../2021-09-29-possible-failure-to-preserve-libraries.en.txt | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt b/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt index 7154bc4..68aa6af 100644 --- a/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt +++ b/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt @@ -93,7 +93,12 @@ Step 3. Given that there are possible other side-effects of the corruption/bug, Note that binary packages may need to be discarded given they may contain corrupt metadata. - If no libraries were broken, it is likely safe to skip this step. + If no libraries were broken, it is likely safe to skip this step. It + should be sufficient, for resource-constrained machines, to simply + rebuild any broken libraries and their consumers (reverse-dependencies): + revdep-rebuild may help you do this. + + (If you do not know what that means, please proceed with Step 3.) Please see the wiki [0] for a full description of the background of this problem and handling corner cases such as e.g. already
[gentoo-commits] data/gentoo-news:master commit in: 2021-10-18-libxcrypt-migration-stable/
commit: 8f2ad6dd0515374e473b79d6f6cbc32ac8050680 Author: Sam James gentoo org> AuthorDate: Mon Nov 22 06:14:07 2021 + Commit: Sam James gentoo org> CommitDate: Mon Nov 22 06:14:07 2021 + URL:https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=8f2ad6dd 2021-10-18-libxcrypt-migration-stable: mention unmasking libcrypt:0/1 for delay If users want to delay the upgrade (please don't do this though), they will (shortly) need to unmask virtual/libcrypt:0/1 too. Bug: https://bugs.gentoo.org/699422 Bug: https://bugs.gentoo.org/809410 Signed-off-by: Sam James gentoo.org> .../2021-10-18-libxcrypt-migration-stable.en.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt b/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt index feddaf6..1b80f95 100644 --- a/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt +++ b/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt @@ -44,6 +44,7 @@ need to take the following steps: * unmask and enable the crypt USE flag of sys-libs/glibc * mask the system USE flag of sys-libs/libxcrypt * mask >=virtual/libcrypt-2 +* unmask virtual/libcrypt:0/1 If you wish to manually migrate now, there are a series of steps described on the wiki (see below), but the outline is:
