Updates and packages
An installed UFLinux system is an Alpine system. Updates are ordinary apk operations
against three kinds of repository: the signed UFLinux repository carrying the custom
packages, the matching Alpine stable main and community branches, and
UFLinux’s smaller apps repository.
doas apk updatedoas apk upgradeThe UFLinux repository for the current baseline is:
https://repo.uflinux.org/apk/v3.24/uflinuxAlongside it, the apps repository publishes uflinux-files, the desktop’s file manager:
https://apps-repo.uflinux.org/apk/v3.24/uflinux-appsIt has its own signing key, uflinux3.ec384.pub, which the uflinux-release package
installs, and it only indexes x86_64, aarch64, ppc64le and riscv64. Because an
unreachable repository line makes every later apk operation fail, the line is written
only on those four architectures — x86 and armv7 systems ship without a graphical
file manager rather than with an unsatisfiable dependency.
Staying on a supported combination
Section titled “Staying on a supported combination”UFLinux pins one Alpine release. Do not mix edge packages or another Alpine release
branch into the system — the desktop stack is built and tested against one branch, and
mixing pulls in libraries it was not validated with. Moving to a newer Alpine branch
means an explicitly tested UFLinux release for that branch, not a manual edit of
/etc/apk/repositories.
After upgrading, review .apk-new files if you have edited system defaults. UFLinux
preserves local edits during upgrades, and .apk-new holds the packaged version of a
file you had changed.
Where configuration lives
Section titled “Where configuration lives”| Location | Contents |
|---|---|
/etc/xdg |
Packaged desktop defaults |
~/.config/labwc/ |
Personal compositor overrides |
~/.config/uflinux/ |
UFLinux Settings, taskbar and Start menu preferences |
/etc/tlp.d/ |
Power profile drop-ins |
/etc/uflinux/power.json |
Physical power-button policy (root-owned) |
The desktop shell uses its packaged defaults when no user file is present, so a personal
config replaces the packaged panel layout rather than extending it. Pinned taskbar
favourites live in $XDG_CONFIG_HOME/uflinux/taskbar.json.
Rolling a package back
Section titled “Rolling a package back”Inspect what is available before choosing:
doas apk policy uflinux-settingsThen install the matching older version explicitly, including its dependencies. For a larger rollback, use the immutable signed repository snapshot published with that UFLinux release.
Installed XFS roots have no automatic filesystem snapshots, so a package rollback is the intended tool — not a snapshot restore.
Signing
Section titled “Signing”UFLinux signs packages with an EC P-256 or P-384 key published under the stable
filename uflinux.ec.pub. apk v2 has no ECDSA signature stream, so the signature travels
in the SHA-256 stream and the stream name RSA256 describes the digest, not the
algorithm. The apps repository is signed by a separate key, uflinux3.ec384.pub. If you
maintain your own fork, see Maintenance.
Derived from docs/installing.md inUFlinux-project/uflinux3(b4f4817). Report documentation problems inUFlinux-project/docs.