Hi, On Tue, 19 Jan 2021, Robert Edmonds wrote: > There is an unfixed issue in Unbound 1.9.0 (#962459 / #973052) that > affects some users (I have not been able to reproduce it). Upstream has > invested some time in helping the Debian maintainers track down > potential combinations of commits from later releases that may be > related to the issue, but we were not able to produce a working, > targeted fix. I would prefer that 1.9.0 not be exposed to more Debian > users, especially a combination of stretch's libevent and buster's > unbound that AFAIK has not been tested before.
Really what this means is that we need to fix unbound in buster before we can resurrect support in stretch. I have read the history of the two bugs and at this point I would suggest to create a package of the latest 1.9.x and ask the tester in #962459 if that versions fixes the issue, since we have not managed to cherry-pick a working set of commits. Then depending on the result, work with the release team to release that version in buster (or possibly 1.10 if really the last 1.9.x doesn't work reliably either). Concerning testing of unbound 1.9.x with the libevent 2.0 in stretch, well, we have LTS users of unbound so we can ask them to test the updated packages. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hert...@debian.org> ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS
