From: nick@brainstorm.co.uk
To: gnats-devel@sources.redhat.com
Subject: gnatsd: Could not resolve database alias? (and suggestions)
Date: Thu, 07 Jun 2001 07:38:00 -0000 [thread overview]
Message-ID: <3B1F91D0.D3E591E2@brainstorm.co.uk> (raw)
In-Reply-To: <Pine.BSF.4.33.0106071349070.36910-100000@taygeta.dbai.tuwien.ac.at>
I get this error when trying to run gnatsweb:
"Error: Could not resolve database alias (Brainstorm)."
I had gnats/gnatsweb working just 2 weeks ago on another machine, but
now have reinstalled it with "--with-gnats-root=/home/gnats/gnats-db".
Could this be the difference? I can't think what else it could be.
The pulldown database widget on the gnatsweb login page is empty, yet I
can do this fine:
gnats> cat /tmp/bugpr | queue-pr -q
gnats> queue-pr --run
The config file is setup with our database name "Brainstorm" obviously.
It sounds like a gnatsweb error, but the message is coming from the
gnats code itself. Any help appreciated.
Also, a couple of suggestions:
1) It doesn't make sense to me for the file generated by mkcat
(Brianstorm in our case) to be in <prefix>/share/gnats rather than
<GNATS_ROOT>/gnats-db...
2) I found Gnats didn't work when I had a space in the category or
submitter ID - it would be good if we could use real product and company
names as the submitter IDs instead of names with underscores.
Otherwise keep up the good work - I'm looking forward to gnats4!
nick
next prev parent reply other threads:[~2001-06-07 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 13:04 Announcing gnatsweb 2.8.1 Yngve Svendsen
2001-06-07 4:51 ` Gerald Pfeifer
2001-06-07 7:38 ` nick [this message]
2001-06-07 7:49 ` gnatsd: Could not resolve database alias? (and suggestions) Yngve Svendsen
2001-06-07 8:00 ` nick
2001-06-07 8:04 ` Yngve Svendsen
2001-06-11 4:54 ` gnatsweb plans? nick
2001-06-11 13:35 ` Yngve Svendsen
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=3B1F91D0.D3E591E2@brainstorm.co.uk \
--to=nick@brainstorm.co.uk \
--cc=gnats-devel@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).