On 10/10/05, Richard Cohen richard@daijobu.co.uk wrote:
Dan Kegel wrote:
Good point. Got a few examples bug numbers that were resolved like that?
See http://bugs.winehq.org/show_bug.cgi?id=2858
I recently resolved a lot of whiskery old bugs, essentially "IE6 installer fails", with directions to the AppDB, because it fixes the user's problem, and IE6 will install the DLLs it needs.
But http://bugs.winehq.org/show_bug.cgi?id=587 "Create replacement of browser component (Internet Explorer/IE)" remains open.
Here is a list of bugs you recently resolved:
2066: IE6 fails to download the mirror list 2945: IE6 installer hangs after a while 3120: Using certain native dlls, IE6 crashes 1293: IE6 setup cannot download setup files 2308: IE6 setup requests all windows be closed..cannot continue 2711: IE6 cannot start because of an unimplemented shdocvw function 2268: Problem with ntdll file api when installing microsoft products
All of the above bugs are marked as duplicates of 2858 (IE6 SP1 fails to install). While most of the above bugs fall under the category of not being able to install IE6, they are individual bugs that need to be addressed, but because 2858 was resolved as FIXED, all of these are now "fixed" when they are more than likely still not fixed. Marking 2858 itself as fixed is an error in that there is no way to install IE6 without using native dlls or special instructions. All of these bugs need to be reopened (including 2858) and marked as blockers of the meta-bug "IE6 fails to install". It's fine to point the users to workarounds in the bugzilla or the wiki, but we can't mark the bugs as fixed just because we have a workaround.
-- James Hawkins