Excerpts from Michael Stipicevic's message of Fri Oct 01 00:52:18 -0400 2010:
> Did this happen right after you sent a message? I had to fix this by doing a
> dump and rebuilding the index.
Yep. Ouch! Although, I suppose there are worse things in life :-)
Cheers,
Edward
__
>
> So I guess my index is corrupted in some weird way (probably I managed
> to create two mails with the same docid). I've worked around it by
> commenting
> out the assert, but any idea how to fix my index?
>
Did this happen right after you sent a message? I had to fix this by doing a
dump and r
Reformatted excerpts from Israel Herraiz's message of 2010-01-25:
> I am using the next branch of Sup, and since a couple of commits ago,
> whenever I try to compose a message (new, forward, etc), I obtain this
> exception:
This should be fixed!
--
William
___
It seems that someone (not me :-) opened an issue about this some
minutes before my message:
http://masanjin.net/sup-bugs/issue49
Cheers,
Israel
___
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
