On 7/16/20 9:37 AM, Santiago Ruano Rincón wrote:
> I leave this as a note: kresd upstream removed systemd sockets support
> since 5.0:
> https://gitlab.nic.cz/knot/knot-resolver/-/issues/485
I'm afraid I don't understand what this has to with the original problem.
the original problem is the foll
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
> ha
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
Hi Daniel,
On Sun, 1 Mar 2020 21:00:20 +0100 Daniel Baumann
wrote:
> severity 952673 serious
> thanks
>
> bumping severity as this breaks all our systems atm. it can be
> reproduced on a clean install, and then installing knot-resolver, which
> will not start any kresd instances.
>
> a manual
4 matches
Mail list logo
