From: marco-oweber@gmx.de (Marc Weber)
Subject: [sup-talk] Trouble loading dump into Xapian index
Date: Fri, 04 Sep 2009 18:25:39 +0200 [thread overview]
Message-ID: <1252081334-sup-213@nixos> (raw)
In-Reply-To: <1252002797-sup-6522@zyrg.net>
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
prev parent reply other threads:[~2009-09-04 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 14:24 Marc Weber
2009-09-03 15:25 ` William Morgan
2009-09-03 16:21 ` Marc Weber
2009-09-03 16:42 ` Rich Lane
2009-09-03 17:16 ` William Morgan
2009-09-04 17:00 ` Rich Lane
2009-09-04 17:29 ` William Morgan
2009-09-03 17:26 ` Marc Weber
2009-09-03 18:35 ` Rich Lane
2009-09-04 16:25 ` Marc Weber [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1252081334-sup-213@nixos \
--to=marco-oweber@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox