Hello, On Sat, 2025-03-01 at 14:58 +0100, Guillem Jover wrote: > > I have not investigated the problem in detail yet. However, downgrading > > dupload > > to 2.11.2 fixes the problem for me. > > I'd assume this is due to the new OpenPGP multi-backend support, which > makes the openpgp-hook require explicit keyrings options.
OK. > I suppose buildd might be failing like this if dupload exited with a > failure? (Which I think deserves its own bug report, to handle that > more gracefully.) > > Before the upload I coordinated with Aurelien Jarno to make sure this > time around the buildds had the required config changes: > > > https://salsa.debian.org/dsa-team/mirror/dsa-puppet/-/commit/44cb84d9f0a85d29c82e63f2e8ad1eb9b92530cc > > But, I guess the instance you are reporting for might be independent > from DSA? The DSA-maintained instances are only building the packages for the release architectures. Debian Ports packages are built on separate machines and therefore such configuration changes would have to be applied there as well: https://salsa.debian.org/debian-ports-team/dsa-puppet > The default debian hosts configured in the shipped conffile contain > the required changes so if you are using a custom one, then that might > need to be adapted? Otherwise it would be nice to know what's going > wrong. Not sure what you mean with "default Debian hosts"? > I improved the error reporting on git, and will be adding a NEWS entry > because this fallout I guess was unexpected. Yes, breaking changes should be communicated in the NEWS file and I suggest that the required configuration changes are added to the default configuration files of the src:sbuild package which also contains the buildd binary package. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
