Hi,
I can confirm this (when using the curses UI, see below) and I have some
precisions as well a possible workaround.
First, this is the contents of the configuration file
(/etc/apt/listchanges.conf) on the "testing" box where the problem is
observable :
[apt]
frontend=pager
email_address=root
confirm=1
save_seen=/var/lib/apt/listchanges.db
which=both
The problem described in the original bug report is in my case further
aggravated by the fact that the mail report is not sent.
The box is updated daily. The last time the message was sent was on
February, 23rd. Here is the /var/log/aptitude excerpt for this day :
[CONSERVÉ] octave3.2
[INSTALLÉ] printer-driver-pxljr
[MIS A JOUR] alsa-oss 1.0.17-5 -> 1.0.25-1
[MIS A JOUR] alsa-tools 1.0.24.1-3 -> 1.0.25-1
[MIS A JOUR] alsa-tools-gui 1.0.24.1-3 -> 1.0.25-1
[MIS A JOUR] alsa-utils 1.0.24.2-5 -> 1.0.25-1
[MIS A JOUR] fonts-pecita 3.2-4 -> 3.3-1
[MIS A JOUR] foomatic-db 20111206-1 -> 20120212-1
[MIS A JOUR] foomatic-filters 4.0.9-1 -> 4.0.12-1
[MIS A JOUR] ghostscript 9.04~dfsg-3 -> 9.05~dfsg-2
[MIS A JOUR] ghostscript-cups 9.04~dfsg-3 -> 9.05~dfsg-2
[MIS A JOUR] ghostscript-x 9.04~dfsg-3 -> 9.05~dfsg-2
[MIS A JOUR] libasound2 1.0.24.1-4 -> 1.0.25-2
[MIS A JOUR] libencode-locale-perl 1.02-2 -> 1.03-1
[MIS A JOUR] libev4 1:4.04-1 -> 1:4.11-1
[MIS A JOUR] libgs9 9.04~dfsg-3 -> 9.05~dfsg-2
[MIS A JOUR] libgs9-common 9.04~dfsg-3 -> 9.05~dfsg-2
[MIS A JOUR] libqscintilla2-8 2.6-3 -> 2.6.1-1
[MIS A JOUR] libsqlite3-0 3.7.9-2 -> 3.7.10-1
[MIS A JOUR] libsqlite3-dev 3.7.9-2 -> 3.7.10-1
[MIS A JOUR] login 1:4.1.4.2+svn3283-3 -> 1:4.1.5-1
[MIS A JOUR] manpages-fr-extra 20111118 -> 20120212
[MIS A JOUR] mime-support 3.51-1 -> 3.52-1
[MIS A JOUR] openprinting-ppds 20111206-1 -> 20120212-1
[MIS A JOUR] passwd 1:4.1.4.2+svn3283-3 -> 1:4.1.5-1
[MIS A JOUR] pyqt4-dev-tools 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-blockdiag 1.1.2-1 -> 1.1.2-2
[MIS A JOUR] python-qscintilla2 2.6-3 -> 2.6.1-1
[MIS A JOUR] python-qt4 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-qt4-dbus 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-qt4-dev 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-qt4-doc 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-qt4-gl 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-qt4-sql 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-sip 4.13.1-3 -> 4.13.2-1
[MIS A JOUR] python-sip-dev 4.13.1-3 -> 4.13.2-1
[MIS A JOUR] sakura 2.4.2-3 -> 2.4.2-4
[MIS A JOUR] sqlite3 3.7.9-2 -> 3.7.10-1
[MIS A JOUR] sqlite3-doc 3.7.9-2 -> 3.7.10-1
[MIS A JOUR] xserver-xorg-video-dummy 1:0.3.5-1 -> 1:0.3.5-2
The day after, the message was not sent. Here is what was upgraded on
February, 24th :
[INSTALLÉ, DÉPENDANCES] sphinx-common
[INSTALLÉ, DÉPENDANCES] sphinx-doc
[INSTALLÉ, DÉPENDANCES] xz-lzma
[CONSERVÉ] octave3.2
[MIS A JOUR] ca-certificates 20111211 -> 20120212
[MIS A JOUR] dbus 1.4.16-1 -> 1.4.18-1
[MIS A JOUR] dbus-x11 1.4.16-1 -> 1.4.18-1
[MIS A JOUR] libaacs0 0.3.0-3 -> 0.3.0-4
[MIS A JOUR] libass4 0.10.0-2 -> 0.10.0-3
[MIS A JOUR] libc-client2007e 8:2007e~dfsg-3.2 -> 8:2007e~dfsg-3.3
[MIS A JOUR] libdbus-1-3 1.4.16-1 -> 1.4.18-1
[MIS A JOUR] libdiscid0 0.2.2-2 -> 0.2.2-3
[MIS A JOUR] libevent-2.0-5 2.0.16-stable-1 -> 2.0.17-stable-1
[MIS A JOUR] libgudev-1.0-0 175-3 -> 175-3.1
[MIS A JOUR] libjs-sphinxdoc 1.0.8+dfsg-2 -> 1.1.2+dfsg-5
[MIS A JOUR] librhino-java 1.7R3-4 -> 1.7R3-5
[MIS A JOUR] libtamuanova-0.2 0.2-1 -> 0.2-2
[MIS A JOUR] libudev0 175-3 -> 175-3.1
[MIS A JOUR] libwrap0 7.6.q-22 -> 7.6.q-23
[MIS A JOUR] mercurial 2.0.2-1 -> 2.1-1
[MIS A JOUR] mercurial-common 2.0.2-1 -> 2.1-1
[MIS A JOUR] mlock 8:2007e~dfsg-3.2 -> 8:2007e~dfsg-3.3
[MIS A JOUR] pdf2djvu 0.7.11-1 -> 0.7.12-1
[MIS A JOUR] python-apt 0.8.0 -> 0.8.3+nmu1
[MIS A JOUR] python-apt-common 0.8.0 -> 0.8.3+nmu1
[MIS A JOUR] python-sphinx 1.0.8+dfsg-2 -> 1.1.2+dfsg-5
[MIS A JOUR] python-wimpiggy 0.0.7.31+dfsg-1 -> 0.0.7.36+dfsg-1
[MIS A JOUR] rhino 1.7R3-4 -> 1.7R3-5
[MIS A JOUR] tcpd 7.6.q-22 -> 7.6.q-23
[MIS A JOUR] udev 175-3 -> 175-3.1
[MIS A JOUR] xfce4-session 4.8.2-3 -> 4.8.3-1
[MIS A JOUR] xpra 0.0.7.31+dfsg-1 -> 0.0.7.36+dfsg-1
Please note the upgrade of python-apt 0.8.0 -> 0.8.3+nmu1 . Later, I tried
uninstalling xz-lzma but this did not change anything.
Yet, I find it strange that the problem only exhibited itself _during_ the
upgrade since when the error messages are printed the new packages are not
even unpacked (AFAIK). On the other hand, I don't see any package upgrade on
the day before that could have triggered the problem (not even on this day
activity log).
And now for the workaround : I found out that this problem only occur when
the curses UI of aptitude is launched by a normal user, gaining root
privileges when requesting a database update, packages upgrade, ...
If you first su to root before to run aptitude, then everything goes as
expected. This is why the problem does not show when using the CLI
("aptitude dist-upgrade") invocation.
Hope this helps.
phep
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
