arrans-overlay - News Dashboard

Subscribe to the News feed: RSS | Atom

Jules retirement: clients and CLI removed

Posted: 2026-11-10 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.

Removal of app-misc/maid-appimage

Posted: 2026-11-10 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

Beeper AppImage removed; FlatPark Flatpak recommended

Posted: 2026-11-05 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.

More... (Archive)