[URGENT] Deleted arm64 packages from the deb.tpo with the important support for the Raspberry Pi platform (and others SBC)
After this commit: tpo/core/debian/tor@ad278a09 ...:
[...] remove all the things we do not have images for (leaves only modern debians and only amd64
and related to this issue #42052 (closed):
[...] the update in Bookworm throws this error: "
as repository 'https://deb.torproject.org/torproject.org bookworm InRelease' doesn't support architecture 'arm64'"On Bookworm (arm64)
It seems that maintainers intend to drop official Tor support to give the latest stable Tor version using the deb.tpo repository for the popular and very used (and modern: Raspberry Pi 5 was launched last 2023 with arm64 arch and they keep releasing versions) Raspberry Pi (3/4/5), and thus for the rest of the SBCs that typically use arm64 architecture and will probably continue to do so for a long time.
This breaks the official Tor support for many projects and systems that use it today, affecting security and anti-censorship on the Internet.
With all this, there seems to be no intention to revert this based on the latest commits which only mention "re-enable ubuntu builds" and nothing about the arm64 architecture.
Please, could revert this commit and re-enable arm64 builds in conjunction with the ubuntu builds?
Refs:
~> Snapshot of the "release" file after the commit destroying arm64: https://web.archive.org/web/20241224132638/https://deb.torproject.org/torproject.org/dists/bookworm/Release ...now: https://deb.torproject.org/torproject.org/dists/bookworm/Release
~> Main "dist" folder: https://web.archive.org/web/20241223140428/http://deb.torproject.org/torproject.org/dists/ ...now: https://deb.torproject.org/torproject.org/dists/
Other refs of users affected: https://forum.torproject.org/t/apt-install-of-deb-torproject-org-keyring-fails-on-raspberry-pi-5-running-bookworm/17600