IRC channel logs
2025-09-07.log
back to list of logs
<Googulator>vasi: just letting you know, I have somehow managed to get the same dependency error with the azurelinux-repos packages included in the build, so it may actually be something else <Googulator>an error in the core-container image definition possibly <vasi>Hmm fascinating, I guess we'll see! <vasi>I really should start doing these builds on EC2 or something, my poor laptop gets so hot <Googulator>I'm doing them on a Core 2 Quad-based machine with a policy of "no part newer than 15 years old" (I made an exception for storage after I had several period-accurate HDDs fail on me, so I now use a modern SATA SSD there) - imagine how hot that gets :) <Googulator>I'm avoiding recent hardware as a precaution against hardware-based Trusting Trust backdoors <Googulator>eventually, the goal is to replicate a bootstrap on all sealed, New Old Stock hardware, to guarantee nothing has been sneakily modified to add a backdoor <vasi>hmm i just had a build fail with a few hundred missing dependencies, i really am not sure why <vasi>let me know next time you have a build run thru ok, and i'll give repro a shot then <Googulator>ran a full ISO build just now with 3.0-bootstrap-dependency-resolution (which has the upstream repo references removed), failed the same way, so it's not the core-container image definition - now trying a full ISO with 3.0-bootstrap <Googulator>vasi: turns out, something related to the wrong dependency resolution result got cached during the no-official-repos run; did a full "make clean", and the build is running fine (with the official repo definitions included, of course) <Googulator>unfortunately that means, we are in fact relying on a previous build's dependency data <Googulator>vasi: found the actual root cause of the slow tdnf operations... <Googulator>live-bootstrap doesn't enable the loopback interface by default, so requests to 127.0.0.1 are never responded to <Googulator>glibc (and apparently also musl) love to fall back to querying a DNS server on localhost if resolv.conf is missing <Googulator>so, added iproute2 to the bootstrap sequence, and suddenly tdnf no longer needs to wait for timeouts