Re: /etc/modules comment is wrong
On Sun, May 22, 2005 at 10:05:05AM -0600, s. keeling wrote:
> Incoming from David Jardine:
> > On Sat, May 21, 2005 at 03:08:02PM -0400, Kamaraju Kusumanchi wrote:
> > > David Jardine wrote:
> > >
> > > >I've never had the courage to file a bug and wouldn't know where to
> > > >start, but I'm sure someone else on the list can explain.
> > >
> > > It is really easy to file a bug report. Just install reportbug
> >
> > Thanks for the explanation and encouragement, raju. I've disovered
> > that I did in fact install reportbug, but looking at the manpage I
> > realise that I'm way out of my depth here. When it comes to bugs
>
> See /etc/reportbug.conf. There's lots of comments explaining things.
> Minus comments, mine is so:
>
> -----------------------------------
> bts debian
> submit
> mua 'mutt -H'
> header "X-Silly-Header: I have edited my /etc/reportbug.conf"
> no-ldap
> query-bts
> cc
> config-files
> compress
> no-ldap
> mirror us
> mirror uk
> sign gpg
> email "keeling@spots.ab.ca"
> realname "s. keeling"
> editor 'emacs -nw'
> -----------------------------------
>
> When you run reportbug (as a user, not as root), it'll walk you
> through the whole process. Prior to that, try to find out what Debian
> package it is that you're reporting a bug for (ie., "dpkg -S
> /some/relevant/file"); it'll ask for that. Then it'll query the bts
> for you, displaying extant bugs, and ask you if your problem is
> mentioned in them.
>
> If it's not already there, report it. reportbug will ask questions,
> open an editor to compose mail where you can supply relevant details,
> etc. That'll go out to the package's maintainer, who'll mail you for
> more details, an explanation of what's happening, or perhaps a
> solution. Kinda fun, really, and can be quite educational.
You people are just unbelievably kind to take the trouble with
people like me. I really appreciate it.
Okay, bugs, here I come...
--
David Jardine
"Running Debian GNU/Linux and
loving every minute of it." -L. von Sacher-M.(1835-1895)
Reply to: