OctoPrint / OctoPrint/OctoPi-UpToDate
[Task] Build 64bit variant if available
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 71
- Forks
- 14
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 1
Description
The task
We currently only fetch and build from the 32bit variant of the input image. It might be a good idea to also check during the build if there's a 64bit variant as well and if so build that too and include its data in the rpi-imager.json snippet.
The downside here is a massive increase of testing, as that will require flashing both images in serial - or on two test devices on the testrig in parallel. Will require some testing to make work properly.
Verification
- I'm a maintainer or collaborator of OctoPi-UpToDate and allowed to use this issue type
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the current 32-bit input-image fetch and build path, along with the generation of the rpi-imager.json snippet. Start by tracing how the existing variant is selected and included, then verify that an available 64-bit variant is built, represented in the snippet, and tested by flashing both images as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system, embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100