Skip to content

pierres/archiso-manager

Folders and files

NameName
Last commit message
Last commit date

Latest commit

4eed11f · Apr 1, 2025

History

83 Commits
Apr 1, 2025
Jun 1, 2024
May 1, 2024
Oct 1, 2022
Dec 1, 2024
Nov 1, 2024

Repository files navigation

Arch Linux ISO release utilities

Prerequisites

Install required packages

pacman -Syu --needed just archiso rsync mktorrent

Configure your signing keys

Create an .env file containing your GPG key. Example:

GPGKEY='3E80CA1A8B89F69CBA57D98A76A5EF9054449A5C'
GPGSENDER='Pierre Schmitz <[email protected]>'
ARCHIVEDIR='/home/pierre/data/archlinux/iso/'

In addition to this you need a key pair which is accepted by PIXE. The files need to be named codesign.crt and codesign.key.

Creating a new ISO image

  • Run just all to create all artifacts. This will create the ISO image and tar files.
  • Optionally run just run-iso to test the ISO with Qemu.
  • Upload the release to repos.archlinux.org with just upload-release. This will just upload the artifacts into a temporary directory but not publish them.
  • Log into archlinux.org/login and create a new release entry using the Archweb Admin. Use the information shown by the build process or manually re-run just show-info. It is good practice to keep the field Available unchecked until the ISO image has been published and most mirrors had time to sync it. You may use just copy-torrent to copy the base64 encoded torrent file into your clipboard.
  • As we only like to keep the last three ISO releases remove the oldest one from Archweb Admin. Then remove the actual files from the mirror by running just remove-release <version>.
  • To actually publish a release and have it sync to mirror run just publish.
  • Optionally run just archive to move build artifacts into the configured ARCHIVEDIR.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks