Sorry.
It was my fault. I had a ~/.sup/xapian I forgot about. That made the
trouble causing the correct error message.
So I think it's safe to switch to Xapian. You may use this script.
It will copy the existing ~/.sup and create a new directory $NEW with
the xapian index. You cane set SUP_BASE to run the new sup to try it
out. Next feels so much better in various ways (speed, search in threads etc.)
Thanks for your all this work!
set -x
set -e
OLD=~/.sup
NEW=/pr/sup-new-test
DUMP=/tmp/dump-file-new
DUMP2=/tmp/dump-file-new2
SYNC_LOG=/tmp/sup-sync-log
GIT_REPO=~/managed_repos/sup_mainline
rm -fr $NEW
export SUP_BASE=$OLD
sup-dump > $DUMP
# from now on operate on the new base only
export SUP_BASE=$NEW
cp -r $OLD $NEW
rm -fr $NEW/ferret
rm -fr $NEW/xapian # remove old xapian cruft!
mv $NEW/{hooks,hooks-disabled}
# echo loading stuff..
export SUP_INDEX=xapian
cd $GIT_REPO
echo "syncing.. this will take long. use tail -f $SYNC_LOG to watch progress"
ruby -Ilib bin/sup-sync --all --all-sources --restore $DUMP &> $SYNC_LOG
echo "writing dump"
ruby -Ilib bin/sup-dump # > $DUMP2
Marc Weber
_______________________________________________
sup-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/sup-talk
