sup talk - Aug 2009 - Nobody told me

Playing the dumb newbie here, but when did that happened?

./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

-- 
Guillaume

Reformatted excerpts from Guillaume Quintard''s message of
2009-08-27:
> Playing the dumb newbie here, but when did that happened?
If anyone else has this problem (and anyone who''s running next with the
Xapian index will): after the dump and before sup-sync, I believe you
need to remove your ~/.sup/xapian directory and ~/.sup/*.db. Life on the
bleeding edge!
> ./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
> 
-- 
William <wmorgan-sup at masanjin.net>

On Fri, Aug 28, 2009 at 10:37 PM, William
Morgan<wmorgan-sup at masanjin.net> wrote:

arg, when I try to restore, I get this:
./lib/sup/crypto.rb:157:in ``'': Cannot allocate memory - /usr/bin/gpg
--quiet --batch --no-verbose --logger-fd 1 --use-agent --verify
/tmp/31666-0-redwood.signature /tmp/31666-0-redwood.payload 2>
/dev/null (Errno::ENOMEM)
	from ./lib/sup/crypto.rb:157:in `run_gpg''
	from ./lib/sup/crypto.rb:92:in `verify''
	from ./lib/sup/util.rb:520:in `send''
	from ./lib/sup/util.rb:520:in `method_missing''
	from ./lib/sup/message.rb:385:in `multipart_signed_to_chunks''
	from ./lib/sup/message.rb:421:in `message_to_chunks''
	from ./lib/sup/message.rb:236:in `load_from_source!''
	from ./lib/sup/message.rb:332:in `build_from_source''
	from ./lib/sup/poll.rb:153:in `each_message_from''
	from ./lib/sup/source.rb:104:in `each''
	from ./lib/sup/util.rb:560:in `send''
	from ./lib/sup/util.rb:560:in `__pass''
	from ./lib/sup/util.rb:547:in `method_missing''
	from ./lib/sup/poll.rb:147:in `each_message_from''
	from ./lib/sup/util.rb:520:in `send''
	from ./lib/sup/util.rb:520:in `method_missing''
	from bin/sup-sync:146
	from bin/sup-sync:141:in `each''
	from bin/sup-sync:141

is it leaking, or is my huge mbox just too big for it?

cheers

-- 
Guillaume

Reformatted excerpts from Guillaume Quintard''s message of
2009-08-28:
> arg, when I try to restore, I get this:
> ./lib/sup/crypto.rb:157:in ``'': Cannot allocate memory -
/usr/bin/gpg --quiet --batch --no-verbose --logger-fd 1 --use-agent --verify
/tmp/31666-0-redwood.signature /tmp/31666-0-redwood.payload 2> /dev/null
(Errno::ENOMEM)
If anyone else has been having memory usage problems on the next branch
recently (probably when sup-syncing a large mbox file), they should be
fixed now. I''ve unmerged the after-add hook, which was the culprit.
-- 
William <wmorgan-sup at masanjin.net>