Package: sysstat
Version: 8.1.8-1
Severity: normal

I just upgraded sysstat from version 8.1.7-1 and received the following 
message in the process:
====cut here=====
Setting up sysstat (8.1.8-1) ...
Installing new version of config file /etc/cron.d/sysstat ...
Installing new version of config file /etc/init.d/sysstat ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
*** WARNING: ucf was run from a maintainer script that uses debconf, but
             the script did not pass --debconf-ok to ucf. The maintainer
             script should be fixed to not stop debconf before calling 
ucf,
             and pass it this parameter. For now, ucf will revert to 
using
             old-style, non-debconf prompting. Ugh!

             Please inform the package maintainer about this problem.
=====cut here====
The tool asks that you be informed, and so I do.

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sysstat depends on:
ii  bzip2                         1.0.5-1    high-quality block-sorting file co
ii  debconf [debconf-2.0]         1.5.24     Debian configuration management sy
ii  libc6                         2.7-18     GNU C Library: Shared libraries
ii  lsb-base                      3.2-20     Linux Standard Base 3.2 init scrip
ii  ucf                           3.0012     Update Configuration File: preserv

Versions of packages sysstat recommends:
ii  cron                          3.0pl1-105 management of regular background p

Versions of packages sysstat suggests:
pn  isag                          <none>     (no description available)

-- debconf information:
  sysstat/enable: false
  sysstat/remove_files: true



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to