# The problem According to Developer Machines [1], current buildd machines are like this: * armel: 4 buildd (4 for arm64/armhf/armel) * armhf: 7 buildd (4 for arm64/armhf/armel and 3 for armhf only) [1] https://db.debian.org/machines.cgi In contrast to other buildd architectures, these instances are quite a few and it seems that it causes a shortage of buildd resourses. (e.g. during mass transition, give-back turn around time becomes longer and longer.) # Actual situation As you know, during 64bit time_t transition, many packages should be built, but it seems that +b1 or +bN build becomes slower. (I've hit BD-Uninstalled some times because of missing dependency rebuild)  ref. https://qa.debian.org/dose/debcheck/unstable_main/index.html # Expected situation Allocate more buildd resources for armel and armhf. Assign existing some buildd as armel/armhf buildd too. * arm-arm-01.debian.org * arm-arm-03.debian.org * arm-arm-04.debian.org Above buildd is used only for arm64 buildd (currently) Maybe there is some reason not suitable for armel/armhf buildd, but I don't know. # Additional information * arm64: 10 buildd (4 for arm64/armhf/armel, 6 for arm64 only) * amd64: 7 buildd (5 for amd64/i386 buildd) * riscv64: 9 buildd