Re: [GnomeMeeting-list] Bug#128588: gnomemeeting: Limited diagnostic information
- From: Christian Rose <menthos menthos com>
- To: gnomemeeting-list gnome org
- Subject: Re: [GnomeMeeting-list] Bug#128588: gnomemeeting: Limited diagnostic information
- Date: 11 Jan 2002 01:44:32 +0100
tor 2002-01-10 klockan 15.28 skrev Dale E Martin:
> > > More likely the opposite, since most problems are likely not caused by
> > > the packaging, and there is always the danger of all bug reports that
> > > are upstream problems not getting forwarded upstream.
> > > In any case, how to file GnomeMeeting bugs is described in detail on the
> > > GnomeMeeting homepage.
> >
> > I shall add information about this on the next (Debian?) release of
> > GnomeMeeting. I agree with your statement, but I doubt that users of the
> > Debian package will put effort into looking up where to report upstream
> > bugs. They will more likeley use reportbug or some other report-tool,
> > which is easy, fast, and the maintainer will handle the rest.
>
> Standard protocol would be for the maintainer to forward the bug upstream,
> if it's an upstream problem. They report that they've done this to the BTS
> and the filer. When it's fixed upstream then they close bug in the Debian
> BTS as well.
>
> Typically, as a Debian user and developer, I file bugs via "reportbug"
> which goes to the Debian BTS, but it provides over good info like what
> versions of libs the app is linked against and that kind of stuff. If an
> applicaton says "loud and clear" to report problems to some other place, of
> course, then if I think it's an upstream problem I might file it upstream.
The problem is the "I might". I think far too many possibly useful bug
reports in general get stuck downstream :-(
Perhaps "reportbug" could be extended to automatically figure out the
right BTS, like Ximian's bug-buddy tool does today.
Christian
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]