On 2024-08-07, Santiago Vila wrote: > El 6/8/24 a las 23:52, Vagrant Cascadian escribió: >> Well, I was able to reproduce a difference running one build with an >> arm64 kernel one with an armhf kernel, but have not identified exactly >> what triggers the difference... > > Thanks for testing! So, if I understood, the variable which makes the build > to be different is the kernel, is this right? > > Since you can reproduce the difference, can you test the branch > I've just set as default here, called wip-202408-reproducible? > > https://salsa.debian.org/sanvila/smartlist-not-yet/
That patch did not fix the underlying issue. > Ideally, I'd like to reproduce this myself, but I only have access > to "pure" arm64 systems on which I can put an armhf chroot. > Is it too difficult to cross-grade it to a "native" armhf system? The userland is easy enough with multi-arch, but to use arm64 hardware with a 32-bit kernel you need a kernel built for that hardware... which is an uncommon configuration. Raspberry PI tends to have such kernels, though I think they are not typically built in Debian proper. At the moment, I am building each test build on different hardware, one natively 32-bit and one running in a 32-bit armhf chroot with the host system running a 64-bit kernel (which is similar to the tests.reproducible-builds.org infrastructure). I forget if the official Debian buildd infrastructure has a mix of 64-bit and 32-bit hardware... it may have moved to only 64-bit hardware with 32-bit chroots. live well, vagrant
signature.asc
Description: PGP signature
