Failed to upgrade index

[foobacca]

I just had another play with my test heliotrope setup following a git pull:

$ ruby1.9.1 -I lib bin/heliotrope-server  -d ~/.heliotrope/ -H 1.2.3.4
Version mismatch error: index is version nil but I am expecting "0.1".
Try running bin/heliotrope-upgrade-index.

$ ruby1.9.1 -I lib bin/heliotrope-upgrade-index -d ~/.heliotrope
"upgrade__to_0_1"
Trying to upgrade from nil to "0.1".
Sorry! To upgrade to index version 0.1, you must reindex everything.

$ ruby1.9.1 -I lib bin/heliotrope-reindex -d ~/.heliotrope
Reindexing...
bin/heliotrope-reindex:128:in `add_entry': entry must be a Whistlepig::Entry object (TypeError)
        from bin/heliotrope-reindex:128:in `block in 
'
        from bin/heliotrope-reindex:63:in `each_message_regular'
        from bin/heliotrope-reindex:48:in `each_message'
        from bin/heliotrope-reindex:126:in `
'

I am caught in a catch 22? Should I checkout an earlier version of heliotrope and do the reindexing at that point? Or is upgrading the index not really supported at this point?

[wmorgan]

Excerpts from Hamish Downer's message of 2011-12-31 08:52:08 -0800:

Sorry! To upgrade to index version 0.1, you must reindex everything.

Unfortunately what this means is not "run heliotrope-reindex", but "scratch your current index and start over with the import process". Sorry! The versioning mechanism is pretty new, and since the index format has changed a bit through various commits, there's not a lot I

can do to automatically upgrade from indexes without version markers.

William wmorgan@masanjin.net

[foobacca]

Ah well, it was just a copy of my gmail I was playing with, no data loss I care about.

[wmorgan]

Excerpts from Hamish Downer's message of 2012-01-01 14:38:22 -0800:

Ah well, it was just a copy of my gmail I was playing with, no data loss I care about.

Ok good. In the future, index versioning should work.

William w@masanjin.net