Your message dated Wed, 9 Jul 2008 19:57:24 +0100
with message-id <[EMAIL PROTECTED]>
and subject line avscan has been removed from Debian, closing #356801
has caused the Debian Bug report #356801,
regarding avscan: "Last Scanned: less than a second ago" -- true for one
second, false thereafter.
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.)
--
356801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356801
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: avscan
Version: 0.8.2-openssl-2
Severity: minor
I put an entry in the Scan List, and do a scan. When the scan is done
it says under the "Last Scanned" header:
less than a second ago
...which is true at first, but then a second passes and it's made false
by age. It doesn't seem to automatically update to "less than a
minute ago" or whatever.
Worse, if there's more than one item in the Scan List, and a few minutes
pass after running the first scan item... and the other item is run and
finishes, the "Last Scanned" header then displays two:
less than a second ago
less than a second ago
...which makes it seem like both items were run at about the same time,
even though they weren't. If 'avscan' is closed and restarted, the
"Last Scanned" header presents somewhat more correctly:
5 minutes ago
11 minutes ago
Alas, these don't update themselves either -- if 'avscan' were left
sitting for days they'd probably remain the same.
Given the present state of the code, it might be better to put more
traditional absolute time values under the "Last Scanned" header; at
least until the current relative "X units ago" values can automatically
update themselves.
Please don't get me wrong -- I like plain English prompts as much as
most users, they're a good thing, but the prompts ought to be perfect or
they make a program look bad.
Hope this helps...
(BTW: Kudos for all the many speedy fixes so far!)
-- 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.15-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Versions of packages avscan depends on:
ii clamav-freshc 0.88-4 downloads clamav virus databases f
ii libbz2-1.0 1.0.3-2 high-quality block-sorting file co
ii libc6 2.3.6-3 GNU C Library: Shared libraries an
ii libclamav1 0.88-4 virus scanner library
ii libcomerr2 1.38+1.39-WIP-2005.12.31-1 common error description library
ii libcurl3 7.15.2-3 Multi-protocol file transfer libra
ii libendeavour2 2.5.7-2 file and disk management suite - l
ii libgcc1 1:4.0.2-10 GCC support library
ii libglib1.2 1.2.10-10.1 The GLib library of C routines
ii libgmp3c2 4.1.4-11 Multiprecision arithmetic library
ii libgtk1.2 1.2.10-18 The GIMP Toolkit set of widgets fo
ii libidn11 0.5.18-2 GNU libidn library, implementation
ii libkrb53 1.4.3-6 MIT Kerberos runtime libraries
ii libssl0.9.8 0.9.8a-7 SSL shared libraries
ii libstdc++6 4.0.2-10 The GNU Standard C++ Library v3
ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li
ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte
ii libxi6 6.9.0.dfsg.1-4 X Window System Input extension li
ii zlib1g 1:1.2.3-11 compression library - runtime
avscan recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.2.2-openssl-3+rm
The avscan package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/470688 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
http://Marco.Tondela.org
--- End Message ---
