Control: tags -1 moreinfo Sam Hartman: >>>>>> "Niels" == Niels Thykier <ni...@thykier.net> writes: > control: tags -1 -moreinfo > > (I hope this supplies the info you need; obviously retag if you have > more questions.) >
It did; but it gave me a new question. :) Just remove it again, when you answer. I have been using a BTS filter to keep the debhelper bug list (more) manageable - See [1] vs [2] for comparison (which filters out about 25% of the open bugs). > > Niels> Hi Sam, > > Niels> Thanks for the bug report. > > Niels> It sounds like you rather want krb5-kdc not to start on > Niels> initial installation. > > That's not what I want at all. > > I want to try and start it, but I don't want a failure to start to be > considered an error that causes package installation to fail. > [...] > > > --Sam > As I understood your original mail, it sounded like we expect the service to fail because the user has not configured it yet. I think I am missing the point of having it start automatically if it will not work out of the box. Can you elaborate on what makes you want it to start automatically? Note that debhelper's tooling for init scripts vs. systemd has the asymmetry that the systemd tooling ignores all failures basically. As I understood the systemd maintainers who wrote the original systemd tooling, they were of the mind that failing installation because a service fails to start was not desirable. But unlike sysvinit, systemd makes it easy for the administrator to tell which services have issues - so I am a bit hesitant to make these symmetric in general. Thanks, ~Niels [1] https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debhelper [2] https://bugs.debian.org/cgi-bin/pkgreport.cgi?exclude=tags%3Awontfix;exclude=tags%3Apending;exclude=tags%3Amoreinfo;exclude=tags%3Ahelp;src=debhelper
