public inbox for
 help / color / mirror / Atom feed
From: Chad Walstrom <>
Subject: Re: Gnatsweb: Unparseable reply from gnatsd
Date: Mon, 14 Mar 2005 20:57:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1110827078.3886.17.camel@localhost.localdomain>

[-- Attachment #1.1: Type: text/plain, Size: 1147 bytes --]

On Mon, Mar 14, 2005 at 02:04:38PM -0500, Jeremy Cowgar wrote:
> I use the emacs interface all day long and have no problems. This is
> the only information I can find about the problem. Does anyone have
> any ideas? I did go through and reformat quite a bit in the dbconfig
> to better suit our needs. Everything I did was remove items, I added
> no new ones, just removed those we did not need. I have been up and
> down the config file w/no luck in finding anything wrong.

Make sure your "initial-entry" and "index" specs in dbconfig no longer
contain the fields you don't need.  Then, reindex the database with
gen-index.  I don't recall if gnatsweb requires certain fields to be
present or not, but browse through the source code just to make certain.

> The gnatsweb edits bugs just fine, it just cannot create them. Send-pr
> and the emacs interface works great w/no problems.

The emacs interface may not be making assumptions about which fields are
available whereas gnatsweb may be.

Chad Walstrom <> 
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

Help-gnats mailing list

  reply	other threads:[~2005-03-14 19:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 19:41 Jeremy Cowgar
2005-03-14 20:57 ` Chad Walstrom [this message]
2005-03-15  3:38   ` Jeremy Cowgar
2005-03-15 17:36     ` Stuart Stevens
     [not found] <>
2005-03-15 17:54 ` Jeremy Cowgar
2005-03-15 18:11   ` Chad Walstrom
2005-03-16  6:43     ` Chad Walstrom

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:

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

  git send-email \ \ \ \

* 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).