Bug#952673: does not start automatically anymore on fresh installs

2020-07-16 Thread Daniel Baumann
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

Bug#952673: does not start automatically anymore on fresh installs

2020-07-16 Thread Santiago Ruano Rincón
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 >

Bug#952673: does not start automatically anymore on fresh installs

2020-07-10 Thread Daniel Baumann
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

Bug#952673: does not start automatically anymore on fresh installs

2020-07-10 Thread Santiago Ruano Rincón
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

Bug#952673: does not start automatically anymore on fresh installs

2020-03-01 Thread Daniel Baumann
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 "systemctl start kresd@1" after every boot workarounds it. Regards, Daniel

Bug#952673: does not start automatically anymore on fresh installs

2020-02-27 Thread Daniel Baumann
upon further look, it seems that lib/systemd/system/kresd@.service lib/systemd/system/kresd@1.service is required in knot-resolver.links, the corresponding git commit removing it (id 3903815) seems to rely on upstreamed patches that apparently are not (entirely?) there (yet?) or have changed in

Bug#952673: does not start automatically anymore on fresh installs

2020-02-27 Thread Daniel Baumann
Package: knot-resolver Severity: important Version: 5.0.1-1 Hi, thank you so much for uploading knot-resover 5 to sid, much appreciated. While the upgrade from 3 works flawlessly, installing version 5 on a system does not start a kresd instance in the system-kresd slice automatically. Hence no