Right. One thing we recommended when talking to relay operators during earlier EOL upgrade periods is adding the debian -backports repository to the Raspberry Pi. It worked well according to the feedback we got. We linked to
for general steps (you need to adapt them for bullseye, though).
Thanks. I thought about doing that, but I would rather not like to mix Raspian bullseye and Debian bullseye-backports.
Is there a good reason against building armhf on deb.torproject.org?
Georg Koppen:
···
Right. One thing we recommended when talking to relay operators during earlier EOL upgrade periods is adding the debian -backports repository to the Raspberry Pi. It worked well according to the feedback we got. We linked to Marks Rpi Cluster: Add buster-backports to a Raspberry Pi
for general steps (you need to adapt them for bullseye, though).
Thanks. I thought about doing that, but I would rather not like to mix Raspian bullseye and Debian bullseye-backports.
Is there a good reason against building armhf on deb.torproject.org?
Just resource constraints. We have a ticket for that work[1] but de-prioritized it even further given that we have a good workaround and a lot of affected users are happy with it.
Right. One thing we recommended when talking to relay operators during earlier EOL upgrade periods is adding the debian -backports repository to the Raspberry Pi. It worked well according to the feedback we got. We linked to Marks Rpi Cluster: Add buster-backports to a Raspberry Pi
for general steps (you need to adapt them for bullseye, though).
