Thank you for the report Aristarkh. It is odd that this was fixed so long ago - 1:9.11.4+dfsg-1 is what the debian bug states.
That was only pushed to Debian buster in: 195 bind9 (1:9.11.4+dfsg-1) unstable; urgency=medium 196 197 [ Bernhard Schmidt ] 198 * Use systemd Type=forking to signal daemon init. 199 Thanks to Elie Roudninski (Closes: #900788) ... 209 -- Ondřej Surý <email address hidden> Sat, 14 Jul 2018 12:27:56 +0000
But I don't see it on any path to Debian/sid - not in the past changelogs nor in the currently used .service files.
I need to ask if this might have had an intentional reason ... or if it really was "lost again" later on.
Thank you for the report Aristarkh.
It is odd that this was fixed so long ago - 1:9.11.4+dfsg-1 is what the debian bug states.
That was only pushed to Debian buster in:
195 bind9 (1:9.11.4+dfsg-1) unstable; urgency=medium
196
197 [ Bernhard Schmidt ]
198 * Use systemd Type=forking to signal daemon init.
199 Thanks to Elie Roudninski (Closes: #900788)
...
209 -- Ondřej Surý <email address hidden> Sat, 14 Jul 2018 12:27:56 +0000
But I don't see it on any path to Debian/sid - not in the past changelogs nor in the currently used .service files.
I need to ask if this might have had an intentional reason ... or if it really was "lost again" later on.