On Tue, Jan 17, 2006 at 11:26:51PM +0100, Stefan Wiens wrote:
I have reported this problem on Tue, 16 Nov 2004, bug ID #281656.
When reporting these bugs please send them to the Security Team, not to the
maintainer. Actually, the bug is not even tagged 'security'. Please see
* Martin Schulze:
For the stable distribution (sarge) these problems have been fixed in
version 0.35-2sarge1.
I would have expected a version like 0.35-1sarge1. The version you
have chosen violated an implicit constraint fulfilled by most (all?)
security updates: the version of a package
On Tue, Jan 17, 2006 at 07:59:45PM +0100, Florian Weimer wrote:
* Martin Schulze:
For the stable distribution (sarge) these problems have been fixed in
version 0.35-2sarge1.
I would have expected a version like 0.35-1sarge1. The version you
have chosen violated an implicit constraint
On Tue, Jan 17, 2006 at 07:59:45PM +0100, Florian Weimer wrote:
AFAICS, this rule is quite reasonable, so I assume that this antiword
version is just a minor glitch. Correct?
Yes. My fault entirely. It actually took me a while to see what
was wrong there - usually I just add 'sargeN' to
* Martin Schulze wrote:
--
Debian Security Advisory DSA 945-1 [EMAIL PROTECTED]
http://www.debian.org/security/ Martin Schulze
January 17th, 2006
5 matches
Mail list logo