aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSergey Poznyakoff <gray@gnu.org.ua>2009-02-21 13:30:51 +0200
committerSergey Poznyakoff <gray@gnu.org.ua>2009-02-21 13:31:26 +0200
commit1213cf065e9b3a5fb45d00276b3d168462838c17 (patch)
tree8d8f3cb7617465139f0051c10ef80fa9c2c91369
parent5bfe69d55cff8940fd3a84ff479e6e8308b164f4 (diff)
downloadwydawca-1213cf065e9b3a5fb45d00276b3d168462838c17.tar.gz
wydawca-1213cf065e9b3a5fb45d00276b3d168462838c17.tar.bz2
Remove trailing whitespace
-rw-r--r--doc/Makefile.am4
-rwxr-xr-xdoc/check-docs.sh6
-rw-r--r--doc/mastermenu.el4
-rw-r--r--doc/rendition.texi2
-rw-r--r--doc/wydawca.texi144
-rw-r--r--src/builtin.c22
-rw-r--r--src/cmdline.opt2
-rw-r--r--src/config.c94
-rw-r--r--src/directive.c36
-rw-r--r--src/diskio.c76
-rw-r--r--src/exec.c12
-rw-r--r--src/getopt.m460
-rw-r--r--src/gpg.c34
-rw-r--r--src/interval.c8
-rw-r--r--src/mail.c30
-rw-r--r--src/method.c22
-rw-r--r--src/process.c18
-rw-r--r--src/sql.c14
-rw-r--r--src/triplet.c48
-rw-r--r--src/verify.c22
-rw-r--r--src/wydawca.c46
-rw-r--r--src/wydawca.h18
-rw-r--r--tests/Makefile.am4
-rw-r--r--tests/atlocal.in2
-rw-r--r--tests/mailstats.at26
25 files changed, 377 insertions, 377 deletions
diff --git a/doc/Makefile.am b/doc/Makefile.am
index 7afd676..0ef1e64 100644
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -50,13 +50,13 @@ check-format:
check-options:
@check-docs.sh options \
'/OPTIONS_BEGIN/,/OPTIONS_END/s/OPTION( *\([^,][^,]*\),.*/\1/pg' \
'/@c option --/{s///;s/^\(help\|version\|usage\)//;p}' \
$(top_srcdir)/src/cmdline.opt -- \
$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I $(srcdir) -E - \
- $(info_TEXINFOS)
+ $(info_TEXINFOS)
check-refs:
@sed -e = $(info_TEXINFOS) $(wydawca_TEXINFOS) | \
sed -n 'N;/@FIXME-.*ref/{s/\(^[0-9][0-9]*\).*@FIXME-.*ref{\([^}]*\)}.*/$(info_TEXINFOS):\1: \2/gp}' > $@-t; \
if [ -s $@-t ]; then echo "Unresolved cross-references:"; cat $@-t;\
fi
@@ -90,13 +90,13 @@ check-unrevised:
else \
rm $@-t; \
fi
all-check-docs: check-format check-options check-refs check-fixmes check-unrevised check-writeme
-check-docs:
+check-docs:
$(MAKE) -k all-check-docs
master-menu:
emacs -batch -l mastermenu.el -f make-master-menu $(info_TEXINFOS)
untabify:
diff --git a/doc/check-docs.sh b/doc/check-docs.sh
index c0b0487..16b6b0e 100755
--- a/doc/check-docs.sh
+++ b/doc/check-docs.sh
@@ -39,13 +39,13 @@ do
if [ "$1" = "--" ]; then
shift
break;
fi
source="$source $1"
shift
-done
+done
TEMPDIR=/tmp/mfck.$$
mkdir $TEMPDIR || exit 1
trap 'rm -rf $TEMPDIR' 1 2 13 15
sed -n "$codesexp" $source | sort | uniq > $TEMPDIR/src
@@ -54,20 +54,20 @@ $* | \
| sort | uniq > $TEMPDIR/doc
join -v1 $TEMPDIR/src $TEMPDIR/doc > $TEMPDIR/src-doc
join -v2 $TEMPDIR/src $TEMPDIR/doc > $TEMPDIR/doc-src
(if [ -s $TEMPDIR/src-doc ]; then
echo "Not documented $item:"
- cat $TEMPDIR/src-doc
+ cat $TEMPDIR/src-doc
fi
if [ -s $TEMPDIR/doc-src ]; then
echo "Non-existing $item:"
cat $TEMPDIR/doc-src
fi) > $TEMPDIR/report
-if [ -s $TEMPDIR/report ]; then
+if [ -s $TEMPDIR/report ]; then
cat $TEMPDIR/report
rm -rf $TEMPDIR
exit 1
else
rm -rf $TEMPDIR
exit 0
diff --git a/doc/mastermenu.el b/doc/mastermenu.el
index 3ab3341..a38e824 100644
--- a/doc/mastermenu.el
+++ b/doc/mastermenu.el
@@ -23,17 +23,17 @@
;;; Commentary:
;; This file redefines texinfo-master-menu-list so that it takes into
;; account included files.
-;; Known bugs: @menu without previous sectioning command will inherit
+;; Known bugs: @menu without previous sectioning command will inherit
;; documentation string from the previous menu. However, since such a
;; menu is illegal in a texinfo file, we can live with it.
-(require 'texinfo)
+(require 'texinfo)
(require 'texnfo-upd)
(defun texinfo-master-menu-list-recursive (title)
"Auxiliary function used by `texinfo-master-menu-list'."
(save-excursion
(let (master-menu-list)
diff --git a/doc/rendition.texi b/doc/rendition.texi
index 016583d..c4092ea 100644
--- a/doc/rendition.texi
+++ b/doc/rendition.texi
@@ -1,10 +1,10 @@
@c Let's use the concept of 'renditions' by Fra@,{c}ois Pinard
@c I extended it by adding a FIXME_FOOTNOTE variable, which controls
@c whether FIXME information should be placed in footnotes or
-@c inlined.
+@c inlined.
@c ======================================================================
@c This document has three levels of rendition: PUBLISH, DISTRIB or PROOF,
@c as decided by @set symbols. The PUBLISH rendition does not show
@c notes or marks asking for revision. Most users will prefer having more
@c information, even if this information is not fully revised for adequacy,
diff --git a/doc/wydawca.texi b/doc/wydawca.texi
index 3f5a682..876a8fa 100644
--- a/doc/wydawca.texi
+++ b/doc/wydawca.texi
@@ -156,13 +156,13 @@ distributed tarball must be placed, and clear-signs it using his
@file{/incoming/ftp}.
@cindex release submission daemon
From now on, it is the responsibility of a @dfn{release submission daemon}
to scan the source directories, gather the triplets, verify them,
and to move any files that had passed the verification successfully to
-their distribution sites.
+their distribution sites.
@command{Wydawca} is such a release submission daemon. It is able to
handle any number of @samp{source/destination} pairs, offers an
extensible logging and mail notification mechanism, allowing both
package maintainers and site administrators to be immediately notified
about any occurring problems.
@@ -262,13 +262,13 @@ etc.
@xopindex{config-file, described}
@sopindex{c, described}
@command{Wydawca} gets all information it needs from its
@dfn{configuration file} (@pxref{wydawca.rc}). The default
configuration file is @file{@var{sysconfdir}/wydawca.rc}, but if it is
located elsewhere, you can specify its new location with the
-@option{--config-file} (@option{-c}) command line option.
+@option{--config-file} (@option{-c}) command line option.
@anchor{lint}
@xopindex{lint, described}
@sopindex{t, described}
If you wish to check your configuration file for syntax errors, use
@option{--lint} (@option{-t}) command line option. When given this
@@ -305,38 +305,38 @@ of information the program reports when it runs. By default it is 0,
meaning to report only errors and other critical conditions. Raising
it may be necessary when debugging new configurations. Each
@option{-d} option raises the level by one, so you can say
@command{wydawca -dd} to obtain level 2, for example. The maximum
debugging level currently is 4, which prints an impractically big
amount of information, which is useful mainly for @command{wydawca}
-developers.
+developers.
@anchor{dry-run}
@xopindex{dry-run, described}
@sopindex{n, described}
Yet another debugging facility is the @option{--dry-run}
(@option{-n}) option. It instructs @command{wydawca} to avoid doing any
modifications to the disk contents, but to verbosely print any actions
it would have taken. Its set the debugging level to 1 and directs the
diagnostics output to the standard error, as if @option{--debug
--stderr} options have been given. You can raise debugging level
further by supplying additional @option{--debug} options. The
@option{--dry-run} option is useful when testing new configurations,
-for example:
+for example:
@smallexample
$ wydawca -c new.cfg --dry-run
@end smallexample
@xopindex{help, described}
@sopindex{h, described}
@xopindex{version, described}
@sopindex{v, described}
In addition, the two usual informational options are available as well:
@option{--help} (@option{-h}) prints a short usage summary, and
-@option{--version} (@option{-v}) prints program version number.
+@option{--version} (@option{-v}) prints program version number.
@node configuring, wydawca.rc, starting, Top
@chapter How to Configure @command{wydawca}.
@UNREVISED
The @command{wydawca} configuration file has a simple line-oriented
syntax. Empty lines are ignored. Comments are introduced by a pound
@@ -375,13 +375,13 @@ by itself. Within a compound statement any number of another
statements (both simple and compound) may appear.
@cindex scope of a statement
When a statement appears outside of any block statement, we say that
it appears at @dfn{the top level} or @dfn{its scope is global}. When
it appears within a block statement, we say that @dfn{it has block
-scope}.
+scope}.
This subsection will guide you through the @command{wydawca}
configuration on a step-by-step basis.
@menu
* include::
@@ -399,13 +399,13 @@ configuration on a step-by-step basis.
@section Include Statement
@cindex inclusion, configuration file
@kwindex include
@UNREVISED
You can request inclusion of any file into your configuration file
using @code{include} statement. Its only argument supplies the name of
-file to be included. For example:
+file to be included. For example:
@smallexample
include /etc/wydawca/msg
@end smallexample
The effect of the above statement is that the contents of file
@@ -449,13 +449,13 @@ argument must be separated from it by a single equals sign, as in
use it as the new inclusion path. Otherwise, if argument is omitted,
the include directory is defined as a directory part of the full
file name of the configuration file. This form might be useful when
debugging new configurations. For example, the following command
runs @command{wydawca} in dry run mode, using configuration file
@file{./test.rc}, and looking for include files in the current working
-directory:
+directory:
@smallexample
$ wydawca --config ./test.rc -I --dry-run
@end smallexample
Please notice, that unlike many other programs (e.g. @command{cc} or
@@ -469,13 +469,13 @@ effect.
@cindex syslog, configuration
@kwindex syslog-facility
@UNREVISED
Unless told otherwise, @command{wydawca} uses @code{syslog} to print
its diagnostic messages. By default, the program uses the
@samp{local1} facility. To change this, use @code{syslog-facility}
-statement:
+statement:
@smallexample
syslog-facility local2
@end smallexample
@kwindex authpriv@r{, syslog facility}
@@ -485,13 +485,13 @@ syslog-facility local2
@kwindex local0 @r{through} local7@r{, syslog facilities}
@kwindex mail@r{, syslog facility}
It takes a single argument, denoting the facility to use. Allowed
values are: @samp{auth}, @samp{authpriv}, @samp{cron}, @samp{daemon},
@samp{ftp}, @samp{local0} through @samp{local7}, and
@samp{mail}. These names are case-insensitive and may be optionally
-prefixed with @samp{log_} (case-insensitive as well).
+prefixed with @samp{log_} (case-insensitive as well).
@kwindex syslog-tag
@cindex syslog tag, configuring
Another thing you may wish to tune is the @dfn{syslog tag}, a string
identifying each message issued by the program. By default it is a
string @samp{wydawca}. To change it, use @code{syslog-tag} statement:
@@ -522,13 +522,13 @@ Several statements in configuration file may need to access
databases simultaneously, the only restriction being that they must be
@command{MySQL} databases (this restriction will be removed in future
releases).
@kwindex sql
A database is defined using @code{sql} block statement. It has the
-following syntax:
+following syntax:
@smallexample
@group
sql @var{identifier}
@var{statements}
end
@@ -594,21 +594,21 @@ in the table below:
@table @asis
@kwindex builtin@r{, access method type}
@item builtin
This method is reserved for future use.
-@kwindex sql@r{, access method type}
+@kwindex sql@r{, access method type}
@item sql
Retrieve data from an @acronym{SQL} database. Currently only
@command{MySQL} is supported.
@kwindex external@r{, access method type}
@item external
Retrieve data using an external program. This method is reserved for
-future use.
+future use.
@end table
Access methods are defined in configuration file using the
following syntax:
@smallexample
@@ -621,13 +621,13 @@ where @var{method-name} is the predefined name of the access method,
@dfn{parameters}, that describe the method.
Access method statements can appear either in the global scope of
the configuration file, or inside a @code{directory} statement
(@pxref{directory pairs}). Global definitions affect all directory
pairs in the configuration file, and ones inside a @code{directory}
-statement override them for that particular directory pair.
+statement override them for that particular directory pair.
There are four predefined methods, which are described later in this
section. The @var{type} must currently always be @samp{sql}. The
@var{param1} is an identifier of one of the preceding @code{sql} blocks
(@pxref{sql}), which determines database name and user
credentials needed to access it. The @var{param2} is an @acronym{SQL}
@@ -664,33 +664,33 @@ shortest initial prefix of that value, not containing slashes.
@cindex Savane
The rest of this section describes the access methods (referred to
by @var{method-name} in the syntax above) used by
@command{wydawca}. They are illustrated by example definitions, based
on the database structure used in
-@uref{http://gna.org/projects/savane, @command{Savane} system}.
-
+@uref{http://gna.org/projects/savane, @command{Savane} system}.
+
@deffn {Access Method} gpg-key
@cindex @acronym{PGP} public key, retrieving
@cindex public @acronym{PGP} key, retrieving
Retrieve the public @acronym{PGP} key of a user. This method must
return exactly one string.
The sample definition is:
-
+
@smallexample
gpg-key sql default SELECT gpg_key \
FROM user \
WHERE user_name='%@{user@}'
@end smallexample
@end deffn
-
+
@deffn {Access Method} project-owner
Retrieve email addresses and real names of administrators (or
@dfn{owners}) of a project. It may return any number of rows, each one
-consisting of two columns: an email address and a user name, in this order.
+consisting of two columns: an email address and a user name, in this order.
@smallexample
@group
project-owner sql default SELECT user.email, user.realname \
FROM user,user_group,groups \
WHERE user_group.user_id=user.user_id \
@@ -701,33 +701,33 @@ project-owner sql default SELECT user.email, user.realname \
@end smallexample
@end deffn
@deffn {Access Method} user-data
Return email address and real name of a user. This method must
return one tuple, consisting of two columns: an email address and a user
-name, in this order.
+name, in this order.
@smallexample
@group
user-data sql default SELECT email, realname \
FROM user \
WHERE user_name='%@{user@}'
@end group
@end smallexample
@end deffn
-
+
@deffn {Access Method} verify-user
Verify if a user is allowed to make uploads for a certain project. This
method must return the system name of the user if he is allowed to
make uploads.
The following definition allows uploads only for project
administrators:
-
+
@smallexample
-@group
+@group
verify-user sql default SELECT user.user_name \
FROM user,user_group,groups \
WHERE user_group.user_id=user.user_id \
AND user_group.group_id=groups.group_id \
AND user_group.admin_flags = 'A' \
AND groups.unix_group_name='%@{project@}' \
@@ -747,13 +747,13 @@ transfer operations by using @code{sendfile} system call. If it
fails, and the error is recoverable, @command{wydawca} falls back to
copying files using user space. This is indicated by one of the following
warning messages:
@smallexample
sendfile: copying @var{source} to @var{dest} failed: Invalid value
-
+
sendfile: copying @var{source} to @var{dest} failed: Function not
implemented
@end smallexample
@kwindex enable-sendfile
If you encounter any of these, disable @code{sendfile} by adding the
@@ -762,47 +762,47 @@ following to your configuration file:
@smallexample
enable-sendfile no
@end smallexample
In particular, you need to disable sendfile when compiling
@command{wydawca} for Linux kernels starting from version 2.6.9 and
-higher.
+higher.
@node archivation
@section Archivation
@cindex archivation, defined
@UNREVISED
There may be cases when project maintainers need to overwrite
existing distributed files with another ones, having the same names.
(Note, hovewer, that this practice is not encouraged). In that case,
@command{wydawca} needs to first @dfn{archive} the already existing
file, and then put the new one in its place. Moreover, the directive
file format allows maintainers to explicitly require archivation of
-their existing files.
+their existing files.
@cindex archivation methods
@kwindex archive
@code{Wydawca} supports two basic archivation methods: to a
@command{tar} file, and to a separate directory. The method to be used
is configured using @code{archive} statement. This statement can
appear either in the global scope, in which case it affects all
directory pairs, or within a @code{directory} block (@pxref{directory
-pairs}), where it affects only the given directory pair.
+pairs}), where it affects only the given directory pair.
This statement takes several arguments. The first argument specifies
-the archivation type:
+the archivation type:
@table @asis
@kwindex none@r{, archivation}
@item none
Disable archivation.
-
+
@kwindex tar@r{, archivation}
@item tar
Use @command{tar} archive.
-
+
@kwindex directory@r{, archivation}
@item directory
Use a separate directory or a directory hierarchy.
@end table
When the archivation type @asis{tar} is used, the second argument to
@@ -828,19 +828,19 @@ specify its full file name using @code{tar-program} statement.
be stored in a directory specified by the second argument to
@code{archive}. If it begins with a slash (i.e. represents an absolute
file name), an exact copy of the distribution directory hierarchy will
be created under it. For example, given this configuration:
@smallexample
-archive directory /var/backups/gnu
+archive directory /var/backups/gnu
@end smallexample
@noindent
all files from @file{/home/@/ftp/@/gnu/@/tar} will be archived in
@file{/var/@/backups/@/gnu/@/tar}, and files from
-@file{/home/@/ftp/@/gnu/@/tar/@/old}
+@file{/home/@/ftp/@/gnu/@/tar/@/old}
will be archived in @file{/var/@/backups/@/gnu/@/tar/@/old}, etc.
If the directory name does not begin with a slash, it will be located
immediately under the corresponding distribution directory. Following
our example, the following @code{directory} settings:
@@ -849,13 +849,13 @@ archive directory .archive
@end smallexample
@noindent
mean that files from @file{/home/@/ftp/@/gnu/@/tar} will be archived in the
directory @file{/home/@/ftp/@/gnu/@/tar/@/.archive}, files from
@file{/home/@/ftp/@/gnu/@/tar/@/old} --- in
-@file{/home/@/ftp/@/gnu/@/tar/@/.archive/@/old}, etc.
+@file{/home/@/ftp/@/gnu/@/tar/@/.archive/@/old}, etc.
@anchor{backup-methods}
@vindex version-control @r{Emacs variable}
When using the @samp{directory} archivation type, it may happen that the
archive file with the same name as the one about to be created already
exists. The third argument to @code{archive} specifies how to handle
@@ -883,23 +883,23 @@ of the others.
@kwindex simple@r{, backup method}
Always make simple backups.
@end table
@vindex VERSION_CONTROL
- If no backup method is given, the value of the @env{VERSION_CONTROL}
+ If no backup method is given, the value of the @env{VERSION_CONTROL}
environment variable will be used. And if @env{VERSION_CONTROL} is
not set, the @samp{existing} is used by default.
@cindex implicit signature archivation
@cindex signature files, archivation
Usually signature files (i.e. the ones ending with @samp{.sig}) should
be located in the same directory as the files they belong to. To
enforce this rule, @command{wydawca} implements
@dfn{implicit signature archivation} facility. It works as
-follows. When archivation of @var{file} is requested by
+follows. When archivation of @var{file} is requested by
@code{archive: @var{file}} statement in the directive
file (@pxref{FTP Upload Directive File - v1.1, Standalone directives,,
maintain.info, Information For Maintainers of GNU Software}),
@command{wydawca} also checks if the file named @file{@var{file}.sig}
exists. If so, it is archived along with @file{@var{file}}.
@@ -936,16 +936,16 @@ source directory and @code{destination}, which specifies location of
the destination directory. Apart from these obligatory statements, a
@code{directory} block may contain an @code{archive} statement
(@pxref{archivation}) and access method definitions (@pxref{access
methods}). Any of these statements, if present, overrides the
corresponding global definition for this directory pair. A
@code{directory} statement ends with the @code{end} keyword on a
-separate line.
+separate line.
For example, the following definition says that valid uploads to
-@file{/home/ftp/incoming/ftp} should be transferred to @file{/home/ftp/gnu}:
+@file{/home/ftp/incoming/ftp} should be transferred to @file{/home/ftp/gnu}:
@smallexample
@group
directory ftp://ftp.gnu.org.ua
source /home/ftp/incoming/ftp
destination /home/ftp/gnu
@@ -1002,13 +1002,13 @@ symlinks created: 0
symlinks removed: 0
@end smallexample
Each item in this statistics is configurable, and a
unique configuration keyword is associated with it. The statistics
items and their corresponding keywords are described in the table
-below:
+below:
@table @code
@kwindex errors@r{, statistics}
@item errors
Any error that occurred during the run.
@@ -1097,13 +1097,13 @@ statistics none
@kwindex all@r{, statistics}
Another special keyword is @samp{all}, that enables all statistics
output. This keyword may also be followed by any number of statistics
keywords, which are in this case @emph{excluded} from the
summary. For example, to output all statistics, except errors and
-warnings one would set:
+warnings one would set:
@smallexample
statistics all errors warnings
@end smallexample
@node notification
@@ -1153,13 +1153,13 @@ mailer @var{url}
@end smallexample
@cindex @acronym{URL}, mailer
@cindex mailer @acronym{URL}
A mailer @acronym{URL} begins with a protocol specification.
Two protocol specifications are currently supported: @samp{sendmail}
-and @samp{smtp}. The former means to use a
+and @samp{smtp}. The former means to use a
@command{sendmail}-compatible program to send mails. Such a program
must be able to read mail from its standard input and must support the
following options:
@table @option
@item -oi
@@ -1186,20 +1186,20 @@ mailer sendmail:/usr/sbin/sendmail
@end smallexample
A special form of a sendmail @acronym{URL}, consisting of protocol
specification only (@samp{sendmail:}) is also allowed. It means
``use the sendmail binary from the @code{_PATH_SENDMAIL}
macro in your @file{/usr/include/paths.h} file''. This is the default
-mailer.
+mailer.
The @samp{smtp} protocol means to use an @acronym{SMTP} server directly.
In this case, mailer location consists of two slashes,
followed by the @acronym{IP} address or host name of the @acronym{SMTP}
server, and, optionally, the port number. If the port number is
present, it is separated from the rest of @acronym{URL} by a colon.
-For example:
+For example:
@smallexample
@group
mailer smtp://remote.server.net
mailer smtp://remote.server.net:24
@end group
@@ -1281,13 +1281,13 @@ The first argument supplies the identifier of a message template,
which should be previously defined by a @code{define-message}.
The rest of arguments is a list of statistics keywords as described in
@ref{statistics}. A report will be sent only if statistics
counters for at least one of the requested categories are not
zero. For example, the following statement requires sending
notifications only if there occurred any errors or access violation
-attempts, or any bad signature was uploaded:
+attempts, or any bad signature was uploaded:
@smallexample
mail-admin-stat stat-msg errors access-violations bad-signatures
@end smallexample
@kwindex admin-address
@@ -1318,17 +1318,17 @@ The meta-variables available for use in admin notifications are:
@kwindex stat:complete_triplets
@item stat:complete_triplets @tab Number of complete triplets
processed.
@kwindex stat:incomplete_triplets
@item stat:incomplete_triplets @tab Number of incomplete triplets left
in the source directory.
-@kwindex stat:bad_triplets
+@kwindex stat:bad_triplets
@item stat:bad_triplets @tab Number of bad triplets seen.
@kwindex stat:expired_triplets
-@item stat:expired_triplets @tab Number of expired triplets.
-@kwindex stat:triplet_success
+@item stat:expired_triplets @tab Number of expired triplets.
+@kwindex stat:triplet_success
@item stat:triplet_success @tab Number of successfully processed
triplets.
@kwindex stat:uploads
@item stat:uploads @tab Number of successful uploads.
@kwindex stat:archives
@item stat:archives @tab Number of archivations performed.
@@ -1344,55 +1344,55 @@ triplets.
define-message stat-msg
Subject: Wydawca stats
This is to notify you that my run on %@{date@}
caused the following results:
-errors ............................. %@{stat:errors@}
-warning ............................ %@{stat:warnings@}
-bad signatures ..................... %@{stat:bad_signatures@}
-access violation attempts .......... %@{stat:access_violations@}
+errors ............................. %@{stat:errors@}
+warning ............................ %@{stat:warnings@}
+bad signatures ..................... %@{stat:bad_signatures@}
+access violation attempts .......... %@{stat:access_violations@}
Regards,
Wydawca
-end
+end
@end smallexample
@node event notification
@subsection Event Notification
@cindex event notification
@UNREVISED
The following @dfn{events} are tracked during the execution. Any of
them can be used to trigger an email notification of any party
concerned: the system administrator, project administrators, or
the user that initiated the upload:
-
+
@table @code
@kwindex success
@item success
Successful upload.
-
+
@kwindex bad-ownership
@item bad-ownership
An unauthorized user attempted to upload files for their project.
-
+
@kwindex bad-directive-signature
@item bad-directive-signature
The directive signature does not match the public key of the
uploader.
-
+
@kwindex bad-detached-signature
@item bad-detached-signature
The detached signature does not match the public key of the
uploader.
@end table
-@kwindex notify-event
+@kwindex notify-event
These notifications are configured using the following statement:
-@smallexample
+@smallexample
notify-event @var{event} @var{who} @var{msg-id}
@end smallexample
@noindent
where @var{event} is one of the events described above, @var{msg-id}
is the identifier of a previously defined message template
@@ -1419,13 +1419,13 @@ project administrators and to the user who did the upload, using two
different templates:
@smallexample
notify-event bad-directive-signature user user-bad-directive-signature
notify-event bad-directive-signature owner owner-bad-directive-signature
@end smallexample
-
+
The following macro-variables may be used in templates for these
notifications:
@table @code
@kwindex project
@item project
@@ -1461,13 +1461,13 @@ A full listing of the uploaded triplet. It is equivalent to:
@end smallexample
See below for an example.
@kwindex triplet:upload
@item triplet:upload
-Listing of the uploaded files (see below).
+Listing of the uploaded files (see below).
@kwindex triplet:dist
@item triplet:dist
Listing of the main distribution file (see below).
@kwindex triplet:sig
@@ -1501,17 +1501,17 @@ example, here is a possible @code{%@{triplet:full@}} listing:
@smallexample
-rw-r--r-- gray users 2707278 2007-09-06 22:14:35 tar-1.18.tar.gz
-rw-r--r-- gray users 189 2007-09-06 22:14:35 tar-1.18.tar.gz.sig
-rw-r--r-- gray user 62 2007-09-06 22:14:35 tar-1.18.tar.gz.directive.asc
@end smallexample
-
+
The following example shows how to configure success notification
for the user:
-
+
@smallexample
# @r{Define a message template.}
define-message user-success
Subject: Upload of %@{project@} successful
Upload of %@{project@} to %@{dir@} finished successfully.
@@ -1568,13 +1568,13 @@ triplet file.
@end table
@vindex VERSION_CONTROL
@cindex backups
For @samp{directive} archivation type, the optional @var{backup-method}
parameter specifies how to back up an existing file whose name
-coincides with the one @command{wydawca} is about to create. If
+coincides with the one @command{wydawca} is about to create. If
@var{backup-method} is not specified, the value of the @env{VERSION_CONTROL}
environment variable will be used. And if @env{VERSION_CONTROL} is not set,
the @samp{existing} method (see below) is used by default.
@vindex version-control @r{Emacs variable}
This option corresponds to the Emacs variable @samp{version-control};
@@ -1597,13 +1597,13 @@ Always make simple backups.
@end table
@end deffn
@deffn {Wydawca Statement} syslog-facility @var{facility}
-Output diagnostics to the given syslog facility. The @var{facility}
+Output diagnostics to the given syslog facility. The @var{facility}
may be one of the following: @samp{user}, @samp{daemon}, @samp{auth},
@samp{authpriv}, @samp{local0} through @samp{local7}, and @samp{mail}.
the string matching is case insensitive. optionally, @samp{log_}
(sense-insensitive as well) prefix may be prepended to @var{facility}.
@xref{syslog}, for more information.
@@ -1681,13 +1681,13 @@ Do not print any statistics.
Sets the amount of time after which any unprocessed file will be
removed.
The @var{interval} is a string that defines a time interval, much
the same way we do this in English: it consists of one or more pairs
``@samp{number} @samp{time unit}''. For example, the following are
-valid interval specifications:
+valid interval specifications:
@smallexample
@group
1 hour
2 hours 35 seconds
1 year 7 months 2 weeks 2 days 11 hours 12 seconds
@@ -1709,13 +1709,13 @@ Sets the file name of the @command{tar} utility. If @var{string} is
not an absolute file name, it will be searched in @env{PATH}.
@xref{archivation}, for more information on when this statement is needed.
@end deffn
@deffn {Wydawca Block Statement} sql @var{identifier}
-This statement begins a MySQL database definition. It may contain
+This statement begins a MySQL database definition. It may contain
several sub-statements, defining how to access the database. The
statement ends with the @code{end} keyword on a line by itself.
@xref{sql}, for more information.
@var{Identifier} is the symbolic name that can be used in
@@ -1777,21 +1777,21 @@ directory [@var{url}]
source @var{name}
destination @var{name}
[@var{statements}]
end
@end group
@end smallexample
-
+
@noindent
where optional @var{url} specifies the @acronym{URL} of the
distribution site