Paul Vriens <paul.vriens.w...@gmail.com> wrote: >Sent: Jan 26, 2009 7:10 AM >To: James Mckenzie <jjmckenzi...@earthlink.net> >Cc: "wine-devel@winehq.org" <wine-devel@winehq.org> >Subject: Re: Bugzilla question with respect to .NET 1.1SP1 > >James Mckenzie wrote: >> Paul Vriens <paul.vriens.w...@gmail.com> >>> Sent: Jan 26, 2009 4:45 AM >>> To: "wine-devel@winehq.org" <wine-devel@winehq.org> >>> Subject: Bugzilla question with respect to .NET 1.1SP1 >>> >>> Hi, >>> >>> I have an application that won't install because it's trying to first do an >>> install of .NET 1.1 and straight after that an upgrade/update to SP1. >>> >>> .NET 1.1SP1 install fails (see bug >>> http://bugs.winehq.org/show_bug.cgi?id=13995). >>> >>> Should I create a new bug report and say that it depends on 13995, should I >>> create a bugreport that is then marked as a duplicate of 13995 or should I >>> just >>> add my findings to 13995? >>> >> If it is a separate application, separate bug report. If the same >> application is affected, update. Since it appears that you are using a >> different application to install .NET 1.1 SP1, then a new report should be >> submitted and then linked to issue 13995. The reason I state this is that >> additional problems may be discovered, even after .NET 1.1 SP1 runs and >> installs. It may also be possible to get your application to run, even if >> .NET 1.1 SP1 will not fully install. >> >> I would classify this as an application does not install because .NET 1.1 >> SP1 will not install properly. >> >> James McKenzie >> >> >So that means bug 14850 needs to be reopened with a link to 13995? > If the problem may be outside of .NET 1.1 SP1, yes. If not, then the answer is no. I'll have to look at the two bug reports and see if they are related and true duplicates.
James McKenzie
