What needs to be done to make Parabola have aarch64 package repos?
The Install Guide solution of using aarch32 packages on an aarch64 system is far from ideal.

Awesome!

I have a Raspberry Pi 3 Model B V1.2 from before I found out about libre software which unfortunately needs a blob to even boot.
I could test aarch64 Parabola on it with the reverse-engineered libre firmware: <https://github.com/librerpi/rpi-open-firmware> although the project already stalled once and doesn't seem to have particularly good support yet.

Guix already packages this project, but I'd rather avoid Guix because it's not 100% libre; it allows proprietary works in its repos.

Please tell me if I could be of help.

I'm running Arch Linux ARM virtualized in my Mac Mini M2, in order to help port Parabola packages to aarch64. I built and installed your-freedom, but it appears that it didn't conflict with any package from base and base-devel. However, bill-auger told me to run this command to list the packages in the blacklist that your-freedom couldn't conflict:

LANG=C pacman -Qiq $(cut -d: -f1 /usr/share/doc/your-freedom/blacklist.txt) 2> /dev/null | grep Name

And this is the output:

Name            : archlinuxarm-keyring
Name            : archlinux-keyring
Name            : base
Name            : cdrtools
Name            : filesystem
Name            : licenses
Name            : linux-api-headers
Name            : linux-firmware
Name            : linux-firmware-whence
Name            : linux-aarch64
Name            : pacman-mirrorlist
Name            : pacman
Name            : systemd-libs
Name            : systemd
Name            : systemd-sysvcompat

right, your-freedom can not conflict with any package which gets replaced in libre by a package with the identical name - all such packages must replaces=() itself for migrations from arch - that list of packages are those which would need to be packaged specifically for aarch64, in order that libretools can create aarch64 chroots - some may need to be cross-compiled for the parabola repos first (o/c you could build them natively on archarm, to get started) - from there, the rest of the packages can be built with libretools - luckily, that is a relatively short list; and several of them are trivial to build 'any' packages

'linux-aarch64' and probably several other kernels will need to be added to the blacklist

there are a few more to add to that list for non-systemd support (openrc, udev, elogind, your-init-freedom, etc); but it would be a great leap forward if only to get a complete systemd librechroot - only a small few packages must be built in a non-systemd chroot

just to note, there is a small blind-spot called non-systemd - artix supports only x86_64 - luckily those changes usually translate to other arches without troubles - but just in case, there is a fork of artix which maintains aarch64-specific non-systemd recipes based on artix and archarm recipes https://armtixlinux.org/