From: Brian Dessent <brian@dessent.net>
To: overseers@sourceware.org
Subject: [Fwd: Creating attachment in bugzilla fails]
Date: Sat, 27 Oct 2007 00:46:00 -0000 [thread overview]
Message-ID: <47228A64.2F831739@dessent.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 26 bytes --]
Spotted on gcc-help list.
[-- Attachment #2: Type: message/rfc822, Size: 3282 bytes --]
From: Johannes Singler <singler@ira.uka.de>
To: gcc-help@gcc.gnu.org
Subject: Creating attachment in bugzilla fails
Date: Fri, 26 Oct 2007 16:46:52 +0200
Message-ID: <4721FDDC.5030008@ira.uka.de>
Hi folks,
I tried to attach a file to a GCC bug report of mine today. However,
there was an error message, the system appears broken to me. Can anybody
confirm this?
This is GCC Bugzilla Version 2.20+
Internal Error
GCC Bugzilla has suffered an internal error. Please save this page and
send it to dberlin@gcc.gnu.org with details of what you were doing at
the time this message appeared.
URL: file:///home/singler/attachment.cgi.html %This URL might be
dynamically inserted, I sent another file.
URL: http://gcc.gnu.org/bugzilla/attachment.cgi
undef error - Undefined subroutine Fh::slice at
data/template/template/en/default/global/hidden-fields.html.tmpl line 58
Bye,
Johannes
reply other threads:[~2007-10-27 0:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47228A64.2F831739@dessent.net \
--to=brian@dessent.net \
--cc=overseers@sourceware.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).