News Dashboard

Subscribe to the News feed: RSS | Atom

Removal of app-misc/maid-appimage

Posted: 2026-11-10 in arrans-overlay by Arran
The app-misc/maid-appimage package and its automatic update workflow have been retired from this overlay.

The maintainer no longer uses Maid, and the package update pipeline has not been maintained or independently checked for some time. To avoid presenting an unverified package as maintained, new Maid AppImage updates will no longer be supplied from this overlay.

Existing installed versions are not automatically removed. The upstream project's current 3.x release line focuses on Android rather than Linux. No verified Maid Flatpak replacement was found at the time of retirement. Older upstream Linux AppImages may remain available in its historical releases, but they are not maintained or updated by this overlay. Users retaining Maid should review upstream's available platforms and releases or maintain a separate ebuild.

To remove the installed package if it is no longer needed:

emerge --deselect app-misc/maid-appimage
emerge --ask --depclean app-misc/maid-appimage

Jules retirement: clients and CLI removed

Posted: 2026-11-10 in arrans-overlay by Arran
Google announced on 29 October 2026 that its Jules asynchronous coding service will wind down on 31 December 2026. Users can finish Jules sessions until 11 November 2026. After 11 November, Jules will be read-only until the final shutdown.

Consequently, this overlay is retiring the following clients and their automatic update workflows:

  app-misc/kjules
  app-misc/flutter-jules
  app-misc/flutter-jules-bin
  dev-util/jules-bin
Before shutdown, export any Jules settings, scheduled tasks, environment variables, setup scripts, memories, and session history you wish to keep. Code, branches and pull requests already stored on GitHub remain there. Keep exports containing environment variables or other secrets secure.

If you installed these packages, remove them from the world set and uninstall them when no longer needed:

  emerge --deselect app-misc/kjules app-misc/flutter-jules app-misc/flutter-jules-bin dev-util/jules-bin
  emerge --ask --depclean
Google mentions Antigravity as part of its ongoing agentic development work, but has not announced automatic migration of Jules data to it.

Official announcement and export information: https://jules.google/docs/changelog/2026-10-29

This notice was drafted for Arran with AI assistance.

Beeper AppImage removed; FlatPark Flatpak recommended

Posted: 2026-11-05 in arrans-overlay by Arran
I am removing net-im/beeper-appimage from this overlay, including its automatic update workflow. I recommend installing Beeper as a per-user Flatpak from FlatPark instead.

FlatPark's Beeper package is community-maintained, not an official Automattic Flatpak. Its application ID is com.automattic.Beeper: https://flatpark.org/apps/com.automattic.Beeper/

Add FlatPark explicitly with the following settings so it is not enumerated in ordinary app listings or used for dependency resolution:

  flatpak --user remote-add \
    --if-not-exists \
    --no-enumerate \
    --no-use-for-deps \
    flatpark \
    https://dl.flatpark.org/flatpark.flatpakrepo
Install Beeper by explicitly naming the remote:

  flatpak --user install flatpark com.automattic.Beeper
If you do not already have Flathub available for per-user runtime dependencies, add it with:

  flatpak --user remote-add --if-not-exists flathub \
    https://dl.flathub.org/repo/flathub.flatpakrepo
To remove the old ebuild installation after migrating, run:

  emerge --deselect net-im/beeper-appimage
  emerge --ask --depclean net-im/beeper-appimage
The FlatPark remote flags do not prevent explicitly installing or updating applications from FlatPark. This notice was drafted for Arran with AI assistance.

KDE Plasma 6.8 retires X11 session

Posted: 2026-10-15 in gentoo by Andreas Sturmlechner
Support for starting X11 sessions is going to be retired with the upcoming Plasma 6.8 release[1]. While stabilisation is still a few months out, users of testing keywords will get it now.

This is in conjunction with full adoption of the newer Wayland system, which offers better support for modern screens and graphics cards, and is actively developed. The small number of individual applications that still require X11 will continue to work via the XWayland compatibility layer. KDE applications will continue to support X11 for the foreseeable future.

