From mboxrd@z Thu Jan  1 00:00:00 1970
From: marco-oweber@gmx.de (Marc Weber)
Date: Thu, 03 Sep 2009 19:26:59 +0200
Subject: [sup-talk] Trouble loading dump into Xapian index
In-Reply-To: <1251995984-sup-7983@zyrg.net>
References: <1251987692-sup-9940@nixos> <1251991420-sup-3869@masanjin.net>
	<1251994802-sup-8575@nixos> <1251995984-sup-7983@zyrg.net>
Message-ID: <1251998504-sup-6794@nixos>


> I added support for thread killing in 4d82ef88, which hasn't been merged
> to master yet. If you'd like to use the Xapian index I suggest using
> next for now.

Hi Rich, using next I get the following error:

+ ruby -Ilib bin/sup-sync --all --all-sources --restore /tmp/dump-file-new
./lib/sup/crypto.rb:17: warning: Insecure world writable dir /pr/webkos
in PATH, mode 040777
Loading state dump from /tmp/dump-file-new...
Read 39048 entries from dump file.
./lib/sup/xapian_index.rb:32:in `load_index': This Sup version expects a
v1 index, but you have an existing v0 index. Please downgrade to your
previous version and dump your labels before upgrading to this version
(then run sup-sync --restore). (RuntimeError)
        from ./lib/sup/index.rb:67:in `load'
        from bin/sup-sync:117

I looked at strace to and noticed that sup only accessed the new
~/.sup-new-test direcotry which was empty. So there is no v0 at all)

Marc Weber