Re: [Tails-dev] Tails for arm64 (with support for Apple Silicon)
Hi n9iu7pk, Good to know you were able to build the images! The nvme will surely help, I/O is terrible on RPis (but then, this is expected). So first of all, no, you don't have new images to compare the shasums at the moment. I think from now on, unless there are major new features from my part which merit early sharing, I will only upload pre-built images on new Tails point releases (uploading takes quite some time and a single upload of 2x3 images takes away around half my available space). In general, only images built on tagged commits are reproducible. In case you don't know (if you do I apologize, I have little knowledge of the Tails community), when the commit is not tagged, the /etc/apt/sources.list and /etc/apt/sources.list.d/bullseye.list files contain entries like ``` deb http://time-based.snapshots.deb.tails.boum.org/debian-security/2024041403 bookworm-security main contrib non-free non-free-firmware ``` with last-snapshot timestamps which change multiple times a day (4, I believe). However, I must have been lucky enough to start a new 6.2/arm64 build while the debian-security snapshot was the same as yours so I got the same sha256sums as you! Not so lucky with asahi and raspi, which you had built earlier and I built later. Nonetheless, I compared today's contents with yesterday's and can confirm that the only difference is precisely those timestamps. "tests: on raspi image -> 206 fails, 1460 skipped, 342 passed -> reproduceable." As you can see, most of the tests are skipped: the raspi image never boots (it cannot be virtualized), so it fails early and skips the other steps. arm64 and asahi, on the other hand, should work. Thanks for the estimate. I initially thought that Tails was snapshotting the whole debian archive, but soon realized that they don't need to do so since when booted the images use the actual live debian archive instead of snapshots. Making arm64 snapshots would be far less costly than I initially thought (nonetheless, I have no plans to set up my own: the images already contain far too many binaries provided by myself!) Best, NC ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tails for arm64 (with support for Apple Silicon)
Hi noisycoil, good news: could now build all images on 6.2 branches :) and could also run tests -> my nginx setup was faulty (typo). Meanwhile I've upgraded my PI5 with a nvme pcie ssd (N04 pcie board on top) -> run's noticeable faster :) Some results: - "how much space the amd64 Debian snapshots in use by Tails take up?" Roughly estimated along the apt-cacher volume after building all images: 1714316 KB /var/cache/apt-cacher-ng - tests: on raspi image -> 206 fails, 1460 skipped, 342 passed -> reproduceable. - sha265sums (do we have images/builds to compare?): c3b7251259df11ef71a559164a6d4d0f23e322fb58220ca6c4207e320bd66107 tails-arm64-6.2_arm64@8928015f41+sta...@fe2dd74d4d-20240414t1502z.apt-sources 7a3843bbd2696e98df715025a9cb93fc8ddf4ff57d011d1368b7cd80356c41a3 tails-arm64-6.2_arm64@8928015f41+stable@fe2dd74d4d-20240414T1502Z.build-manifest 6bc699eb40d4eb9eca1450fc9eb8eb1d215fbe76cf5c7a80689ba018457dfd2e tails-arm64-6.2_arm64@8928015f41+stable@fe2dd74d4d-20240414T1502Z.buildlog e0efcb0d0590363e726aed0698c03aece54334f680400764ab14719221165e5e tails-arm64-6.2_arm64@8928015f41+sta...@fe2dd74d4d-20240414t1502z.img d9c721096f08eddc4a50c7cc79a756abbe39dbc0cad502b8fb9020717f4c4782 tails-arm64-6.2_arm64@8928015f41+sta...@fe2dd74d4d-20240414t1502z.iso 191c45f6d51ab741443e7eeeff03c832c0af12fb448bcdb9a77ba109fa9e2fc0 tails-arm64-6.2_arm64@8928015f41+stable@fe2dd74d4d-20240414T1502Z.packages 23369a3e276a322d794e5ef09a1e74c25849ad82741564fba18045702b8e395b tails-arm64-6.2_asahi@7345947cc8+sta...@fe2dd74d4d-20240414t1418z.apt-sources 022aefd49fc78699a584cbfc697806d90280125541f46a08dede06c06df4e9ae tails-arm64-6.2_asahi@7345947cc8+stable@fe2dd74d4d-20240414T1418Z.build-manifest 93f1e07f3fae5796604a780d2d87166e90eee6167306fb68177e93663903874f tails-arm64-6.2_asahi@7345947cc8+stable@fe2dd74d4d-20240414T1418Z.buildlog b33178d88094ff3b83970f8e7497fe2b14110ef95d4d42cf34da787967254ed0 tails-arm64-6.2_asahi@7345947cc8+sta...@fe2dd74d4d-20240414t1418z.img 1a07ed1050417460ff7a16a62c854330ea510d73771c19968706b3444cabbe3d tails-arm64-6.2_asahi@7345947cc8+sta...@fe2dd74d4d-20240414t1418z.iso 9afab6262eef404e73a28d28338752f3543c026aab9341aefeb322109d34a6b0 tails-arm64-6.2_asahi@7345947cc8+stable@fe2dd74d4d-20240414T1418Z.packages 9b638dca0ddc976797969a6422fc5bef2de8ec0bef9effbc794c391a00aada1f tails-arm64-6.2_raspi@dc0264f870+sta...@fe2dd74d4d-20240414t1215z.apt-sources 7029f74e0e0e2751054ed3b88dfb675516a0b676f47bc2dc5644aab729be191f tails-arm64-6.2_raspi@dc0264f870+stable@fe2dd74d4d-20240414T1215Z.build-manifest 360cde7f2bf7097fc85a127e4a84d61bc680875ec5144c2cef4b14374fad2638 tails-arm64-6.2_raspi@dc0264f870+stable@fe2dd74d4d-20240414T1215Z.buildlog c1bb35e768cc2961b75dbe539ea28c854fb1dee37b588c2114277c27395392f1 tails-arm64-6.2_raspi@dc0264f870+sta...@fe2dd74d4d-20240414t1215z.img d9967d1c353d4c0018cf899c8c19393886e2ae3c78938fbf73b069775a7d20cc tails-arm64-6.2_raspi@dc0264f870+sta...@fe2dd74d4d-20240414t1215z.iso 21f1a4fd4f098fccaef141c25dc67b18a185c38d42d8dfc14beeaa746b89f221 tails-arm64-6.2_raspi@dc0264f870+stable@fe2dd74d4d-20240414T1215Z.packages All the best! n9iu7pk PGP 7426 4598 B5AD 4D12 1699 C710 [ D602 E331 4D12 FFCB ] https://keys.openpgp.org/search?q=D602E3314D12FFCB On 13.04.24 13:55, noisyc...@tutanota.com wrote: Hi n9iu7pk, It looks like fixing uBlock is quite trivial, actually, so I did it myself. When an upstream patch becomes available I will revert my changes and apply that instead. The wip/* branches can now build the images. I also uploaded the 6.2/* branches. These have exactly the same content as the corresponding wip/* branches, the difference being that the arm64/asahi/raspi patches are applied directly on top of stable instead of being buried below the newer commits, so they're easily identifiable. As stable gets updated I will keep rebasing them onto it (and merging the changes to wip/*) until the 6.2 release, at which point I will freeze them. Best, NC ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