KDE Plasma 6.7 is the final release[2] to support X11. We intend to keep it available in ::gentoo until at least 2027-01-31, but without any commitment beyond that.

Users must make use of this time to either move to Plasma's Wayland session or find an alternative. And while the 6.8 feature development window is closed, late upstream feedback may still end up in your corner cases[3] being fixed by Plasma 6.9.

Packages discontinued in KDE Plasma 6.8:

  • kde-plasma/kwin-x11
  • kde-plasma/kgamma [4]
  • kde-plasma/plasma-login-sessions (obsolete, consumed by plasma-workspace)
  • kde-plasma/wacomtablet [5] (obsolete for configuring xf86-input-wacom)




Notes for the common case of users upgrading ============================================

For users of a Plasma profile, no specific upgrade steps are necessary. After an upgrade to 6.8, there will be no more Plasma X11 session available, only Wayland. It may be a good time to revisit the Gentoo KDE Wiki[5], anyway.

Plasma profile will simultaneously switch SDDM, the current default login manager for Plasma, to Wayland via USE="kwin" in gui-apps/sddm-gentoo-config which automatically sets up /etc/sddm.conf.d/01gentoo.conf accordingly.

After that, there may no longer be anything left depending on xorg-server, so it could be cleaned up in a subsequent emerge --depclean:

  emerge --depclean --pretend xorg-server xorg-drivers
*Please note*: This does not imply any global changes to X USE flag. Disabling X globally is not necessary for this change, and we advise against doing so. It can cause all sorts of unintended side effects from historically ambiguous usage - besides, not every "X11" library is obsolete in Wayland.



Notes for users wishing to remain on X11-capable Plasma =======================================================

In order to temporarily (see above) stay on Plasma 6.7 as 6.8 becomes available on your system, use the resulting list of the following command in order to mask[7] the upgrade:

  for p in `qlist -IC kde-plasma/`; do echo ">=${p}-6.8"; done
For SDDM to keep using X11, set USE="-kwin" on gui-apps/sddm-gentoo-config[8].



[1] https://kde.org/announcements/plasma/6/6.8.0/ [2] https://community.kde.org/Schedules/Plasma_6#Future_releases [3] https://community.kde.org/Plasma/Wayland_Known_Significant_Issues [4] https://blog.davidedmundson.co.uk/blog/wayland-and-kgamma/ [5] https://userbase.kde.org/Kde_wayland_for_artists#Support_for_Graphics_Tablets [6] https://wiki.gentoo.org/wiki/KDE [7] https://wiki.gentoo.org/wiki/Knowledge_Base:Masking_a_package [8] https://wiki.gentoo.org/wiki//etc/portage/package.use

pf-sources-extended now carries LTS kernels only

Posted: 2026-10-07 in stuff by Ivan S. Titov
sys-kernel/pf-sources-extended now carries only the LTS kernel branches:

  6.1_p6-r3, 6.6_p6-r3, 6.12_p4-r3, 6.18_p6-r3
The ebuilds for 6.2, 6.3, 6.4, 6.5, 6.7, 6.8, 6.9, 6.10, 6.11, 6.13, 6.14, 6.15, 6.16, 6.17 and 6.19 have been removed; 7.0 was removed on 2026-05-15. These branches are end-of-life upstream, so linux-stable no longer fixes them, and tracking linux-stable is the point of this package.

== What to do ==

An installed source tree stays in /usr/src/ until you unmerge it, but it can no longer be reinstalled and gets no further fixes. Move to one of the LTS slots above; 6.18 is the newest. These ebuilds carry KEYWORDS="" and must be accepted explicitly in /etc/portage/package.accept_keywords, for example:

  =sys-kernel/pf-sources-extended-6.18_p6-r3 **
Emerge it, build and boot the new kernel, then unmerge the old source tree:

  emerge --unmerge =sys-kernel/pf-sources-extended-X.Y_pZ
Outside this package, sys-kernel/pf-sources carries the full pf-kernel patchset, and ::gentoo's sys-kernel/gentoo-sources tracks linux-stable without the pf delta.

LocalAI packages reorganized

