Re: Bugzilla question with respect to .NET 1.1SP1

[James Mckenzie]

Paul Vriens
> Sent: Jan 26, 2009 4:45 AM
> To: "[e-mail]" 
> 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

Bugzilla question with respect to .NET 1.1SP1

[Paul Vriens]

James Mckenzie wrote:
> Paul Vriens
> > Sent: Jan 26, 2009 4:45 AM
> > To: "[e-mail]" 
> > 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?

Bugzilla question with respect to .NET 1.1SP1

[Alexandre Julliard]

Paul Vriens  writes:
> So that means bug 14850 needs to be reopened with a link to 13995?

No, if it's the same bug it should be a single report. If .NET doesn't
install then obviously all apps that try to install it will be broken,
it doesn't make sense to create a separate bug for each app that suffers
from the problem.

Bugzilla question with respect to .NET 1.1SP1

[Paul Vriens]

Alexandre Julliard wrote:
> Paul Vriens  writes:
> > So that means bug 14850 needs to be reopened with a link to 13995?
>
> No, if it's the same bug it should be a single report. If .NET doesn't
> install then obviously all apps that try to install it will be broken,
> it doesn't make sense to create a separate bug for each app that suffers
> from the problem.

Only a comment will not increase the 'popularity' of a bug though. How do we 
determine the priority of such a bug? (Or don't we deal with priorities anyway?).

Bugzilla question with respect to .NET 1.1SP1

[Alexandre Julliard]

Paul Vriens  writes:
> Alexandre Julliard wrote:
> > Paul Vriens  writes:
> > > So that means bug 14850 needs to be reopened with a link to 13995?
> >
> > No, if it's the same bug it should be a single report. If .NET doesn't
> > install then obviously all apps that try to install it will be broken,
> > it doesn't make sense to create a separate bug for each app that suffers
> > from the problem.
>
> Only a comment will not increase the 'popularity' of a bug though. How
> do we determine the priority of such a bug? (Or don't we deal with
> priorities anyway?).

We don't really, and a separate bug which will be closed as duplicate
wouldn't help anyway. If there is evidence that it affects a lot of apps
you can make the severity major.

Bugzilla question with respect to .NET 1.1SP1

[Paul Vriens]

Alexandre Julliard wrote:
> Paul Vriens  writes:
> > Alexandre Julliard wrote:
> > > Paul Vriens  writes:
> > > > So that means bug 14850 needs to be reopened with a link to 13995?
> > >
> > > No, if it's the same bug it should be a single report. If .NET doesn't
> > > install then obviously all apps that try to install it will be broken,
> > > it doesn't make sense to create a separate bug for each app that suffers
> > > from the problem.
> >
> > Only a comment will not increase the 'popularity' of a bug though. How
> > do we determine the priority of such a bug? (Or don't we deal with
> > priorities anyway?).
>
> We don't really, and a separate bug which will be closed as duplicate
> wouldn't help anyway. If there is evidence that it affects a lot of apps
> you can make the severity major.

OK, fair enough.

I'll just have this already existing bug linked to from the appdb then.