Ryan Hughes
f8010a355a
repo-add --new skips updating entries that are already in the db, so when the omarchy-* packages are rebuilt in place (new content, same filename, because pkgver is constant) the persistent cache's offline.db.tar.gz kept the OLD size/checksum entries. Pacman then read the stale db size and rejected the new file with 'Exceeded the maximum allowed file size'. Delete the db files and let repo-add regenerate them fresh — slower but deterministic, and 'offline.db.tar.gz' is small to rebuild even for the full ~600 package set.
Omarchy ISO
The Omarchy ISO streamlines the installation of Omarchy. It includes the Omarchy Configurator as a front-end to archinstall and automatically launches the Omarchy Installer after base arch has been setup.
Downloading the latest ISO
See the ISO link on omarchy.org.
Creating the ISO
Run ./bin/omarchy-iso-make and the output goes into ./release. You can build from your local $OMARCHY_PATH for testing by using --local-source or from a checkout of the dev branch (instead of master) by using --dev.
Environment Variables
You can customize the repositories used during the build process by passing in variables:
OMARCHY_INSTALLER_REPO- GitHub repository for the installer (default:basecamp/omarchy)OMARCHY_INSTALLER_REF- Git ref (branch/tag) for the installer (default:master)
Example usage:
OMARCHY_INSTALLER_REPO="myuser/omarchy-fork" OMARCHY_INSTALLER_REF="some-feature" ./bin/omarchy-iso-make
Testing the ISO
Run ./bin/omarchy-iso-boot [release/omarchy.iso].
Signing the ISO
Run ./bin/omarchy-iso-sign [gpg-user] [release/omarchy.iso].
Uploading the ISO
Run ./bin/omarchy-iso-upload [release/omarchy.iso]. This requires you've configured rclone (use rclone config).
Full release of the ISO
Run ./bin/omarchy-iso-release VERSION to create, test, sign, and upload the ISO in one flow. Add --rc to release an RC build instead.