Hi daniel, Daniel Baumann <daniel.baum...@progress-technologies.net> writes: >> By applying the attached patch, systemd users will enjoy a fully working >> vsftpd on their machines: it will get enabled and started properly (even >> if installed on sysvinit and later switching to systemd). > > can you explain what's not working with the current package and what > dh-systemd would 'fix'? requesting a change without explaining why > doesn't make sense. Sure, sorry for not being more clear about it:
Currently, when installing vsftpd, the unit file vsftpd.service does not get enabled within the vsftpd package. We (as in the systemd maintainers) realized that before the wheezy release and added an ugly kludge which would just enable any unit (with a hardcoded blacklist) unconditionally. We now must get rid of this kludge, or our users cannot disable services (using “systemctl disable”). Applying the patch I sent will add the appropriate code to enable your service file. I hope that makes it clearer. Let me know if you have any further questions. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
