Re: [sup-talk] Problems running sup-convert-ferret-index

[William Morgan <wmorgan-sup@masanjin.net>]

Reformatted excerpts from Steve Goldman's message of 2010-01-18:
> This feels like a wild goose chase.

To be fair, all we know from you at this point is you got a segfault.
We don't even know what Ruby version, what xapian gem, etc.

> Can I start a xapian index from scratch?

If you rename your ~/.sup/ferret directory, any future Sup activity
(e.g. bin/sup or sup-sync) should take place on a fresh new Xapian
index. All of your current messages and message state will be forgotten.

> Any downside to this besides the time sink?

If you ever use sup-sync --all, it will rescan the soucess to pick up
those early messages and presumably incur the same problem. You'll have
to make fresh sources to really avoid that.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk