El 10/07/20 a las 18:50, Daniel Baumann escribió: > On 7/10/20 3:13 PM, Santiago Ruano Rincón wrote: > > I'd rather downgrade severity to important. > > i'd rather not - either it's a bug and then it should be fixed, or, if > the new behaviour is on purpose, then it needs to be documented and > handled for upgrades. > > in either way, upgrading buster->bullseye leaves systems without working > DNS, which deserves severity serious.
Ah, you're right. I thought kresd continued to be enabled when upgrading to 5.x. I leave this as a note: kresd upstream removed systemd sockets support since 5.0: https://gitlab.nic.cz/knot/knot-resolver/-/issues/485 From NEWS: Knot Resolver 5.0.0 (2020-01-27) ================================ Incompatible changes -------------------- - see upgrading guide: https://knot-resolver.readthedocs.io/en/stable/upgrading.html - systemd sockets are no longer supported (#485) ... Also, upstream includes maintainer scripts to handle changes during upgrading. Cheers, -- Santiago
signature.asc
Description: PGP signature
