On 15/11/06 at 19:00 +0000, Torsten Werner wrote: > On 11/15/06, Frank Küster <[EMAIL PROTECTED]> wrote: > >I strongly disagree. These piupart runs have revealed many *real* RC > >bugs that really should not remain unnoticed. A mail to the maintainer > >won't help in many cases, namely when the maintainer is MIA or just > >doesn't have time for this particular package. A webpage with piuparts > >output won't have any effect. > > But exactly that is done with lintian's output. You can read it on > http://lintian.debian.org/reports/mTorsten_Werner.html#otrs2 which is > linked from the PTS but it is never directly reported as a bug. > > I do not mind getting bug reports with RC severity but they should be > really RC.
You mean like #398626 against jwchat, for which you are the co-maintainer ? > Depending on the complexity of the package (like otrs2) it > might take you hours or days to verify that the bug is RC - at least > when you do not know this package very well. Exactly. That's why I try to do the necessary work to avoid the more obvious false positives, but then file a bug even if I'm not 100% sure that it's valid, and move to the next failure. So far, I've filed more than 120 RC bugs, and about 50 of them were fixed. I've not kept records about the number of false positives, but I don't think there was more than 5 or 10 of them. If I had spent hours trying to verify the bugs, I wouldn't have filed so many bugs, and there would be a lot more unknown RC issues in etch. So far, you have been the only DD to complain about those tests. Maybe you should pick some bugs from http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=submitter&data=lucas%40lucas-nussbaum.net , investigate them, close them if they are not RC, and prove me that I would better have not filed those bugs, since there are so many false positives. Ok, I've lost enough time with this, let's go back to filing RC bugs ;) -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