Posted: 2026-10-04 in local-ai by Plamen K. Kosseff
The LocalAI packages of this overlay have been renamed and recategorized. Package moves migrate installed systems and world entries automatically:

sci-ml/local-ai            -> sci-ml/localai
app-local-ai/backends-meta -> www-apps/localai-server
app-local-ai/<backend>     -> localai-backend/<backend>
The two top-level names also swap roles. sci-ml/localai - the atom your world file now holds - is a meta package: it installs the server (www-apps/localai-server) plus the inference backends selected by its USE flags, which all default to on. The server package itself no longer references any backend package. Removing sci-ml/localai from the world file lets emerge --depclean remove the server and every backend in one sweep.

If you run a full LocalAI stack, no action is needed: the next world update follows the moves and keeps everything installed.

If you run the server WITHOUT backends, pick one before your next world update:

  • keep sci-ml/localai in world and disable its backend flags, e.g. echo "sci-ml/localai -*" >> /etc/portage/package.use/localai


  • or anchor the server directly: emerge --deselect sci-ml/localai emerge --noreplace www-apps/localai-server


Otherwise the meta package's default USE flags will schedule every backend for installation.

If the update aborts with file collisions on the server's files (/usr/bin/local-ai and the service files), unmerge the old server install - it carries the meta's new name in the package database - while keeping the world entry, then run the update again:

emerge -C --deselect=n sci-ml/localai
emerge -uDN @world
This is safe: the update reinstalls the server and the backends immediately, and /var/lib/local-ai (models, state) is untouched.

Disabling the Steam runtime is no longer supported

Posted: 2026-10-04 in steam-overlay by James Le Cuirot
You currently have Valve's Steam client installed with its runtime disabled. Disabling the runtime traditionally told Steam to use libraries from the host instead. This has never been supported by Valve, and it is no longer very effective. It has already long been the case that the client will use host libraries anyway, only falling back to the runtime when a host library a missing. Almost all games, even very old native ones, are now run in a container by default, where it is not possible to disable the runtime.

As such, steam-overlay is now shifting to a supported setup by forcibly enabling the `steamruntime` USE flag. The intention is to keep the USE flag and the associated esteam package around for 2 months until 2026-12-04. With these gone, most of the steam-overlay packages will be largely redundant, so the steam-launcher and extest packages will migrate to the main Gentoo repository, and the overlay will be retired.

If you used esteam to remove bundled libraries from some games, then you may need to restore those libraries for each game by navigating to Properties -> Installed Files -> Verify integrity of game files.

If you want to run some games directly on the host with host libraries preferred, you can still do so by selecting Legacy Steam Runtime under Properties -> Compatibility, but it is your responsibility to install those libraries.

Do not assume that the older Steam runtimes used by older games only have ancient versions of libraries. Obviously, compatibility needs to be maintained, as that is the point of the runtime, but while writing this, I found that the "Scout" runtime had the same version of libSDL2 as Gentoo and a newer version of libSDL1.2 than Gentoo.

It is worth bearing in mind that, despite the success of the Steam Deck, relatively few games are Linux native. New native games tend to be built on large engines like Unity or Unreal, and if these do use traditional free software libraries at all, they are statically linked.

Many older native games have been left to rot while their Windows counterparts have continued to receive updates, making Proton the more sensible choice in these cases. With Wine and Proton now being able to run 32-bit binaries on a purely 64-bit Linux system, you may decide to drop 32-bit support from your system entirely once the 64-bit Steam client goes out of testing, which will hopefully be soon.

If Steam no longer meets your needs, you may want to consider Lutris instead, but it has broadly the same options, such as using host libraries, its own runtime, or Steam's "Sniper" runtime in a container. It does nothing to ensure you have the right host libraries installed.

Please give any feedback at: https://github.com/anyc/steam-overlay/issues/386

zed now builds releases; patched one is zeo

Posted: 2026-10-01 in bentoo by Lucas Couto
Until now app-editors/zed in this overlay was a daily snapshot of Zed's main branch carrying the bentoo patch series: the Claude agent integrations (USE claude-agent-acp-plus, claude-agent-acp-tui, claude-code-ide) and the agent-panel changes that ride on them.

