Search Portage & Overlays:

Gentoo Repository News

Deprecation of legacy X11 input drivers - 03/04/2020 00:00 GMT

The Gentoo X11 Team is announcing the deprecation and future removal of
the legacy X11 input drivers x11-drivers/xf86-input-mouse and
x11-drivers/xf86-input-keyboard. As of 2020-05-01 those input drivers
will be masked for removal.

These drivers have been deprecated for many years, first by
xf86-input-evdev and then by xf86-input-libinput.

The only use for those drivers remain in deployments which intentionally
opt-out of using udev, as both evdev and libinput require udev during
runtime, however given that upstream has already removed the Linux
support from xf86-input-keyboard, future X11 releases will no longer
support xf86-input-keyboard on Linux rendering those installation
infeasible to use without udev.

In order to ensure frictionless upgrade path for future X11 releases, we
have decided to deprecate those drivers that are not in active use by
pretty much any installation of Gentoo.

No action is required from end-users who are already using libinput (or
evdev). To check which driver is in use, one can use

    $ grep 'Using input driver' ~/.local/share/xorg/Xorg.0.log

for the systems running xorg-server as regular user (-suid
+elogind/+systemd) or by running

    # grep 'Using input driver' /var/log/Xorg.0.log

for those running xorg-server as root.

If however neither libinput or evdev is in use, one should append
'libinput' to the INPUT_DEVICES variable inside /etc/portage/make.conf
while removing 'keyboard' and 'mouse' if present, then update @world
with new USE flags

    # emerge -N @world

Posted By: Piotr Karbowski

K8s Moving to a Single Package - 03/04/2020 00:00 GMT

Formerly, we packaged kubernetes as seven separate packages:

sys-cluster/kubeadm, sys-cluster/kube-apiserver,
sys-cluster/kube-controller-manager, sys-cluster/kubectl,
sys-cluster/kubelet, sys-cluster/kube-proxy and

Starting with kubernetes 1.18.0, 1.17.5 and 1.16.9, these will be merged
into one package, sys-cluster/kubernetes. The components of this package
which are build and installed will be selectable by use flags.

If you are using 1.16.x or 1.17.x and would like to migrate to the
single package without upgrading, I have also made 1.16.8 and 1.17.4
available in this new package.

Currently, everything is built and installed by default; however, I am
open to changing this if there is a better way to configure the default

Posted By: William Hubbs

Stable ia64 keywords removed - 30/03/2020 00:00 GMT

The Gentoo/IA64 team no longer thinks that the time invested in package
stabilization is warranted for the small number of users on IA64. As a
result, we will drop all "ia64" keywords to "~ia64" on 2020-04-03 and will
add "~ia64" to ACCEPT_KEYWORDS in the profile.

Users need not make any changes to their systems, and the Gentoo/IA64 team
has no plans to remove support for the architecture.

Posted By: Matt Turner

Removing ABI_X86_32 support from virtual/opencl - 09/03/2020 00:00 GMT

From April 2020 onwards virtual/opencl will no longer provide support
for the 32-bit ABI on either multilib amd64 or native x86 systems. The
reason for this is that most modern OpenCL providers currently available
from Gentoo only support the 64-bit ABI anyway. Therefore, we intend
to initially mask:
 - virtual/opencl in x86 profiles,
 - USE=abi_x86_32 for virtual/opencl in all profiles, and
 - USE=opencl in x86 profiles.
and follow up with removal of multilib support and x86 keywords from

Note that this change will only affect the virtual package, i.e. OpenCL
providers which do support ABI_X86_32 will continue to advertise this
capability. Users of such providers who wish to retain 32-bit OpenCL
support are advised to add virtual/opencl to package.provided; see
portage(5) for details.

Posted By: Marek Szuba

OpenSSH 8.2_p1 running sshd breakage - 20/02/2020 00:00 GMT

If sshd is running, and a system is upgraded from
=net-misc/openssh-8.2_p1, any new ssh
connection will fail until sshd is restarted.

Before restarting sshd, it is *strongly* recommended that you test your
configuration with the following command (as root):
    sshd -t

If your system is booted with openrc, use this command (as root) 
to restart sshd:
    rc-service sshd --nodeps restart

If your system is booted with systemd, use this command (as root)
to restart sshd:
    systemctl restart sshd

WARNING: On systemd booted machines with PAM disabled, this command
         will terminate all currently open ssh connections. It is 
         *strongly* recommended that you validate your configuration
         before restarting sshd.

If you are using systemd socket activation for sshd, then no action is

Posted By: Patrick McLean

Python 2.7 went EOL - 07/02/2020 00:00 GMT

Python 2.7 has reached its end-of-life by 2019-12-31.  Python package
upstreams have started removing Python 2 compatibility code from their
packages more aggressively.  This includes common dependencies such as
dev-python/pytest, dev-python/setuptools and dev-python/sphinx.  While
we realize that many packages are still dependent on Python 2, providing
full support for it exceeds our maintenance capabilities.

Upstream is planning to make one more release of dev-lang/python:2.7
in April 2020.  We are going to continue maintaining and patching
the interpreter for as long as it is feasible, most likely even after
all Python 2 packages are gone from Gentoo.

At the same time, we are actively working towards switching
the distribution to Python 3.  Whenever possible, we are removing
Python 2 support from packages.  It will remain available for
the packages missing Python 3 compatibility and their dependencies
for some more time.  However, packages that have little chances of being
ported will eventually be removed.

If you are still using Python 2 for your projects, we strongly recommend
you to migrate away.  For the time being, it is preferable to use
dev-python/virtualenv or a similar solution rather than ebuilds,
to install the dependencies for your projects locally.

Regular Gentoo systems will be migrated off Python 2 gracefully.  It may
be necessary to use --changed-deps or a similar option during system
upgrades whenever they become blocked by Python 2 packages installed

If you wish to remove Python 2.7 entirely sooner, you can try removing
python2_7 from PYTHON_TARGETS.  However, this will require adding
explicit package.use entries if some of the installed packages still
require Python 2.  An example package.use entry follows:

  # disable py2.7 without altering the other flags
  */* PYTHON_TARGETS: -python2_7
  # enable py2.7 for setuptools
  dev-python/setuptools PYTHON_TARGETS: python2_7
  # switch a single-impl package to 2.7
  dev-embedded/libftdi PYTHON_TARGETS: python2_7
  dev-embedded/libftdi PYTHON_SINGLE_TARGET: -* python2_7

Note that package.use entries are not necessary for packages that
support one implementation only (i.e. do not support Python 3 at all).

Posted By: Michał Górny

Stable alpha keywords removed - 23/01/2020 00:00 GMT

The Gentoo/Alpha team no longer thinks that the time invested in package
stabilization is warranted for the small number of users on Alpha. As a
result, we will drop all "alpha" keywords to "~alpha" on 2020-01-25 and will
add "~alpha" to ACCEPT_KEYWORDS in the profile.

Users need not make any changes to their systems, and the Gentoo/Alpha team
has no plans to remove support for the architecture.

Posted By: Matt Turner

Genkernel 4 changed default filenames - 30/12/2019 00:00 GMT

To be consistent with kernel's own naming which allows for easier
matching of kernel/initramfs with kernel files (/lib/modules),
genkernel 4 changed default kernel and initramfs filename:

    kernel-genkernel-%%ARCH%%-%%KV%%      -> vmlinuz-%%KV%%  ->
    initramfs-genkernel-%%ARCH%%-%%KV%%   -> initramfs-%%KV%%.img

Note that in genkernel 4, filenames are fully customizable and that
$ARCH value is now part of $KV value by default.

All bootloaders and utilities like sys-apps/kexec-tools available in
Gentoo repository support the new naming schema.

However, due to lexical ordering, the default boot entry in your boot
manager could still point to last kernel built with genkernel before
that name change, resulting in booting old kernel when not paying
attention on boot.

Posted By: Thomas Deutschmann

sys-boot/raspberrypi-firmware will not install device tree files - 25/11/2019 00:00 GMT

sys-boot/raspberrypi-firmware up to and including version 1.20190709
installed files /boot/*.dtb and /boot/overlays/*. Newer versions will no
longer install these files.

These files will be installed by sys-kernel/raspberrypi-image package.

If you do not use sys-kernel/raspberrypi-image, you need to install
these files according to the method you use to install the kernel. For
installation from source, this can be done with such commands:

    make dtbs
    cp -v arch/arm64/boot/dts/broadcom/*.dtb /boot/
    cp -rv arch/arm64/boot/dts/overlays/ /boot/

This change is being made to enable arm64 users and custom kernels users
to use sys-boot/raspberrypi-firmware package.

Posted By: Andrey Utkin

sys-fs/cryfs-0.10.2 update - 29/10/2019 00:00 GMT

Filesystems created with CryFS 0.9.x are incompatible with the new storage
format. [1] Migration is necessary before mounting with CryFS 0.10 and
possible for old containers going back as far as CryFS 0.9.4. [2]

However, upstream recommend to create new containers with 0.10 to avoid
potential data loss from a failed migration, and in order to benefit from all
performance advantages of the new format.

Before updating, copy all data from cryfs containers to a temporary and secure
location. After the update, move it back into a newly created container. Don't
forget to remove the temporary files afterwards.

Users of KDE Plasma Vaults should follow the same procedure. To check the type
of existing containers, open them using the Vaults widget. It is part of the
path as displayed in dolphin.


Posted By: Andreas Sturmlechner