Package: debsecan
Version: 0.4.17
Severity: normal
Hi,
the nightly e-mail report lists both "new security updates" and
"available security updates" for linux-image-3.16.0-4-amd64, with
multiple issues each. However, aptitude insists everything is current.
At first I thought, something's just temporarily out of sync, but it's
been doing it for days now, so maybe something is amiss.
Cheers,
Christian
chris@crabtree:~$ LANG=C apt-cache policy linux-image-3.16.0-4-amd64
linux-image-3.16.0-4-amd64:
Installed: 3.16.7-ckt25-2
Candidate: 3.16.7-ckt25-2
Version table:
*** 3.16.7-ckt25-2 0
500 http://ftp.at.debian.org/debian/ jessie-updates/main amd64 Packages
100 /var/lib/dpkg/status
3.16.7-ckt25-1 0
500 http://ftp.at.debian.org/debian/ jessie/main amd64 Packages
3.16.7-ckt20-1+deb8u4 0
500 http://security.debian.org/ jessie/updates/main amd64 Packages
chris@crabtree:~$ uname -a
Linux crabtree 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64
GNU/Linux
-- System Information:
Debian Release: 8.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debsecan depends on:
ii debconf [debconf-2.0] 1.5.56
ii python 2.7.9-1
ii python-apt 0.9.3.12
Versions of packages debsecan recommends:
ii cron 3.0pl1-127+deb8u1
ii nullmailer [mail-transport-agent] 1:1.13-1
debsecan suggests no packages.
-- debconf information:
* debsecan/source:
* debsecan/report: true
* debsecan/suite: jessie
* debsecan/mailto: root