Skip to content

infradocs: upkeep/images: updates for 2025Q1 images #226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
classabbyamp wants to merge 1 commit into from
Closed

infradocs: upkeep/images: updates for 2025Q1 images #226

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions docs/src/upkeep/images.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,11 @@ Void prepares and distributes multiple live images. These are prepared manually
due to the need for full root authority during build, and for the need to sign
them after building.

## Preparation

In `void-docs`, tag a release as `<year>.<month>.<day>` and update the package.
In `void-mklive`, increment the `version` file and tag that commit as `v<date>`.

## Building the Images

The images should be built using Github CI in the void-mklive repository. This
Expand All @@ -17,12 +22,13 @@ $ ./release.sh start

By default, this will build:

- Live ISOs with `base` and `xfce` variants for `x86_64*` and `i686`
- Live ISOs with `base` and `xfce` variants for `x86_64*`, `i686`, `aarch64*`,
and `asahi*`
- ROOTFSes for `x86_64*`, `i686`, `aarch64*`, `armv7l*`, and `armv6l*`
- PLATFORMFSes for `aarch64*`, `armv7l*`, and `armv6l*` Raspberry Pis
- SBC images for `aarch64*`, `armv7l*`, and `armv6l*` Raspberry Pis

This will take approximately 2 hours for the default settings. To ensure all
This will take approximately 30 minutes for the default settings. To ensure all
images have the same datecode, the datecode is cached at the beginning of the
run. The CI workflow will also generate `sha256sum.txt` for the built images.

Expand Down Expand Up @@ -61,7 +67,7 @@ $ export DATECODE=<date>
$ pwgen -cny 25 1 > void-release-$DATECODE.key
$ cat void-release-$DATECODE.key void-release-$DATECODE.key | \
minisign -G -p void-release-$DATECODE.pub -s void-release-$DATECODE.sec \
-c "This key is only valid for images with date $DATECODE." \
-c "This key is only valid for images with date $DATECODE."
```

Copy the public half of this key to the `void-release-keys` package in
Expand Down
Loading