Graham Murray posted on Wed, 26 May 2010 06:36:35 +0100 as excerpted: > Mike Frysinger <[email protected]> writes: > >> the bug reporter can open their own bugs. gentoo developers can open >> any bug. that's about it. > > Which can be a pain for other users who suffered the same bug (and are > probably on the CC list), the maintainer says to re-open if the problem > is not fixed, the user finds the problem is still there but the bug > reporter does not re-open the bug. All you can do is add a comment and > hope that a developer sees it and re-opens the bug.
That's what clone bug is for... or at least what /I/ use it for. If I'm not the bug OR/owner and I'm still seeing the bug, I can't open the existing one, but I can clone it, with an explanation why, about the best that can be done under the circumstances. It's then upto the wranglers whether they want to reopen the old one and make the new one a dup, or occasionally there's different minor details (maybe a patch didn't get applied or doesn't apply to a new version), and it can be argued to be a new bug, simply related to the old one. Either way, the wranglers or package maintainer get to decide. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
