On Thu, 2008-03-27 at 05:04 +1100, Tim Richardson wrote: > Sven, > I prefer to close my reports when I can confirm that the bug is fixed, > which I have not yet been able to do. I reported the bug upstream > myself, so I am aware of the claim that it is fixed. You have closed the > Debian bug without confirming yourself that it is fixed; I don't think > this is a sound way to proceed. I am not sure that the packages have > actually migrated to unstable yet (I have a machine that runs unstable > but because I am moving countries it is packed away for a couple more > weeks; a few days ago I checked the status of gnome 2.22: the packages > where in experimental still). If this is true, it means you have closed > a bug that is still actually present in the main Debian repositories, > and it's hard for me to see how this is correct. I'm a fairly new Debian > user, so perhaps I have something to learn here, but imagine if you did > this to a Release Candidate bug! > > I do from time to time close other people's bugs, but only after I have > verified that the problem is fixed and it is clear that the original > reporter is not going to close it. To be honest, I don't think it is > good practice to close someone else's report without even verifying a > rumoured upstream fix :-) > > It is my intention to reopen the bug because I run reports on my open > bugs to keep on top of them, and a closed bug will not be picked up by > my review process. But I will wait for your feedback, since I am new > here.
Hi, It's a good idea if you cc me directly, that way I won't easily miss anything directed to me! The bug was closed with a version. The BTS tracks versions, so the bug is actually only closed for version 2.22 (which is in the experimental archive), once this version reaches unstable, the bug is considered closed in unstable etc. You will however, only get one announcement about it being fixed, and not one when the fix reaches unstable (or testing). This is a shortcoming of the BTS. I'm not sure if there's an open bug report about it. Also, keep in mind that the GNOME packages receive a lot of bug reports, and far from all reporters take the same care as you to make sure their issues are fixed, so personally, I prefer to mark bugs as done as soon as I can, and I generally trust upstream. After all, closed bug reports can be reopened. As for this problem in particular, I have now confirmed it to be fixed. I hope this is a satisfactory explanation :) (For the record, I'm not a DD or a maintainer, I only help out with bug triage and do some bug fixing if I can....) -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22
signature.asc
Description: This is a digitally signed message part
