Ross Boylan
2004-Oct-02 15:15 UTC
[Logcheck-devel] Bug#270019: 270018, 270019 should remain open
I object to the closing of these bugs on all of the following grounds: 1. They are wishlist items, and the wish has not been resolved, simply dismissed. 2. They are closed on the grounds that the messages are startup messages. Some are, but some are not. 3. The suggestion that startup messages should not be filtered out seems unwarranted. 4. I responded to earlier requests for exact log lines, but the bugs are now being closed because I have not provided filter patterns. This is essentially a policy that a bug should be closed unless the user provides the fix. That is unreasonable. 5. The bugs were closed less than one week (and no weekends) after a note threatening to close them. That is insufficient time for a response. In reviewing the logs, I see that my message with the exact log lines for the serial/ppp drivers did not get through; I can send that. It will take me a little while to do so. In short, I think the bugs should remain open. As they are wishlist items, there is no great urgency in dealing with them, but dismissing them is inappropriate. The grounds given for closing the bug are either incorrect or inappropriate.
maks attems
2004-Oct-02 17:58 UTC
Bug#270018: [Logcheck-devel] Bug#270018: 270018, 270019 should remain open
On Sat, 02 Oct 2004, Ross Boylan wrote:> I object to the closing of these bugs on all of the following grounds: > > 1. They are wishlist items, and the wish has not been resolved, simply > dismissed. > 2. They are closed on the grounds that the messages are startup > messages. Some are, but some are not. > 3. The suggestion that startup messages should not be filtered out > seems unwarranted. > 4. I responded to earlier requests for exact log lines, but the bugs > are now being closed because I have not provided filter patterns. > This is essentially a policy that a bug should be closed unless the > user provides the fix. That is unreasonable. > 5. The bugs were closed less than one week (and no weekends) after a > note threatening to close them. That is insufficient time for a > response. > > > In reviewing the logs, I see that my message with the exact log lines > for the serial/ppp drivers did not get through; I can send that. It > will take me a little while to do so. > > In short, I think the bugs should remain open. As they are wishlist > items, there is no great urgency in dealing with them, but dismissing > them is inappropriate. The grounds given for closing the bug are > either incorrect or inappropriate.neat, both bugs were tagged moreinfo, on several request no valid info were provided. startup messages of daemons shouldn't be filtered by logcheck, exceptions are common stuff for desktop users. the current logcheck maintainers care not having invalid bug reports lying around, so either reopen the bug with requested info or any time later open new bug again with correct information to be handled with. -- maks
Reasonably Related Threads
- Bug#270019: serial/lp rules for logcheck
- [RFC] Documentation clarification: Phabricator, not the lists is the main entry point for new patches
- Bug#448510: logcheck-database: revised pattern for spamd
- Bug#353962: integrate courier file in logcheck-database
- Bug#222240: Ask for frequency during install (logcheck)