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.
Dear Obarun Community,
The release of 66 version 0.8.2.0 marks a significant step forward for the Obarun service management system. This update introduces powerful new features, critical bug fixes, and performance improvements designed to offer greater control, reliability, and ease of use for system administrators and users. Below is an overview of the key changes to help make the most of this release.
Dear Obarun users, all required packages for 66, updated for the new 0.8.0.0 release, have been moved from the testing repository to their respective stable counterparts. Archives of previous versions can be found in the [obarchive] repository on the packages page.
If you haven’t completed the migration yet, follow the instructions below.
Following our previous announcement, we’re pleased to officially present the new Obarun website! The old site, which had become outdated, unattractive, and buggy, no longer met our users' needs. This redesign brings improved clarity, accessibility, and efficiency, making it easier to navigate and offering a more welcoming experience.