From: Daniel Berlin <dberlin@dberlin.org>
To: Christopher Faylor <cgf@redhat.com>
Cc: overseers@sources.redhat.com
Subject: Re: [nick@ilm.com: gcc bugzilla internal server error]
Date: Mon, 22 Sep 2003 21:22:00 -0000 [thread overview]
Message-ID: <D673202D-ED42-11D7-B14F-000A95AF1FAE@dberlin.org> (raw)
In-Reply-To: <20030922195758.GA11945@redhat.com>
Nope, the incoming email is busted
Go to /www/gcc/bugzilla
and run
perl contrib/bugzilla_email_append.pl
and
perl contrib/bug_email.pl
until they stop complaining about missing modules :)
On Sep 22, 2003, at 3:57 PM, Christopher Faylor wrote:
> A #(@*& RHN update upgraded perl to a new version so random perl
> scripts
> are dying due to lack of perl modules that actually exist. I'm working
> on this now, but if you see reports about this, this is what's going
> on.
>
> Dan, can you verify that bugzilla is working? I fixed the obvious perl
> breakage but I want to make sure that everything else is ok.
>
> cgf
>
> ----- Forwarded message from Nick Rasmussen <nick@ilm.com> -----
>
> From: Nick Rasmussen <nick@ilm.com>
> To: sourcemaster@sourceware.org
> Subject: gcc bugzilla internal server error
> Date: Mon, 22 Sep 2003 11:56:30 -0700
>
> I'm running into an internal server error when trying to access the gcc
> bugzilla page:
>
> http://gcc.gnu.org/bugzilla/
>
> and you're listed as the contact.
>
> -nick
>
> ----- End forwarded message -----
next prev parent reply other threads:[~2003-09-22 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 19:57 Christopher Faylor
2003-09-22 21:22 ` Daniel Berlin [this message]
2003-09-22 22:09 ` Christopher Faylor
2003-09-23 0:00 ` Daniel Berlin
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=D673202D-ED42-11D7-B14F-000A95AF1FAE@dberlin.org \
--to=dberlin@dberlin.org \
--cc=cgf@redhat.com \
--cc=overseers@sources.redhat.com \
/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).