public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Molenda <jason-gcclist@molenda.com>
To: Daniel Berlin <dberlin@dberlin.org>, overseers@gcc.gnu.org
Subject: Re: Web part of bugzilla is ready (fwd)
Date: Wed, 05 Feb 2003 08:04:00 -0000	[thread overview]
Message-ID: <20030205000409.A70837@molenda.com> (raw)
In-Reply-To: <20030204043613.GB27417@redhat.com>; from cgf@redhat.com on Mon, Feb 03, 2003 at 11:36:13PM -0500

On Mon, Feb 03, 2003 at 11:36:13PM -0500, Christopher Faylor wrote:
> Ok, I did a little research.

Sorry for not following up to this - I should have answered.


> >> 1. I need to know how gcc-gnats actually works (IE the mail flow).
> >> To auto-parse incoming gnats reports, i need to feed the entire
> >> message
> >> into a perl script that has access to bugzilla.
> >>
> >> How does mail to gcc-gnats end up on gcc-bugs? (IE is it
> >> auto-mirroring in qmail, or is it done by a gnats handling script).
> 
> There is a qmail alias set up which redirects mail delivered to
> gcc-gnats to a program (/usr/local/libexec/gnats/queue-pr) which
> eventually sends email to gcc-bugs and gcc-prs.

Yeah, queue-pr (and gnatsd (gnatsweb)) save the incoming PRs as
plain text in a holding directory until a crontab runs (once every
ten minutes) to read in the newly-arrived PRs and put them in their
proper place under the proper uid.

Specifically, /qmail/alias/.qmail-gcc-gnats contains

|/sourceware/infra/bin/mlcheck --preferred-domain=gcc.gnu.org
|/qmail/bin/preline /usr/local/libexec/gnats/queue-pr --directory=/sourceware/gnats/gcc-db -q

More than one program can be called out of .qmail-gcc-gnats, so if
you want to also get a copy of newly arriving gnats PRs, another
script can be handed them as they come in.  They don't yet have
their gnats #'s assigned, of course (you'd have to add a script to
the gcc-prs mailing list to see that).  And you're running under
the one of the mail processing UIDs so you want to exercise some
security caution with what you plug in here.

> >> 2. How does gcc-bugs email get appended to a bug?  For bugzilla, it's,
> >> as one would imagine, a perl script that does it.
> 
> I think that bug data is only appended when gcc-gnats is cc'ed.

Yeah, e-mail messages being appended to a bug will come in through
gcc-gnats@gcc and they'll be added to the existing PR if their PR
category/# matches correctly.

When a user changes the state of a PR or whatever through gnatsweb, a
notification is sent out to the gcc-prs list.  Note that nothing is
sent to gcc-gnats@, so if you just monitor gcc-gnats you'll only see
new PRs and PRs with e-mail additions, not state changes.  If you
monitor gcc-prs, you'll see new PRs, additions to PRs, and state
changes to PRs.  At least you _should_ see all those things. :-)


J

  reply	other threads:[~2003-02-05  8:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04  4:17 Daniel Berlin
2003-02-04  4:36 ` Christopher Faylor
2003-02-05  8:04   ` Jason Molenda [this message]
2003-02-06  0:31     ` Daniel Berlin
2003-02-08  2:45       ` Christopher Faylor
2003-02-08  4:53         ` Daniel Berlin
2003-02-08 16:25           ` Christopher Faylor
2003-02-08 16:36             ` Christopher Faylor
2003-02-08 17:06               ` Daniel Berlin
2003-02-10  1:23             ` Daniel Berlin
2003-02-21  1:13               ` Christopher Faylor
2003-02-08 12:39         ` Joseph S. Myers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030205000409.A70837@molenda.com \
    --to=jason-gcclist@molenda.com \
    --cc=dberlin@dberlin.org \
    --cc=overseers@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).