[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug Reporting system



Bill Mitchell writes:

> > Many users have difficulty determining which package is responsible for
> > a problem.  How are they going to determine if a bug is architecture-specific?
> 
> That's a good argument for adding the `Architecture:' field to
> bug reports.  Users may not be able to determine that the bug
> is architecture-specific, but they can report that the bug was
> observed on a sparc (or whatever).

This is already the case if they use clameters bug program.
I believe that most bugs nowardays are written with such a 
tool.

> If the package maintainer (who probably has an i386 system, but
> could have an m68k or whatever) finds that the bug is repeatable,
> he can address it as an architecture-independent bug.  If the
> bug report specifies an architecture different than his, and
> the bug is not repeatable and/or there are some indications that
> it might be architecture specific, he can look for help from
> someone on the appropriate arch list.

seconded.

Regards

	Joey

-- 
  / Martin Schulze  *  joey@infodrom.north.de  *  26129 Oldenburg /
 /                              No question is too silly to ask, /
/    but, of course, some are too silly to answer  -- perl book /


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .


Reply to: