Installation fails and the corresponding bug report

[Colin Watson]

On Sat, Feb 21, 2009 at 10:27:31PM -0500, Mackenzie Morgan wrote:
> On Saturday 21 February 2009 7:20:54 pm Vincenzo Ciancia wrote:
> > I will surely do what Colin asked me for any other ubiquity report,
> > but I don't think that I am supposed to do this for ordinary, non
> > hardware-related packages.
> 
> It's mostly just with hardware-related things that it's preferable to
> make a second bug report which, later, a dev can mark as a duplicate
> after they've gotten enough info from both reporters.  Having info
> from two people with different bugs that have similar symptoms in 1
> report makes things difficult.  Ubiquity, since it's concerned with
> installing, is fairly well-tied to hardware for many things (though if
> it was setting the wrong password, that's probably not hardware).

Right, either hardware or very environment-specific things (for instance
it can be quite sensitive to your exact prior partitioning layout).

We ask people to check for duplicates to stop them filing the Nth
iteration of "please upgrade to version X of package Y", or some other
bug that's clearly distinguishable just by reading it. Different rules
ought to apply when we're talking about "this program failed in this
strange way and produced the following output", I think.

-- 
Colin Watson                                       [cjwatson at ubuntu.com]