Hi coldtobi, coldtobi <[email protected]> writes: > Is this the way systemd people generally respond to problem reports? Just > closing bugs and hide (possible) problems? I'm very disappointed. You know, in > Debian we do not hide problems. Typically I wouldn’t even respond to this, but your last sentence strikes me as pretty arrogant¹, and the second sentence is a baseless accusation, so here goes:
Closing a bug is not “hiding problems”. We (the systemd maintainers in Debian) generally tend to close bugs early (and reopen on demand) to keep the amount of bugs manageable. We think this is good for us, since it makes our work possible in the first place, it’s good for new contributors who see a well-tended buglist and it’s good for users who don’t have to scroll through pages of non-issues, wishlist items that noone will ever fix and other reports like that. IMO, the Debian bugtracker severely lacks a good way of displaying/filtering bugs. In case we had that, I wouldn’t have any problem with leaving bugs like this open forever. Also, I’d like to point out that we actually _do_ respond in the first place, and that within one hour (!) of your report. That’s a kick-ass response time, and having responses at all is something that enough other Debian packages don’t even achieve, unfortunately. ① You are trying to lecture us about how Debian works, while there is no agreed-upon set of rules that backs up your particular interpretation of how Debian should work. This comes across as you imposing your will onto us. -- Best regards, Michael -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
