From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs401031ebc; Mon, 18 Jan 2010 14:07:31 -0800 (PST) Received: by 10.224.40.130 with SMTP id k2mr4760405qae.69.1263852450887; Mon, 18 Jan 2010 14:07:30 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 8si3342035qwj.13.2010.01.18.14.07.30; Mon, 18 Jan 2010 14:07:30 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 526623C805C; Mon, 18 Jan 2010 17:07:30 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 893483C8052 for ; Mon, 18 Jan 2010 17:05:11 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1NWzig-0003UP-Pi for sup-talk@rubyforge.org; Mon, 18 Jan 2010 17:05:11 -0500 From: William Morgan To: sup-talk In-reply-to: <1263843740-sup-4441@sgoldmanlinux.tower-research.com> References: <1263757714-sup-394@sgoldmanlinux.tower-research.com> <1263760574-sup-1333@masanjin.net> <1263763237-sup-3701@sgoldmanlinux.tower-research.com> <1263764041-sup-9982@masanjin.net> <1263771478-sup-431@sgoldmanlinux.tower-research.com> <1263772988-sup-2344@masanjin.net> <1263774467-sup-9664@sgoldmanlinux.tower-research.com> <1263778916-sup-8839@sgoldmanlinux.tower-research.com> <1263779746-sup-4232@zyrg.net> <1263843740-sup-4441@sgoldmanlinux.tower-research.com> Date: Mon, 18 Jan 2010 17:05:10 -0500 Message-Id: <1263851352-sup-6223@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] Problems running sup-convert-ferret-index X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Reformatted excerpts from Steve Goldman's message of 2010-01-18: > This feels like a wild goose chase. To be fair, all we know from you at this point is you got a segfault. We don't even know what Ruby version, what xapian gem, etc. > Can I start a xapian index from scratch? If you rename your ~/.sup/ferret directory, any future Sup activity (e.g. bin/sup or sup-sync) should take place on a fresh new Xapian index. All of your current messages and message state will be forgotten. > Any downside to this besides the time sink? If you ever use sup-sync --all, it will rescan the soucess to pick up those early messages and presumably incur the same problem. You'll have to make fresh sources to really avoid that. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk