Bug#997835: you could add powerdns init script

Matthew Vernon matthew at debian.org
Tue Oct 26 10:15:39 BST 2021


On 25/10/2021 17:21, Mathieu ROY wrote:

> powerdns packaged removed then working init script. You might consider 
> including them in your package.

> I was about to send you a working version but the debian developer in 
> charge of powerdns, apparently tied to powerdns development, made me 
> reconsider using this software, since apparently making it easy to 
> maintain is perceived as a felony.

Thanks for the report. I would happily take a patch incorporating the 
powerdns init script, especially if you can confirm it works on a 
testing system.

[Otherwise I can presumably find it myself, but I can't really test it 
and it's obviously more work for me ;-)]

Apropos bugs 997054 and 997056, I think the maintainer overreacted, but 
I think that they felt that your reference to 964139 was an (implicit) 
threat to raise the question of the powerdns init script with the 
technical committee. I don't think that's a particularly helpful line to 
take with maintainers who want to drop an init script - asking them to 
reconsider or otherwise send the script to orphan-sysvinit-scripts is a 
good approach, but there's enough lingering hurt around init systems 
that anything that looks like a threat is unlikely to be productive.

In any case, I see nothing in Chris' email that suggests you can't 
provide the init script to the orphan-sysvinit-scripts package.



More information about the Debian-init-diversity mailing list