I queued xz for a rebuild, just to see if that fixes it. If not we have to dig deeper, maybe LTO messes something up.
We and Archlinux are using -flto-partition's default. You can always check their makepkg.conf in…
Probably not all, but a few have these problems because gcc is not mandatory to list as makedep because its in base-devel (which is fine), but ALHP did not take that into account until https://git.…
Signature on community-x86-64-v3 is fine on the server:
gpg: assuming signed data in 'community-x86-64-v3/os/x86_64/community-x86-64-v3.db.tar.xz'
gpg: Signature made Fri 13 May 2022…
Well, I can not reproduce it for alhp.harting.dev/alhp.anonfunc.dev. You are sure you switched mirrors?
You can have a look at
pacman-key --list-keys 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298
That should list the alhp buildbot key.
Yep, this is a know issue. I already experimented with separating the builds on a network level via systemd-nspawn. There is only firewall integration left, otherwise this already worked in my…
Just FYI, all builds after 2022-05-12 01:00 UTC are build with the new flags -mpclmul and -devirtualize-at-ltrans.
We probably could test it, but I would prefer not doing it on the production machine. I can probably make some test builds locally later/tomorrow.
