Skip to content

qubes-dom0-packagev2.yml: update for latest builderv2#15

Open
aronowski wants to merge 1 commit intomasterfrom
build-for-remote-signing
Open

qubes-dom0-packagev2.yml: update for latest builderv2#15
aronowski wants to merge 1 commit intomasterfrom
build-for-remote-signing

Conversation

@aronowski
Copy link
Copy Markdown

The updated building workflow is meant to be ran on a GitHub worker with Ubuntu 24.04. For this case the workflow disables AppArmor and, given the required recent Sequoia release, installs Rust with the recommended method available at https://rust-lang.org/tools/install/.

@aronowski aronowski requested a review from macpijan February 2, 2026 16:20
The updated building workflow is meant to be ran on a GitHub worker with
Ubuntu 24.04. For this case the workflow disables AppArmor and, given
the required recent Sequoia release, installs Rust with the recommended
method available at https://rust-lang.org/tools/install/.

Signed-off-by: Kamil Aronowski <kamil.aronowski@3mdeb.com>
@aronowski aronowski force-pushed the build-for-remote-signing branch from bdbba48 to b102a70 Compare February 3, 2026 16:15
@aronowski aronowski changed the title qubes-dom0-packagev2.yml: update for latest builderv2 and remote signing qubes-dom0-packagev2.yml: update for latest builderv2 Feb 3, 2026
with:
repository: QubesOS/qubes-builderv2
ref: 80dd898cc0472dd99f161f1d1c7c44da64de93f2
ref: 5327e41b3d68befc61bee87fb1ac0033662d575f
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a reason for this change to commit message.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This ref was the most recent qubes-builderv2 at the time of doing this work.

The point of this update was to have the ability to run the most recent Docker executors on GitHub workers, to mitigate potential incompatibilities between our current setup and the one proposed in this PR, which keeps up with the upstream. Otherwise there might be ambiguities, whether a failing build was caused by our old revision, or something else.

Speaking about incompatibilities, the legacy builder support, which we still have in this repository, might become unavailable soon - for example, that's why the upstream qubes-zfs-dkms has my commit, where I removed the support for it, and it got approved.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants