Your message dated Thu, 3 Jul 2008 12:41:36 -0400
with message-id <[EMAIL PROTECTED]>
and subject line close #461611
has caused the Debian Bug report #461611,
regarding debsecan: should show that libxfont1 issues have been fixed in sid
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
461611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461611
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: debsecan
Version: 0.4.10
Severity: normal
according to DSA-1466 (http://lwn.net/Articles/265755/), the security
issues is libxfont1 were fixed in the 1.3.1-2 packages that are now in
sid. debsecan should show that the issues have now been addressed.
something strange is going on with www.debian.org/security because
DSA-1466 is not showing up in the DSA list at all. maybe this is a
separate issue that the security team needs to be made aware of?
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages debsecan depends on:
ii debconf [debconf-2.0] 1.5.18 Debian configuration management sy
ii python 2.4.4-6 An interactive high-level object-o
ii python-apt 0.7.4+b1 Python interface to libapt-pkg
Versions of packages debsecan recommends:
ii cron 3.0pl1-103 management of regular background p
ii exim4 4.68-2 meta-package to ease Exim MTA (v4)
ii exim4-daemon-light [mail-tran 4.68-2 lightweight Exim MTA (v4) daemon
-- debconf information excluded
--- End Message ---
--- Begin Message ---
this is a problem with the security tracker [1], not debsecan. hence,
closing this bug.
[1] http://lists.debian.org/debian-security-tracker/2008/05/msg00005.html
--- End Message ---
