Translations by Julien Cristau

Accept --help, --version command-line options.

The most recent version of this utility is on http://jeroen.A-Eskwadraat.nl/sw/annotate

If a I<.commands> file is specified it is first validated (see the details at I<ftp://ftp-master.debian.org/pub/UploadQueue/README>), and the name specified in the Uploader field is used for signing.

WEBSITE/SUPPORT

Note that svn/svk tagging conventions vary, so debcommit uses L<svnpath(1)> to determine where the tag should be placed in the repository.

If this is set to I<yes>, then it is the same as the --no-acks command line parameter being used. The default is I<no>.

The directory name is checked by testing whether the current directory name (as determined by B<pwd>(1)) matches the regex given by the configuration file option DEVSCRIPTS_CHECK_DIRNAME_REGEX or by the command line option B<--check-dirname-regex> I<regex>. Here I<regex> is a Perl regex (see B<perlre>(3perl)), which will be anchored at the beginning and the end. If I<regex> contains a '/', then it must match the full directory path. If not, then it must match the full directory name. If I<regex> contains the string \'PACKAGE', this will be replaced by the source package name, as determined from the changelog. The default value for the regex is: \'PACKAGE(-.*)?', thus matching directory names such as PACKAGE and PACKAGE-version.

B<annotate-output> does not currently accept any command-line options, so --help, --version, and that kind of stuff do not currently work (unless you install /usr/bin/--help ;) ).

TODO

B<annotate-output> I<program> [I<args> ...]

This specifies the package name to be used in the new changelog; this may only be used in conjunction with the B<--create> option.

B<--no-preserve>

If this is set to I<yes>, then it is the same as the --no-acks command line parameter being used. The default is I<no>.

# This the format for an FTP site: # Full-site-with-pattern [Version [Action]] ftp://ftp.tex.ac.uk/tex-archive/web/c_cpp/cweb/cweb-(.*)\e.tar\e.gz \e debian uupdate

package [ <package> ... ]

Note that svn/svk tagging conventions vary, so debcommit uses L<svnpath(1)> to determine where the tag should be placed in the repository.

Display the page listing the requested bugs in a web browser using L<sensible-browser(1)>.

L<svnpath(1)>.

Get rich with this very sophisticated piece of bash.

ANNOTATE-OUTPUT

Debian Utilities

DEBIAN

NAME

annotate-output - annotate program output with time and stream

SYNOPSIS

DESCRIPTION

B<annotate-output> will execute the specified program, while prepending every line with the current time and O for stdout and E for stderr.

OPTIONS

B<-h>, B<--help>

Display a help message and exit successfully.

EXAMPLE

$ annotate-output make 21:41:21 I: Started make 21:41:21 O: gcc -Wall program.c 21:43:18 E: program.c: Couldn't compile, and took me ages to find out 21:43:19 E: collect2: ld returned 1 exit status 21:43:19 E: make: *** [all] Error 1 21:43:19 I: Finished with exitcode 2

BUGS

Since stdout and stderr are processed in parallel, it can happen that some lines received on stdout will show up before later-printed stderr lines (and vice-versa).

This is unfortunately very hard to fix with the current annotation strategy. A fix would involve switching to PTRACE'ing the process. Giving nice a (much) higher priority over the executed program could however cause this behaviour to show up less frequently.

The program does not work as well when the output is not linewise. In particular, when an interactive program asks for input, the question might not be shown until after you have answered it. This will give the impression that the annotated program has hung, while it has not.

SEE ALSO

This program is community-supported (meaning: you'll need to fix it yourself). Patches are however appreciated, as is any feedback (positive or negative).

AUTHOR

B<annotate-output> was written by Jeroen van Wolffelaar E<lt>jeroen@wolffelaar.nlE<gt> This manpage comes under the same copyright as annotate-output itself, read /usr/bin/annotate-output (or wherever you install it) for the details.

ARCHPATH

archpath - output arch (tla/Bazaar) archive names, with support for branches

B<archpath>

B<archpath> I<branch>

B<archpath> I<branch>--I<version>

B<archpath> is intended to be run in an arch (tla or Bazaar) working copy.

In its simplest usage, B<archpath> with no parameters outputs the package name (archive/category--branch--version) associated with the working copy.

If a parameter is given, it may either be a branch--version, in which case B<archpath> will output a corresponding package name in the current archive and category, or a plain branch name (without \(oq--"), in which case B<archpath> will output a corresponding package name in the current archive and category and with the same version as the current working copy.

This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a command like this: