[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: systemd-fsck?



I think this is a good example of how not to respond to reports, as we recently
discussed on this list.  Even though most parts are excellent. :-)

On Sat, May 10, 2014 at 03:36:26PM +0200, Laurent Bigonville wrote:
> The root cause of this bug is [...]

This part is useful.

> So please get dirmngr fixed instead of blaming systemd/logind.

This is the part you should _NEVER_ do.  It is YOUR responsibitiliy, as a
maintainer (you are the maintainer, right?), to make sure that a bug that is
reported in the wrong place gets sent to the right place.  It is GOOD that a
user reports it (it is a real bug), and it isn't a problem if technically it
isn't in your package; you just fix that.

These sort of responses are giving you a bad name.  If you'd leave that
statement out, the mail would be helpful.  With it, the user will feel that you
tell them to "go away" (which was complained about in this very thread).

> I've reopened the initial bug opened against dirmngr about the fact that the
> initscript is calling su (#668890)

This again, is the right thing to do.

Instead of complaining that the user reported the bug to the wrong package,
please thank them for reporting it.  They're spending their time to make Debian
better.  They are not trying to defame you.

Thanks,
Bas


Reply to: