Update: **We will move forward with dropping armhf from postmarketOS** Checklist: * [x] remove armhf job from pmaports * [x] drop all armhf devices (https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8883) * [x] remove armhf from pmaports.cfg * [x] remove armhf from bpo * [x] remove armhf from apkbrowser * anything else? **Original issue with reasoning below** --- We are considering dropping armhf from postmarketOS edge in ~2 weeks. ## What is armhf? To be clear: armhf in Alpine targets armv6 CPUs with an FPU. This is **NOT** to be confused with Debian's naming scheme, where Debian armhf targets armv7. We are **NOT** dropping armv7 devices (e.g. Nokia N900, Samsung Galaxy Note II, etc) anytime soon, as many people still use or maintain support for armv7 devices and it overall is still seeing a lot of care and attention. This change **only affects armv6 devices with an FPU** (also see below for a list of devices that would be affected). ## Why drop armhf? - Alpine has been considering dropping armhf at least 3 times in the past few years, most recently [one month ago](https://fosstodon.org/@ncopa/116215867094108492). - Our systemd build does not run on armhf (so in practise OpenRC is the only choice, instead of having both available) - ...neither do our mainline `linux-postmarketos-*` kernels - ...and neither do even Alpine's `linux-lts` and `linux-stable` (one reason why there's no systemd build for armhf on our side, the other reason is pmbootstrap limitations that make it not currently possible to build systemd without BPF support on only armhf) - We support very few "armhf" devices, and even fewer *real* armhf devices. - Many packages and UIs are not available on armhf anymore - In general the armhf support in postmarketOS is not very optimal ## Which devices are armhf? / How many devices will be affected by this? The current situation with armhf in postmarketOS is, that we have 26 armhf devices: ``` device/downstream/device-asus-duma/APKBUILD:arch="armhf" device/downstream/device-bq-chaozu/APKBUILD:arch="armhf" device/downstream/device-google-glass/APKBUILD:arch="armhf" device/downstream/device-gp-peak/APKBUILD:arch="armhf" device/downstream/device-htc-vivo/APKBUILD:arch="armhf" device/downstream/device-infocus-flatfish/APKBUILD:arch="armhf" device/downstream/device-lg-d285/APKBUILD:arch="armhf" device/downstream/device-lg-dory/APKBUILD:arch="armhf" device/downstream/device-nokia-rm885/APKBUILD:arch="armhf" device/downstream/device-raspberry-pi/APKBUILD:arch="armhf" device/downstream/device-raspberry-pi0/APKBUILD:arch="armhf" device/downstream/device-samsung-apexq/APKBUILD:arch="armhf" device/downstream/device-samsung-i747m/APKBUILD:arch="armhf" device/downstream/device-samsung-i8200/APKBUILD:arch="armhf" device/downstream/device-samsung-kylevess/APKBUILD:arch="armhf" device/downstream/device-samsung-serranodsdd/APKBUILD:arch="armhf" device/downstream/device-semc-anzu/APKBUILD:arch="armhf" device/downstream/device-sony-aries/APKBUILD:arch="armhf" device/downstream/device-sony-scorpion/APKBUILD:arch="armhf" device/downstream/device-sony-seagull/APKBUILD:arch="armhf" device/downstream/device-sony-taoshan/APKBUILD:arch="armhf" device/downstream/device-t2m-flame/APKBUILD:arch="armhf" device/downstream/device-wiko-lenny3/APKBUILD:arch="armhf" device/downstream/device-xiaomi-armani/APKBUILD:arch="armhf" device/downstream/device-xiaomi-cancro/APKBUILD:arch="armhf" device/testing/device-nokia-n9/APKBUILD:arch="armhf" ``` Out of these 26 devices: * **24** are actually armv7 that just run an armhf distro (according to their wiki pages) * They are armhf for legacy reasons which are no longer relevant today (alpine did not have a separate armv7 port back then), and should be all upgraded to armv7 * **1** of these 24 devices (`nokia-n9`) runs a mainline kernel (and is in `testing`) * **2** *actual* armhf devices (`raspberry-pi` and `raspberry-pi0`) which are also supported in Alpine (as well as Raspberry Pi OS / Raspbian) However, all these 26 devices are completely unmaintained and no one so far has stepped up to maintain any of them yet. They will thus be affected by the [archival of all unmaintained devices after v26.06](pmaports#4445). If someone wants to take over one of these device ports, they should upgrade it to armv7 whenever possible. Assuming all these devices get archived or upgraded to armv7, this will leave no more armhf devices left regardless of if armhf gets dropped sooner or not. ## But I still rely on armhf / I'm doing development on an armhf device, what can I do? If you are running on a Raspberry Pi Zero or Raspberry Pi 1: you can still use Alpine on these devices for a while, if you want. We will give 2 weeks for feedback before dropping armhf entirely from pmaports. **If you still rely on this architecture and would like it to stay, please comment below!** Also consider taking over maintainership of these devices if you rely on them (also moving them to armv7 where feasible, so you won't be affected by this change anyway).