Hi Mike and other Horde maintainers, On 22-10-2022 17:31, Mike Gabriel wrote:
For Horde, getting autopkgtests resolved (and packages migrate to testing) is one thing, but getting all of Horde deprecation-warnings-free with php8.2 at run time is a completely different cup of team. (Horde upstream is slowly working on Horde6, but that will not be ready for bookworm, so we have to stay with Horde5 for Debian 12).I am currently trying to get my UDD dashboard beautiful again, but this will be an ongoing effort until December (and probably more uploads after X-mas).The allow-stderr flag in debian/tests/control is a viable solution, but I'd love to use that as a last ressort. At the moment, it is more helpful (to me) to see all those CI failures and not have them mask with that flag.
We're now nearing the end of the php8.2 transition (hopefully), but there's still a large set of horde packages affected. In the view of the release team these autopkgtest failures will very soon be RC bugs. Will you fix these autopkgtest real soon now (the underlying issue or allow-stderr)? Do I need to file RC bugs for all of them? Should I remove horde from bookworm and let you fix the packages one by one? We can live with any reasonable option, but accepting these autopkgtest regressions in bookworm is only acceptable by us with RC bugs filed (causing the autoremoval timer to start counting).
Paul
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature