feat(workflows): Add arm64 .deb #1359
Labels
No labels
Abandoned
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
bob the builder
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity!1359
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "skeet70/continuwuity:1235-add-arm-deb"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This pull request adds arm64 building to the
build-debianworkflow, to support rPi and other arm linux users.Fixes: #1235
Pull request checklist:
mainbranch, and the branch is named something other thanmain.myself, if applicable. This includes ensuring code compiles.
TODO: to test this, someone with push access needs to push it to a branch and run it manually on the workflow page
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.
Closing this as it appears to be abandoned.
@ginger this was not abandoned and is still needed.
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.
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.
@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.
WIP: feat(workflows): Add arm64 .debto feat(workflows): Add arm64 .debRunning now: https://forgejo.ellis.link/continuwuation/continuwuity/actions/runs/20234/jobs/0/attempt/1
Looks like
(arm64, ubuntu-previous)specifically fails with unknown packages, the rest seem to work fine 🤔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.
Awesome, I've kicked the flow off again with the updated changes
Looks good to me! Thanks!
aa93b7918eca100e093bThanks for jumping on this, now my rPI can finally auto-update :D