[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: unparseable gnatsd shell error
From: |
Nick Bower |
Subject: |
Re: unparseable gnatsd shell error |
Date: |
Wed, 17 Oct 2001 09:48:43 +0100 |
> At 19:24 16.10.2001 +0100, Nick Bower wrote:
> >nailed it - it's when i change the notify from -1 to 8 in the submitters
> >file for a particular submitter. don't know why this causes a problem
> >for only the non-pending category. must be something to do with at-pr
> >(turning off the notication fixes it) and that fact that i used the
> >customization features to remove:
>
> (snip)
>
> I assume you also removed the Reporter's email field from Gnatsweb?
nup - gnats/gnatsweb is unhacked (except for gnatsweb-site vars). other
than using dbconfig to do the customizations in the intended way,
everything is stock-standard. the reporter's email is valid and
recorded. see later for this separate issue.
this is definately a bug with gnats - i'll submit a PR. i've just
switched back to the distribution dbconfig, set notify-about-expired-prs
= true and i get the same error.
everything is installed in the default locations btw.
> The pending category is handled in a special way, since only the
> GNATS administrator receives notification e-mail when pending PRs
> arrive. If you take a look at PR 284, you'll se an explanation
> together with suggested fix.
thanks - separate issue, and i think it's an obvious use to enter a PR
via the web interface and not have to provide an email, ie for a call
centre in a commerical environment.
cheers, nick