I did try this:
* Remove the Xapian index
* Reindex
* Re-do the search
This did not actually fix the problem.
Therefore this is, as far as I can tell, an issue with upstream Roundup.
If we want to try digging deeper, we should read the Roundup code and see how
they're using Xapian. Maybe there's e.g. some configuration option they set that
is inappropriate.
The other next step is to file a bug with upstream's bug tracker, perhaps with a
copy of our database or instructions on how to reproduce the problem.
It'd be nice if there were a command-line test tool that we could use to test if
searches find things we expect them to. There's the roundup-admin tool, but per
http://roundup.sourceforge.net/doc-1.0/user_guide.html it doesn't seem to have a
search option.
|