Your message dated Sun, 22 Oct 2006 09:11:11 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#394338: sarge is an invalid debian version?!
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: debsecan
Version: 0.2
Severity: important
[EMAIL PROTECTED]:~$ cat /etc/debian_version
3.1
[EMAIL PROTECTED]:~$ debsecan --suite sarge
Traceback (most recent call last):
File "/usr/bin/debsecan", line 753, in ?
rate_system(target, options, fetch_data(options), history)
File "/usr/bin/debsecan", line 698, in rate_system
pkg_version = Version(contents)
File "/usr/bin/debsecan", line 92, in __init__
self.__parsed = self.__parse(version)
File "/usr/bin/debsecan", line 111, in __parse
raise ValueError, "invalid Debian version string"
ValueError: invalid Debian version string
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2um
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages debsecan depends on:
ii python 2.3.5-2 An interactive high-level object-o
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.4.3
* Joseph Nahmias:
> On Fri, Oct 20, 2006 at 11:30:39PM +0200, Florian Weimer wrote:
>> * Joseph Nahmias:
>>
>> > Package: debsecan
>> > Version: 0.2
>>
>> Can you reproduce this with debsecan 0.4.0 or later, with python-apt
>> installed?
>
> Just downloaded 0.4.3, and it looks like it's working properly.
Thanks, closing the bug.
--- End Message ---
