public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul <set@pobox.com>
To: gentoo-dev@gentoo.org
Cc: webmaster@oregonstate.edu
Subject: [gentoo-dev] Re: bugs.gentoo.org
Date: Sun, 6 Jul 2003 00:56:33 -0400	[thread overview]
Message-ID: <20030706045633.GA2212@squish.home.loc> (raw)
In-Reply-To: <1057370524.3232.5.camel@localhost>

Grant Goodyear <g2boojum@gentoo.org>, on Fri Jul 04, 2003 [10:02:05 PM] said:
> On Fri, 2003-07-04 at 21:49, Brett I. Holcomb wrote:
> > I'm showing it still is broken.  I get a timeout from the browser when 
> > accessing it and pinging it gives nothing.    Should it take a while before 
> > it's available or should it be online right away?

	Hi;

	Bugs.gentoo.org is broken in a different way now:

Status: 400 Bad request (malformed multipart POST) Content-type:
text/html
Software error:

Undefined subroutine &main::ThrowCodeError called at
Bugzilla/CGI.pm line 78.

For help, please send mail to the webmaster
(webmaster@oregonstate.edu), giving this error message and the
time and date of the error.
Content-type: text/html
Software error:

[Sat Jul  5 21:52:24 2003] processmail: Undefined subroutine
&main::ThrowCodeError called at Bugzilla/CGI.pm line 78.
Compilation failed in require at ./processmail line 31.


	When I submit an attachment to a bug. It appears, but
I dont think I was copied via CC.

Paul
set@pobox.com

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-07-06  4:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-04 22:08 [gentoo-dev] bugs.gentoo.org rob holland
2003-07-05  1:49 ` Brett I. Holcomb
2003-07-05  2:02   ` Grant Goodyear
2003-07-06  4:56     ` Paul [this message]
2003-07-06 11:03       ` [gentoo-dev] bugs.gentoo.org Kurt Lieber
2003-07-06 17:07         ` Weeve
2003-07-06 18:58           ` Michael Cummings

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=20030706045633.GA2212@squish.home.loc \
    --to=set@pobox.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=webmaster@oregonstate.edu \
    /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