From: Hamish D <dmishd@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: [sup-devel] error after leveldb-ruby upgrade
Date: Sun, 17 Jul 2011 18:42:11 +0100 [thread overview]
Message-ID: <CAOxvSbddWV33kzmS0OPCg-jvcKjzwu1JyGFjqL4Puaxiv-a=tQ@mail.gmail.com> (raw)
Hello
I've just done a git pull, and noticed there was a bump in version of
leveldb-ruby, so did a gem update to 0.7.
Then when trying to run heliotrope-add or heliotrope-server, it
immediately dies with:
$ heliotrope-server -d ~/.heliotrope
/var/lib/gems/1.9.1/gems/leveldb-ruby-0.7/lib/leveldb.rb:11:in `make':
Corruption: checksum mismatch (LevelDB::Error)
from /var/lib/gems/1.9.1/gems/leveldb-ruby-0.7/lib/leveldb.rb:11:in `new'
from /home/mish/dev/sup/heliotrope/lib/heliotrope/index.rb:45:in `initialize'
from /home/mish/dev/sup/heliotrope/bin/heliotrope-server:583:in `new'
from /home/mish/dev/sup/heliotrope/bin/heliotrope-server:583:in `<main>'
Any ideas?
Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2011-07-17 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 17:42 Hamish D [this message]
2011-07-17 20:05 ` William Morgan
2011-07-17 22:51 ` Hamish D
2011-07-18 4:21 ` William Morgan
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='CAOxvSbddWV33kzmS0OPCg-jvcKjzwu1JyGFjqL4Puaxiv-a=tQ@mail.gmail.com' \
--to=dmishd@gmail.com \
--cc=sup-devel@rubyforge.org \
/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