From: Yngve Svendsen <yngve.svendsen@clustra.com>
To: "Choi, Jang-Wook" <choijo@adc.co.kr>, help-gnats@gnu.org
Cc: Milan Zamazal <pdm@zamazal.org>
Subject: Re: send-pr error!
Date: Fri, 14 Dec 2001 03:09:00 -0000 [thread overview]
Message-ID: <5.1.0.14.2.20011214113951.00a0f450@10.10.1.1> (raw)
Message-ID: <20011214030900.yEx84Ph_15X2z1yAnKrxtkjmTh86jhRQAOEBySkGd7U@z> (raw)
In-Reply-To: <20011214173108.A15498@adc.co.kr>
At 17:31 14.12.01 +0900, Choi, Jang-Wook wrote:
>Hello, I installed the latest gnats in my redhat linux.
>
>I just followed the install instructions of gnats.info, but when I execute
>send-pr from the shell, I got an error message. I read manuals but still
>don't know what's wrong. Somebody please help me.
If you by "latest version" mean that you have checked out a development
snapshot of version 4, this is a known problem. Most of the remote site
functionality was ripped out of GNATS 4, since it was never implemented
properly in previous versions, and send-pr version 4 still needs some work
and a few design decisions to replace the stuff that's gone. The problem
you have is related to the fact that the "new" send-pr hasn't been
documented properly. Send-pr is now supposed to have its own config file
where stuff like submitter-id is set. Anyway, I recommend that you don't
deploy send-pr around your network until we got these things sorted out.
Milan: We need to decide exactly how send-pr is supposed to work when
installed at remote locations (There is an empty section in the
installation chapter waiting for material on installation at remote sites,
and the send-pr documentation in chapter 2 still describes the old
version). Are we going to keep the "request-sid" functionality (see
http://bugs.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gnats&pr=193 ),
or should remote submitters get an ID through other channels?
Yngve Svendsen
GNATS doc guy
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2001-12-14 3:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 9:23 Choi, Jang-Wook
2001-11-06 9:25 ` Yngve Svendsen [this message]
2001-11-12 10:06 ` Milan Zamazal
2001-11-12 10:40 ` Yngve Svendsen
2001-11-18 19:55 ` Milan Zamazal
2001-12-23 12:36 ` Milan Zamazal
2001-12-15 10:52 ` Yngve Svendsen
2001-12-15 7:24 ` Milan Zamazal
2001-12-14 3:09 ` Yngve Svendsen
2001-12-14 0:43 ` Choi, Jang-Wook
2001-11-08 10:23 Chad C. Walstrom
2001-11-08 10:23 ` Jamin W. Collins
2001-11-08 13:05 ` Chad C. Walstrom
2001-11-08 18:22 ` Jamin W. Collins
2001-11-09 2:55 ` Chad C. Walstrom
2001-11-09 14:16 ` Jamin W. Collins
2001-11-09 14:17 ` Yngve Svendsen
2001-12-15 2:54 ` Yngve Svendsen
2001-11-10 2:46 ` Milan Zamazal
2001-12-15 7:24 ` Milan Zamazal
2001-12-14 20:45 ` Jamin W. Collins
2001-12-14 15:24 ` Chad C. Walstrom
2001-12-14 11:39 ` Jamin W. Collins
2001-12-14 10:55 ` Chad C. Walstrom
2001-12-14 8:34 ` Jamin W. Collins
2001-11-08 10:23 ` Yngve Svendsen
2001-11-08 13:08 ` Chad C. Walstrom
2001-11-09 18:10 ` Milan Zamazal
2001-12-15 7:24 ` Milan Zamazal
2002-01-17 19:14 ` Hugo Gayosso
2001-12-14 11:17 ` Chad C. Walstrom
2001-12-14 9:28 ` Yngve Svendsen
2001-12-14 8:27 ` Chad C. 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:
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=5.1.0.14.2.20011214113951.00a0f450@10.10.1.1 \
--to=yngve.svendsen@clustra.com \
--cc=choijo@adc.co.kr \
--cc=help-gnats@gnu.org \
--cc=pdm@zamazal.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).