where no page was returned to the submitter resulting in many
duplicate PR's.
The pipe to sendmail was just being closed without the nice ".\n" to
tell sendmail this is the end of the mail. Now we always send "\n.\n"
to be sure the is a standalone "." on a line.
Why this wasn't a problem before, but is now, I'm not really sure, but
it's probably a perl 5.0 -> 5.8 change which triggered this.
If there are still problems after this commit, please report including
PR number(s).
Prodded by: bugmeister(s)
Co-prodding and testing help: edwin
Not fixed for far too long by: simon
to permit entering the code in lowercase (since the generator doesn't
generate lowercase letters).
Use a relative url to querypr-code.cgi so that mirrors (and test boxes)
can use the query-pr cgis unmodified.
The test for expired codes was inverted, so emptied the database every
time the test ran. Due to the time that the sweep was made, this bug
only hit the user if someone else had submitted a PR in the period
between their obtaining the code and submitting the PR.
This is likely the cause of the unexplained failures that some users
were seeing, which we all blamed on misbehaving caches.
related to querying GNATS together, in order to aid with the upgrade to
GNATS 4.
Switch over dosendpr.cgi and query-pr.cgi to use it.
query-pr-summary.cgi to follow.
This code relies on the netpbm port being installed ; this is
already a dependency of the textproc/docproj port.
This comes courtesy of a collaboration with Eric Anderson
<anderson@centtech.com> who submitted both the idea and the vast
majority of the code to implement it; thank you very much, Eric - this
is a great Christmas present to us and our user community.
in the headers. Although this information can be gleaned from the web
server logs, it should not be necessary to have access to the web
server in order to know who sent in a PR.
