From mboxrd@z Thu Jan 1 00:00:00 1970 From: rlane@club.cc.cmu.edu (Rich Lane) Date: Mon, 27 Jul 2009 23:33:16 -0400 Subject: [sup-talk] xapian merged into next In-Reply-To: <1e5fdab70907271304xcc52d55pb745cb85d258fdc4@mail.gmail.com> References: <1248711109-sup-7061@entry> <1e5fdab70907270916o2f8e1768vbe7e3bcc1c807e39@mail.gmail.com> <1248711777-sup-9329@entry> <1e5fdab70907270931t7dfbe285h67197a7355b611d6@mail.gmail.com> <1248712876-sup-1446@entry> <1e5fdab70907271304xcc52d55pb745cb85d258fdc4@mail.gmail.com> Message-ID: <1248751256-sup-4491@pion.club.cc.cmu.edu> Excerpts from Guillaume Quintard's message of Mon Jul 27 16:04:58 -0400 2009: > > 5. ruby -Ilib bin/sup-dump > dumpfile > -> produces a empty file (not sure it's normal) > > ./lib/sup/xapian_index.rb:17:in `at': bignum too big to convert into Oops, breaking sup-dump would make switching to Xapian a little difficult. I've posted patches for both these issues. We really should have more tests to catch this sort of thing...