From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] Trouble loading dump into Xapian index
Date: Thu, 03 Sep 2009 14:35:05 -0400 [thread overview]
Message-ID: <1252002797-sup-6522@zyrg.net> (raw)
In-Reply-To: <1251998504-sup-6794@nixos>
Excerpts from Marc Weber's message of Thu Sep 03 13:26:59 -0400 2009:
>
> > 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)
That's strange, because this codepath (xapian_index.rb:32) is only hit
when the xapian directory already exists. Can you add a log message to
output the "path" variable and see if it looks correct?
next prev parent reply other threads:[~2009-09-03 18:35 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 [this message]
2009-09-04 16:25 ` Marc Weber
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=1252002797-sup-6522@zyrg.net \
--to=rlane@club.cc.cmu.edu \
/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