Dear Obarun Community,
A new release of pacopts is available in the obextra repository. pacopts is rewritten
in Python: it reads the pacman databases through pyalpm, talks directly to the AUR, no longer
needs cower nor expac, and can now build any PKGBUILD in a rootless sandbox without
installing anything on your host. Below is what you have to do to upgrade, followed by an
overview of the changes.
Dear Obarun Community,
New releases of 66 (0.9.2.0) and 66-tools (0.3.0.0) are available in the Obarun
testing repositories. 66 becomes more predictable and easier to debug, and 66-tools brings
a web interface to drive 66 from a browser, a 66-dbus-launch without any external D-Bus
library and a deeply reviewed 66-ns. Below is what you have to do to upgrade,
followed by an overview of the changes.
With 0.9.0.0, 66 no longer links against skalibs, s6 or execline. The scanner, the supervisor, the logger, the fd holder and the privilege dropper are now native programs of the suite. Leaving the foundation a project was built on is not a decision to make lightly, so here is why. The tipping point was the event system: implementing it correctly is what made it clear that going further meant leaving s6. To see what it is for, start with a very ordinary problem that service managers usually solve with glue.
Dear Obarun Community,
Obarun install images are no longer built by hand. A GitLab pipeline now builds them on its own, on the first day of every month, and publishes them without anyone having to press a button. The download page always points at the newest image, so there is nothing to look up and no stale link to avoid.
Dear Obarun Community,
Obarun has a new installer. It is called obinstall, it is available in [obextra], and it
replaces the historical obarun-install and its companion obarun-install-themes. It offers two
ways to install the system: a graphical wizard that runs in a browser, and a declarative command
line driven by a single TOML file.
The new Obarun ISOs already carry this change. They are built by obinstall itself, they ship it, and they start it for you: pick Install in the boot menu, or open the installer from the live desktop once you are logged in.
Dear Obarun Community,
The new release of 66 is available in the Obarun testing repositories. This post is not a
description of what changed inside 66, the changelog
already does that. It tells you what you have to do to bring an existing system to
0.9.1.0, in the order it has to be done.
Dear Obarun Community,
The [obcommunity] repository is now signed: both its database and its packages
can be cryptographically verified, just like the official Obarun repositories.
Dear Obarun Community,
The xlibre-server, xlibre-input and xlibre-video packages have been moved from
the [obcommunity] repository to the official [obextra] repository. This marks an
important step in Obarun's transition away from Xorg.
Dear Obarun Community,
Documentation for every Obarun program now lives under a single dedicated domain: docs.obarun.org. More importantly, it now updates itself.
Dear Obarun Community,
The build and deployment pipeline behind every Obarun package — [obcore], [obextra], [observice]
and [obcommunity] — has been rebuilt from the ground up. The new tool is called apkg. It
replaces the legacy apkg-*.sh bash scripts that have been quietly orchestrating Obarun package
releases for more than 3 years. This post explains what changed, what it means for maintainers, and — most
importantly — why contributing a package to [obcommunity] is now drastically easier than it used
to be.