feat(workflows): Add arm64 .deb #1359

Merged
nex merged 3 commits from skeet70/continuwuity:1235-add-arm-deb into main 2026-07-27 19:51:35 +00:00
Contributor

This pull request adds arm64 building to the build-debian workflow, to support rPi and other arm linux users.

Fixes: #1235

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
<!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> This pull request adds arm64 building to the `build-debian` workflow, to support rPi and other arm linux users. <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> Fixes: #1235 <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [ ] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. - [ ] I have written a [news fragment][n1] for this PR, if applicable<!--(can be done after hitting open!)-->. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages [n1]: https://towncrier.readthedocs.io/en/stable/tutorial.html#creating-news-fragments
feat(workflows): Add arm64 .deb
All checks were successful
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 3s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m42s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 17m23s
3b43f2e8ea
Owner

TODO: to test this, someone with push access needs to push it to a branch and run it manually on the workflow page

TODO: to test this, someone with push access needs to push it to a branch and run it manually on [the workflow page](https://forgejo.ellis.link/continuwuation/continuwuity/actions?workflow=build-debian.yml)
ginger added this to the (deleted) milestone 2026-02-20 14:13:57 +00:00
Member

Hey Ho, it would be nice to have arm64 .deb packages, yes (and no, I don't have the rights to push the right buttons). However, what I would find even better if the repository would contain release .deb artifacts rather than nightly .deb builds (or ideally both, one repo with "just" release artifacts and one with a few nightlies.

Also, it would be nifty if we could attach .deb packages to the release page as assets, currently we only attach the bare binaries and the source.

Hey Ho, it would be nice to have arm64 .deb packages, yes (and no, I don't have the rights to push the right buttons). However, what I would find even better if the repository would contain release .deb artifacts rather than nightly .deb builds (or ideally both, one repo with "just" release artifacts and one with a few nightlies. Also, it would be nifty if we could attach .deb packages to the release page as assets, currently we only attach the bare binaries and the source.
Owner

Closing this as it appears to be abandoned.

Closing this as it appears to be abandoned.
ginger closed this pull request 2026-07-14 13:40:01 +00:00
Author
Contributor

@ginger this was not abandoned and is still needed.

TODO: to test this, someone with push access needs to push it to a branch and run it manually on the workflow page

I don't have that access, so I couldn't push it any further than it currently is. Current .deb releases are still just four copies of the exact same artifact.

@ginger this was not abandoned and is still needed. > TODO: to test this, someone with push access needs to push it to a branch and run it manually on the workflow page I don't have that access, so I couldn't push it any further than it currently is. [Current .deb releases](https://forgejo.ellis.link/continuwuation/-/packages/debian/continuwuity/26.6.2) are still just four copies of the exact same artifact.
skeet70 reopened this pull request 2026-07-14 17:23:28 +00:00
Owner

This branch's changes currently conflict with the workflow in main. Once that conflict is resolved, ping me and I'll test the updated workflow.

This branch's changes currently conflict with the workflow in main. Once that conflict is resolved, ping me and I'll test the updated workflow.
Update after trying to run as much as I could locally via docker
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Checks / Prek / Check changed files (pull_request) Successful in 5s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m6s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m16s
Deploy Element Web / 🏗️ Build and Deploy (pull_request) Failing after 6m36s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 11m36s
e05fcb7039
Author
Contributor

@ginger it should be good to test now. I tried to validate as much as I could by running act/docker cross builds locally, which led to a few more changes w/ comments calling out the edge cases that were hit.

@ginger it should be good to test now. I tried to validate as much as I could by running act/docker cross builds locally, which led to a few more changes w/ comments calling out the edge cases that were hit.
skeet70 changed title from WIP: feat(workflows): Add arm64 .deb to feat(workflows): Add arm64 .deb 2026-07-20 18:48:10 +00:00
Owner
Running now: https://forgejo.ellis.link/continuwuation/continuwuity/actions/runs/20234/jobs/0/attempt/1
Owner

Looks like (arm64, ubuntu-previous) specifically fails with unknown packages, the rest seem to work fine 🤔

Looks like `(arm64, ubuntu-previous)` specifically fails with unknown packages, the rest seem to work fine 🤔
Fix for jammy previous image w/ different sources format
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Checks / Prek / Check changed files (pull_request) Successful in 5s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m12s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 11m46s
aa93b7918e
Author
Contributor

Pushed a fix. Latest LTS for ubuntu is 26 (making 24.04 the presumptive previous), so I didn't cover 20 as "previous", which has a different sources layout. Added an extra defensive bit that makes it work for jammy too (which'll be a dead conditional once everything moves forward, but not a big deal).

Sorry I missed that in my testing.

Pushed a fix. Latest LTS for ubuntu is 26 (making 24.04 the presumptive previous), so I didn't cover 20 as "previous", which has a different sources layout. Added an extra defensive bit that makes it work for jammy too (which'll be a dead conditional once everything moves forward, but not a big deal). Sorry I missed that in my testing.
Owner

Awesome, I've kicked the flow off again with the updated changes

Awesome, I've kicked the flow off again with the updated changes
nex approved these changes 2026-07-27 17:39:50 +00:00
nex left a comment

Looks good to me! Thanks!

Looks good to me! Thanks!
nex requested reviews from Jade, ginger 2026-07-27 17:39:57 +00:00
ginger approved these changes 2026-07-27 19:44:51 +00:00
ginger force-pushed 1235-add-arm-deb from aa93b7918e
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Checks / Prek / Check changed files (pull_request) Successful in 5s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m12s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 11m46s
to ca100e093b
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m17s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m24s
Documentation / Build and Deploy Documentation (push) Successful in 1m1s
Checks / Prek / Pre-commit & Formatting (push) Successful in 1m7s
Checks / Prek / Check changed files (push) Successful in 7s
Release Docker Image / Build linux-amd64 (release) (push) Has been cancelled
Release Docker Image / Build linux-arm64 (release) (push) Has been cancelled
Release Docker Image / Create Multi-arch Release Manifest (push) Has been cancelled
Release Docker Image / Build linux-amd64 (max-perf) (push) Has been cancelled
Release Docker Image / Build linux-arm64 (max-perf) (push) Has been cancelled
Release Docker Image / Create Max-Perf Manifest (push) Has been cancelled
Release Docker Image / Release Binaries (push) Has been cancelled
Release Docker Image / Mirror Images (push) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (push) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Deploy Element Web / 🏗️ Build and Deploy (pull_request) Failing after 6m48s
2026-07-27 19:49:13 +00:00
Compare
nex merged commit ca100e093b into main 2026-07-27 19:51:35 +00:00
nex deleted branch 1235-add-arm-deb 2026-07-27 19:51:36 +00:00
Author
Contributor

Thanks for jumping on this, now my rPI can finally auto-update :D

Thanks for jumping on this, now my rPI can finally auto-update :D
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!1359
No description provided.