That package is split in two:

  • app-editors/zed builds upstream's tagged releases from source, with no patches -- the source counterpart of app-editors/zed-bin. Stable versions (1.22.0) and pre-releases (1.23.1_pre) are both offered.
  • app-editors/zeo is the snapshot plus the patch series, as it was, with Zed's identity replaced by Zeo's: the command is "zeo", settings live in ~/.config/zeo/, and it opens zeo:// links (zed:// still works). app-editors/zeo-bin is the same build, prebuilt for x86-64-v3 CPUs (Haswell, Zen 1 and newer).


Only one of zed, zed-bin, zeo and zeo-bin can be installed at a time.



Keeping the patched editor ==========================

1) Switch packages. Portage resolves the blocker by unmerging zed:

     emerge --ask app-editors/zeo      # or app-editors/zeo-bin
     emerge --ask --deselect app-editors/zed
2) Move per-package configuration from app-editors/zed to
 app-editors/zeo in /etc/portage (package.use, package.env,
 package.accept_keywords).
3) Copy your settings once, if ~/.config/zeo does not exist yet (this
 overwrites it). Zeo does not read Zed's directories:

     cp -a ~/.config/zed/. ~/.config/zeo/
     cp -a ~/.local/share/zed/. ~/.local/share/zeo/

Staying on plain Zed ====================

The installed snapshot (1.24.0_pre20261001) is numbered above the newest release, so the next world update shows a DOWNGRADE of app-editors/zed to a release. That is expected. The USE flags claude-agent-acp-plus, claude-agent-acp-tui and claude-code-ide no longer exist on zed; drop them from package.use.

Ceph 20.2.4 requires manual CephX key rotation

Posted: 2026-09-12 in gentoo by Shiz01
Ceph 20.2.4 (Tentacle) is a hotfix release addressing four CVEs [1]. The fix for CVE-2025-30156 introduces a new CephX key type, aes256k, and cluster operators must rotate and client keys by hand as part of the upgrade.

Read the upstream announcement [1] and the CephX key upgrade procedure [2] BEFORE you start. If you deploy Ceph use cephadm or Rook you can skip key rotation instructions and only check client support.

The CVEs fixed in this release are:

CVE-2025-30156  Authentication bypass in CephX caused by misuse
                of AES-CBC.
CVE-2026-39944  Improper verification of a cryptographic
                signature in the RGW STS session tokens.
CVE-2026-50152  Improper authorization in the Ceph Monitor
                subscription handler.
CVE-2026-54330  Improper SigV4 signature verification in RGW.
Manual steps required =====================

1. If you run RGW multisite, set "rgw_sigv4_insecure" to true on
 every cluster BEFORE you begin.  The multisite REST client would
 fall back into old insecure behaviour and would emit SigV4
 requests that the fixed verifier rejects.
 After ALL clusters upgrade, set this option back to false.
2. Upgrade the daemons in the usual Ceph order: mon's, then
 mgr's, then OSDs, then MDSs, then the gateways and clients.
3. Expect six new health warnings and errors about insecure CephX
 keys after the upgrade [3].  This is normal; they clear as you
 work through the rotation.
4. Rotate the keys of all daemons and clients to aes256k, following
 the instructions [2].
5. Kernel clients (kernel CephFS and krbd) only support aes256k
 starting with Linux 7.0.  Check your kernel version before you
 rotate any key that a kernel client uses, or that client will
 lose access to the cluster.
6. Secrets kept in the mon config-key store may have been
 exposed through CVE-2026-50152.  Upstream guidance on rotating
 them is still pending; assess your own exposure and rotate what
 you can in the meantime.
A cluster left with old keys stays vulnerable to the authentication bypass, so do not stop halfway through the rotation.

[1] https://ceph.io/en/news/blog/2026/v20-2-4-v19-2-6-combo-released/ [2] https://docs.ceph.com/en/latest/rados/configuration/auth-config-ref/index.html#upgrading-and-rotating-cephx-keys [3] https://docs.ceph.com/en/latest/rados/operations/health-checks/index.html#auth-insecure-keys-creatable

More... (Archive)