Elara
There is this multi-architecture image: [lopsided/archlinux](https://hub.docker.com/r/lopsided/archlinux/), which supports `amd64` and all the ARM variants, but it doesn't contain things like `grep`, which are used by the acceptance tests.
There also seems to be a `devel` tag on that image, which has the `base-devel` group installed, so it has all the tools I need. That one should work, but...
Ok, in that case, the acceptance tests are finished and pass. I did test them locally for both amd64 and the ARM variants, and they all pass there too.
Should I add `archlinux` to the `pkgFormat` field in `.github/workflows/build.yml`?
I could also try to make a PR against https://github.com/goreleaser/goreleaser that integrates these changes and can be merged once they make it into a release.
I went through a bunch of PKGBUILDs on the AUR to see if I missed anything and implemented all of it.
Should I add the `ConventionalExtension()` method to all packagers as part of my PR or just Arch?
Since the filename would likely be hardcoded, we could check for corruption by having a BLE characteristic that generates and sends a crc32 (or some other algorithm) back to the...