From: Wes Barris <wesb@networkcs.com>
To: gnats-devel@sourceware.cygnus.com
Subject: send-pr broken
Date: Mon, 12 Mar 2001 13:06:00 -0000 [thread overview]
Message-ID: <20010312150537.A91932@us.networkcs.com> (raw)
The cvs version of gnats: send-pr is broken. After building, installing,
and configuring gnats, send-pr produces this error:
root@kirby# send-pr
It seems that send-pr is not installed with your organization set to a useful
value. To fix this, you need to edit the configuration
file and fill in the organization with the correct value.
It seems that send-pr is not installed with your unique submitter-id.
You need to run
install-sid YOUR-SID
where YOUR-SID is the identification code you received with `send-pr'.
`send-pr' will automatically insert this value into the template field
`>Submitter-Id'. If you've downloaded `send-pr' from the Net, use `net'
for this value. If you do not know your id, run `send-pr --request-id' to
get one from your support site.
root@kirby#
I snooped through the send-pr code and found this snippet:
# Configuration file to be read. It must be a shell script that can redefine
# the variables above to fit a local configuration.
CONFIGFILE=/usr/local/etc/gnats/send-pr.conf
if [ -r $CONFIGFILE ]; then
. $CONFIGFILE
fi
It looks like send-pr is looking for a file named "send-pr.conf". This
is not included in the gnats distribution. I don't see any documentation
on it anywhere.
--
-----------------------------------------------------------------------
Wes Barris wes@networkcs.com
Network Computing Services, Inc. 612.337.3423
-----------------------------------------------------------------------
Today's fortune: I think animal testing is a terrible idea; they get
all nervous and give the wrong answers.
next reply other threads:[~2001-03-12 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 13:06 Wes Barris [this message]
2001-03-12 13:45 ` Yngve Svendsen
2001-04-08 11:28 ` Milan Zamazal
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=20010312150537.A91932@us.networkcs.com \
--to=wesb@networkcs.com \
--cc=gnats-devel@sourceware.cygnus.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).