Your message dated Fri, 21 Apr 2006 08:15:47 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362971: apt-listchanges: debconf should ask for
confirmation, too
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: apt-listchanges
Version: 2.59-0.2
Severity: minor
it's from the descriptions of the options not clear whether apt stops
and waits for confirmation -- and after looking into the manpage and the
created config it does not.
so imo adding a question for confirmation in debconf or alternatively setting in
the [apt] section of the generated file confirm=1 is meaningful.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages apt-listchanges depends on:
ii apt 0.6.43.3 Advanced front-end for dpkg
ii debconf 1.4.72 Debian configuration management sy
ii debianutils 2.15.5 Miscellaneous utilities specific t
ii python 2.3.5-5 An interactive high-level object-o
ii python-apt 0.6.16.2 Python interface to libapt-pkg
ii ucf 2.008 Update Configuration File: preserv
apt-listchanges recommends no packages.
-- debconf information:
apt-listchanges/confirm: false
apt-listchanges/email-address: root
apt-listchanges/which: news
* apt-listchanges/frontend: pager
apt-listchanges/save-seen: true
--- End Message ---
--- Begin Message ---
On Sun, Apr 16, 2006 at 10:48:23PM +0200, Arne Anka wrote:
> Package: apt-listchanges
> Version: 2.59-0.2
> Severity: minor
>
> it's from the descriptions of the options not clear whether apt stops
> and waits for confirmation -- and after looking into the manpage and the
> created config it does not.
> so imo adding a question for confirmation in debconf or alternatively setting
> in
> the [apt] section of the generated file confirm=1 is meaningful.
I'm not entirely sure that I understand you correctly, but if you are
suggesting that there be a debconf question for enabling the confirmation
feature, there already is one.
--
- mdz
--- End Message ---
