** Changed in: spambayes (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/30720
Title:
sb_filter.py does not lock the database file resulting
** Bug watch added: Debian Bug tracker #296322
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296322
** Also affects: spambayes (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296322
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: spambayes (Debian)
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/30720
Title:
sb_filter.py does not lock the database file resulting in
lowering severity due to extant workaround
(https://bugs.launchpad.net/ubuntu/+source/spambayes/+bug/30720/comments/3)
** Changed in: spambayes (Ubuntu)
Importance: Medium = Low
Status: New = Confirmed
--
sb_filter.py does not lock the database file resulting in corruption
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
sb_filter.py
(I am an occasional spambayes developer)
This behaviour is by design. future versions are likely to offer other
storage options which do not have this problem (possibly based on zodb).
Short-term solutions include:
a. Configure procmail to use a lock file, and use a wrapper script
around
