Hi NoisyCoil,
anyhow I'm not finished with building, next step would be an apple
silicon arm64e image as soon as I've got hardware. Also an rpi5 image
build with on an arm platform. Would take some time/days, don't expect
fast results.
How did you build the Tails packages for arm? I once fetched the sources
from the apt repos and tried to re-compile/-build them on an arm
platform (pain point have been all the dependencies as arm deb's). That
was partially successful, but not for all packages.
Another point would be Tails snapshots from debian's apt repos (as
currently that's mapped by the DNS hijack to latest always). I assume,
that would be possible also for arm packages, on could follow the x86_64
versions of packages of a given Tails snapshot to also create an arm
snapshot - arm and x86 versions should not differ?
> - If you are running the image on a RPi5, then you could as well build it there (unless you have a good reason not to). This is what I am doing right now, as natively building Tails on a 8GB RPi5 is MUCH faster than building it on a 16-core 32-threads 64GB AMD machine. I'm talking 1.5hr tops (often less) on RPi5 vs. even 13 hrs on amd64.
I know that from experiments years ago with arm vm's runing with qemu on
intel platforms. I was curious whether that would work for Tails
somehow: It does! VERY slow but not that slow, that it is impossible.
And YES, it's better to use an arm64 platform with >= 8GM RAM (rpi,
rock, apple silicon and may others).
> - What you're saying about debian-security sounds weird to me. I never had issues accessing the debian-security repo via http, neither in general nor during Tails builds. E.g. a plain `curl http://deb.debian.org:80/debian-security/dists/bookworm-security/Release <http://deb.debian.org/debian-security/dists/bookworm-security/Release>` works.
Digged deeper into, might be caused by hybrid IPv4/IPv6 environment,
debian-security had been resolved to IPv6 addresses that failed to be
accessed as http resource.
> - Yes, you picked the right branch. I am working on rebasing everything on stable (with new features), so a big rebase is coming soon, but the new branch names will still be wip/arm64, wip/asahi and wip/raspi. 'stable' and 'devel' are just (probably non-up-to-date versions of) Tails' regular stable and devel, with no arm64-related changes.
Somehow confused: base_branch defines, which branch will be cloned/used
insde of the build VM while rake build. In case of "stable" even NOT the
wip/raspi branch will be used to build, so how could a raspi image be
build on "stable"?
Best regards!
n9iu7pk
PGP 7426 4598 B5AD 4D12 1699 C710 [ D602 E331 4D12 FFCB ]
https://keys.openpgp.org/search?q=D602E3314D12FFCB
