Bug ID | 952799 |
---|---|
Summary | bogofilter-{db,sqlite3} insists on using wordlist.tc |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | 2015* |
Hardware | x86-64 |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Other |
Assignee | bnc-team-screening@forge.provo.novell.com |
Reporter | gour@atmarama.net |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
In the past, when using other Linux distros I was mostly using bogofilter with sqlite3 back-end, but after switching to openSUSE I've decided to convert to 'default' (Berkeley) DB backend. Unfortunately, after bogofilter package was updated in openSUSE, it looks it does insist on using $HOME/.bogofilter/wordlist.tc for the database name even if one uses Berkeley DB or Sqlite3 back-ends? When I try to use my old wordlist.db, Bogofilter plugin (Claws & Evolution) starts from the scratch and creates wordlist.tc. I wonder about this line in *.spec: %if 0%{?suse_version} > 1320 iow. whether the new Bogofilter package is ready to use existing setup with appropriate back-end (not equal to TokyoCabinet)?