send-pr broken

send-pr broken

[Wes Barris]

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.

Re: send-pr broken

[Yngve Svendsen]

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

I went through the process of installing Gnats 4 from CVS in order to check 
the docs, and you have found exactly the same as I - the documentation is 
far from up-to-date. Besides, a standard send-pr.conf file should 
definitely be created. I have created a GNATS report about this on 
sources.redhat.com, so this has been recorded. Development on version 4 is 
proceding, but slowly (hint hint), so fixing these things may take some time.

I ended up using somthing like the following. It's been a couple of weeks 
since I did the install, but I think this is exactly the same as we had in 
our v3 config:

GNATS_ADDR="xxxxxxx@clustra.com"
GNATS_ADMIN="xxxxxxxxx@clustra.com"
GNATS_SITE="xxxxxxxxxx"
SUBMITTER="xxxxxxxxxx"
DEFAULT_ORGANIZATION="xxxxxxxxxxxxxxxxx"
DEFAULT_RELEASE="<prompt>"
NOTIFY=0
ACKNOWLEDGE=0
DEFAULT_SUBMITTER="xxxxxxxxxxx"
KEEP_RECEIVED_HEADERS=1
BDAY_START=8
BDAY_END=16
BWEEK_START=1
BWEEK_END=5
DEBUG_MODE=0

If only I could find the time, I'd clean up my installation notes and make 
some preliminary docs available. Maybe later this week.

Yngve Svendsen
IS Engineer
Clustra AS, Trondheim, Norway

Re: send-pr broken

[Milan Zamazal]

>>>>> "WB" == Wes Barris <wesb@networkcs.com> writes:

    WB> root@kirby# send-pr It seems that send-pr is not installed with
    WB> your organization set to a useful value.  To fix this, you need
    WB> to edit the  configuration file and fill in the organization
                  ^^^^

The name of the file should be there, but wasn't because of a typo in
the text (fixed now).  The file is basically a shell script sourced in
by send-pr.  There are also other means to set the parameters,
e.g. through shell variables, but I think that is undocumented as well.
Yes, the documentation will be fixed.

Milan Zamazal

-- 
  _/_\_/_  o     _\_/_\_  o     _/_\_/_  o     _\_/_\_  o    BEWARE!
-<_|_|_|_><--  -<_|_|_|_><--  -<_|_|_|_><--  -<_|_|_|_><--   *Bugs* are
   / \ /   o      \ / \   o      / \ /   o      \ / \   o     approaching!