Package: apt-listchanges Version: 2.85.13 Severity: normal Assume I have a package foo (= 1.6) which has had a NEWS entry for version 1.2 only. Now I upload foo (= 1.7) with a NEWS entry for version 1.5 (backdated NEWS entry, I know of two recent occurrences). Because the user had installed 1.6 prior to upgrading to 1.7, the 1.5 NEWS entry is not shown, even though the 1.6 package’s last NEWS entry was for version 1.2 – I thought apt-listchanges kept track of which entries it had already shown?
Backports make this even more complicated… -- System Information: Debian Release: jessie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Versions of packages apt-listchanges depends on: ii apt 1.0.7 ii debconf [debconf-2.0] 1.5.53 ii debianutils 4.4 ii dpkg-dev 1.17.13 ii python 2.7.8-1 ii python-apt 0.9.3.10 ii python-support 1.0.15 ii ucf 3.0030 apt-listchanges recommends no packages. Versions of packages apt-listchanges suggests: ii dillo [www-browser] 3.0.4-1 ii konqueror [www-browser] 4:4.14.0-1 ii konsole [x-terminal-emulator] 4:4.14.0-1 ii links2 [www-browser] 2.8-2 ii lynx-cur [www-browser] 2.8.9dev1-2 ii postfix [mail-transport-agent] 2.11.1-1 ii python-glade2 2.24.0-4 ii python-gtk2 2.24.0-4 ii w3m [www-browser] 0.5.3-17 ii xterm [x-terminal-emulator] 310-1 -- debconf information: apt-listchanges/which: news apt-listchanges/frontend: pager apt-listchanges/email-address: root apt-listchanges/save-seen: true apt-listchanges/confirm: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
