Package: apt-listchanges
Version: 2.70
Severity: normal

        Hi,

 I dpkg-reconfigure packages when I need to reconfigure them, but with
 apt-listchanges this seems to be a no-op.

 When I dpkg-reconfigure apt-listchanges, it will correctly display the
 settings I have configured in the past (from debconf's cache), but I
 end up with my settings in /etc/apt/listchanges.conf.ucf-dist, and
 /etc/apt/listchanges.conf holds the default settings:
bee% diff /etc/apt/listchanges.conf /etc/apt/listchanges.conf.ucf-dist 
--- /etc/apt/listchanges.conf   2006-10-15 17:07:17.000000000 +0200
+++ /etc/apt/listchanges.conf.ucf-dist  2006-10-15 17:18:00.000000000 +0200
@@ -1,6 +1,6 @@
 [apt]
 frontend=pager
-email_address=root
-confirm=0
+email_address=
+confirm=1
 save_seen=/var/lib/apt/listchanges.db
-which=news
+which=both

 I added a "set -x" and "exec 2>/dev/tty" to the apt-listchanges
 postinst, and saw:
+ '[' true = true ']'
+ echo save_seen=/var/lib/apt/listchanges.db
+ db_get apt-listchanges/which
+ _db_cmd 'GET apt-listchanges/which'
+ IFS=' '
+ printf '%s\n' 'GET apt-listchanges/which'
+ IFS='
'
+ read -r _db_internal_line
+ RET=both
+ case ${_db_internal_line%%[   ]*} in
+ return 0
+ echo which=both
+ '[' -f /etc/apt/listchanges.conf ']'
+ ucf --debconf-ok /etc/apt/listchanges.conf.new /etc/apt/listchanges.conf
+ rm -f /etc/apt/listchanges.conf.new
+ '[' configure = configure ']'
+ which update-python-modules
+ update-python-modules -b apt-listchanges.dirs
+ exit 0

 I then removed the "rm -f" to have a chance to review the .new file,
 and it holds the correct settings:
# cat /etc/apt/listchanges.conf.new 
[apt]
frontend=pager
email_address=
confirm=1
save_seen=/var/lib/apt/listchanges.db
which=both

 I then called ucf manually:
# ucf -v /etc/apt/listchanges.conf.new /etc/apt/listchanges.conf
ucf: The new file is /etc/apt/listchanges.conf.new
ucf: The Destination file is /etc/apt/listchanges.conf
ucf: The Source directory is /etc/apt
ucf: The State directory is /var/lib/ucf
The hash file exists
egrep [[:space:]]\/etc\/apt\/listchanges\.conf$ /var/lib/ucf/hashfile
aec10b96e7940298caefd9232d3644cf  /etc/apt/listchanges.conf
md5sums match, nothing needs be done.

 And the config file is unchanged in the end.

 I think you shouldn't call ucf when one wants to reconfigure a package,
 but only on upgrades; I suspect this is the cause of #393470 as well,
 at least I wouldn't get #393470 if you didn't call ucf during
 dpkg-reconfigure.

 I would have liked to provide you with a full reproducing scenario for
 either #393470 or this bug, but unfortunately, I can't dpkg-reconfigure
 apt-listchanges at all in my pbuilder, despite forcing the debconf
 frontend.  I suppose you should be able to reproduce the bug I'm
 reporting more easily than #393470 though, as #393470 probably only
 happens during the first installation.

   Bye,

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages apt-listchanges depends on:
ii  apt                           0.6.46.2   Advanced front-end for dpkg
ii  debconf [debconf-2.0]         1.5.6      Debian configuration management sy
ii  debianutils                   2.17.3     Miscellaneous utilities specific t
ii  python                        2.4.3-11   An interactive high-level object-o
ii  python-apt                    0.6.19     Python interface to libapt-pkg
ii  python-support                0.5.4      automated rebuilding support for p
ii  ucf                           2.0015     Update Configuration File: preserv

Versions of packages apt-listchanges recommends:
ii  postfix [mail-transport-agent 2.3.3-3    A high-performance mail transport 

-- debconf information:
* apt-listchanges/confirm: true
* apt-listchanges/which: both
* apt-listchanges/frontend: pager
* apt-listchanges/email-address:
* apt-listchanges/save-seen: true

-- 
Loïc Minier <[EMAIL PROTECTED]>

Reply via email to