Your message dated Mon, 7 Feb 2011 01:12:01 +0100
with message-id <20110207001201.GR6712@mobee>
and subject line Re: Close Debian bug #226643 bogofilter: bogoupgrade exhausts
all available RAM and swap
has caused the Debian Bug report #226643,
regarding bogoupgrade segfaults at 3GB vm limit
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.)
--
226643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=226643
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bogofilter
Severity: important
The bogoupgrade utility provided with bogofilter (package version
0.15.13-1) to upgrade databases from formats used in earlier versions
uses an amazing amount of memory. So much, in fact, that in the
process of upgrading my 33MB spamlist.db and 38MB goodlist.gb it got
up to 3GB of virtual memory and then segfaulted when it needed more
because that is the limit of how much memory the kernel can fit into a
process's vm on 32-bit machines. Needless to say, my databases have
not been successfully upgraded and I am not amused.
-Nate
P.S. ha ha perl
--
--< ((\))< >----< [email protected] >----< http://www.movealong.org/ >--
pub 1024D/05A058E0 2002-03-07 Nate Riffe (06-Mar-2002) <[email protected]>
Key fingerprint = 0DAC F5CB D182 3165 D757 C466 CD42 12A8 05A0 58E0
--- End Message ---
--- Begin Message ---
On Fri, Jan 15, 2010 at 10:25:15PM +0100, Serafeim Zanikolas wrote [edited]:
> On Fri, Jan 15, 2010 at 10:39:16AM +0100, Matthias Andree wrote [edited]:
> [..]
> > It should be safe to take the bogofilter 1.1.7+ bogoupgrade.in
> > script and use it in the 1.1.3 package if you really want to touch
> > that for a minor issue.
>
> I'll close the bug as soon as 1.1.7 becomes the earliest supported release
> (ie. once squeeze is out).
The time has come for this bug to be closed ;)
Cheers,
Serafeim
--- End Message ---
