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+stable@???
7a3843bbd2696e98df715025a9cb93fc8ddf4ff57d011d1368b7cd80356c41a3
tails-arm64-6.2_arm64@8928015f41+stable@???
6bc699eb40d4eb9eca1450fc9eb8eb1d215fbe76cf5c7a80689ba018457dfd2e
tails-arm64-6.2_arm64@8928015f41+stable@???
e0efcb0d0590363e726aed0698c03aece54334f680400764ab14719221165e5e
tails-arm64-6.2_arm64@8928015f41+stable@???
d9c721096f08eddc4a50c7cc79a756abbe39dbc0cad502b8fb9020717f4c4782
tails-arm64-6.2_arm64@8928015f41+stable@???
191c45f6d51ab741443e7eeeff03c832c0af12fb448bcdb9a77ba109fa9e2fc0
tails-arm64-6.2_arm64@8928015f41+stable@???
23369a3e276a322d794e5ef09a1e74c25849ad82741564fba18045702b8e395b
tails-arm64-6.2_asahi@7345947cc8+stable@???
022aefd49fc78699a584cbfc697806d90280125541f46a08dede06c06df4e9ae
tails-arm64-6.2_asahi@7345947cc8+stable@???
93f1e07f3fae5796604a780d2d87166e90eee6167306fb68177e93663903874f
tails-arm64-6.2_asahi@7345947cc8+stable@???
b33178d88094ff3b83970f8e7497fe2b14110ef95d4d42cf34da787967254ed0
tails-arm64-6.2_asahi@7345947cc8+stable@???
1a07ed1050417460ff7a16a62c854330ea510d73771c19968706b3444cabbe3d
tails-arm64-6.2_asahi@7345947cc8+stable@???
9afab6262eef404e73a28d28338752f3543c026aab9341aefeb322109d34a6b0
tails-arm64-6.2_asahi@7345947cc8+stable@???
9b638dca0ddc976797969a6422fc5bef2de8ec0bef9effbc794c391a00aada1f
tails-arm64-6.2_raspi@dc0264f870+stable@???
7029f74e0e0e2751054ed3b88dfb675516a0b676f47bc2dc5644aab729be191f
tails-arm64-6.2_raspi@dc0264f870+stable@???
360cde7f2bf7097fc85a127e4a84d61bc680875ec5144c2cef4b14374fad2638
tails-arm64-6.2_raspi@dc0264f870+stable@???
c1bb35e768cc2961b75dbe539ea28c854fb1dee37b588c2114277c27395392f1
tails-arm64-6.2_raspi@dc0264f870+stable@???
d9967d1c353d4c0018cf899c8c19393886e2ae3c78938fbf73b069775a7d20cc
tails-arm64-6.2_raspi@dc0264f870+stable@???
21f1a4fd4f098fccaef141c25dc67b18a185c38d42d8dfc14beeaa746b89f221
tails-arm64-6.2_raspi@dc0264f870+stable@???
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, noisycoil@??? 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
