Package: at
Version: 3.1.10
Severity: normal

After updating to Etch, some of my scripts stopped working because the
batch command no longer understands the -f parameter.  In Sarge this
parameter did work (I did not see a note about this during the update,
shouldn't there be a message for apt-listchanges to inform about
incompatible changes?).

Looking through the at manpage, I found the description of batch's
parameters in the SYNOPSIS to be correct:

SYNOPSIS
       at [-V] [-q queue] [-f file] [-mldbv] TIME
       at -c job [job...]
       atq [-V] [-q queue]
       atrm [-V] job [job...]
       batch


But in the DESCRIPTION batch is listed as still having the -f
parameter:

DESCRIPTION
[...]
       For both at and batch, commands are read from standard input or the
       file specified with the -f option and executed.


The manpage should not contradict itself.
(Why not bringing the -f parameter back?)

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages at depends on:
ii  exim4-daemon-light [mail-tr 4.63-17      lightweight exim MTA (v4) daemon
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared libraries
ii  libpam0g                    0.79-4       Pluggable Authentication Modules l
ii  lsb-base                    3.1-23.1     Linux Standard Base 3.1 init scrip

at recommends no packages.

-- no debconf information

-- 
....Christian.Garbs.....................................http://www.cgarbs.de

"I know not with what weapons World War III will be fought, but World
 War IV will be fought with sticks and stones."    -- Albert Einstein

Attachment: signature.asc
Description: Digital signature

Reply via email to