From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs431411ebc; Tue, 19 Jan 2010 05:31:43 -0800 (PST) Received: by 10.224.1.37 with SMTP id 37mr5246906qad.325.1263907902882; Tue, 19 Jan 2010 05:31:42 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 7si8130318qwb.52.2010.01.19.05.31.42; Tue, 19 Jan 2010 05:31:42 -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 2F104177994D; Tue, 19 Jan 2010 08:31:42 -0500 (EST) Received: from ns2.limegroup.com (ns2.limegroup.com [64.20.166.97]) by rubyforge.org (Postfix) with ESMTP id EAAF41858267 for ; Tue, 19 Jan 2010 08:31:23 -0500 (EST) Received: from ns1.limegroup.com (ns1.limegroup.com [10.1.1.5]) by ns2.limegroup.com (8.13.1/8.13.1) with ESMTP id o0JDVNPT019381 for ; Tue, 19 Jan 2010 08:31:23 -0500 Received: from lithium-a.limegroup.com (lithium-a.limegroup.com [10.1.1.12]) by ns1.limegroup.com (8.13.1/8.13.1) with ESMTP id o0JDVNZf004606 for ; Tue, 19 Jan 2010 08:31:23 -0500 Received: from sgoldmanlinux.tower-research.com (sgoldmanlinux.tower-research.com [10.0.25.84]) by lithium-a.limegroup.com (8.13.1/8.13.1) with ESMTP id o0JDVNEf013067 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 19 Jan 2010 08:31:23 -0500 Received: from sgoldmanlinux.tower-research.com (localhost.localdomain [127.0.0.1]) by sgoldmanlinux.tower-research.com (8.14.3/8.14.3) with ESMTP id o0JDVNIR010293 for ; Tue, 19 Jan 2010 08:31:23 -0500 Received: (from sgoldman@localhost) by sgoldmanlinux.tower-research.com (8.14.3/8.14.3/Submit) id o0JDVNB1010292; Tue, 19 Jan 2010 08:31:23 -0500 From: Steve Goldman To: sup-talk In-reply-to: <1263851352-sup-6223@masanjin.net> 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> <1263851352-sup-6223@masanjin.net> Date: Tue, 19 Jan 2010 08:31:23 -0500 Message-Id: <1263907792-sup-3649@sgoldmanlinux.tower-research.com> User-Agent: Sup/git MIME-Version: 1.0 Content-Disposition: inline X-Scanned-By: MIMEDefang 2.67 on 10.1.1.6 X-Scanned-By: MIMEDefang 2.67 on 10.1.1.4 X-Scanned-By: MIMEDefang 2.67 on 10.1.1.10 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from William Morgan's message of Mon Jan 18 17:05:10 -0500 2010: > 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. Right. I'd rather start fresh than try to debug this, personally. > > 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. What are fresh sources? Thanks. -- Steve Goldman sgoldman@tower-research.com T: 212.219.6014 F: 212.219.6007 Tower Research Capital, LLC 377 Broadway, 11th Fl. New York, NY 10013 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk