From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs216828ebc; Tue, 26 Jan 2010 19:24:42 -0800 (PST) Received: by 10.90.188.5 with SMTP id l5mr179679agf.73.1264562681071; Tue, 26 Jan 2010 19:24:41 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 24si14736110gxk.21.2010.01.26.19.24.40; Tue, 26 Jan 2010 19:24:40 -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 626A21858302; Tue, 26 Jan 2010 22:24:40 -0500 (EST) Received: from ns2.limegroup.com (ns2.limegroup.com [64.20.166.97]) by rubyforge.org (Postfix) with ESMTP id 7CB0218582D0 for ; Tue, 26 Jan 2010 22:24:35 -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 o0R3OZpC006324 for ; Tue, 26 Jan 2010 22:24:35 -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 o0R3OYrT013703 for ; Tue, 26 Jan 2010 22:24:34 -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 o0R3OYAU016214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 26 Jan 2010 22:24:34 -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 o0R3OYJA026713 for ; Tue, 26 Jan 2010 22:24:34 -0500 Received: (from sgoldman@localhost) by sgoldmanlinux.tower-research.com (8.14.3/8.14.3/Submit) id o0R3OYRV026711; Tue, 26 Jan 2010 22:24:34 -0500 From: Steve Goldman To: sup-talk In-reply-to: <1264510235-sup-2915@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> <1263907792-sup-3649@sgoldmanlinux.tower-research.com> <1263908176-sup-851@masanjin.net> <1264437234-sup-8884@sgoldmanlinux.tower-research.com> <1264454942-sup-8589@masanjin.net> <1264456502-sup-2092@sgoldmanlinux.tower-research.com> <1264510235-sup-2915@masanjin.net> Date: Tue, 26 Jan 2010 22:24:34 -0500 Message-Id: <1264562538-sup-9933@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 Tue Jan 26 08:00:02 -0500 2010: > Reformatted excerpts from Steve Goldman's message of 2010-01-25: > > Presumably. I run it through sup-config, which outputs "Rats, that > > didn't work" when the return code is non-zero. But sup-sync outputs > > nothing. > > And just to confirm, when you run that sup-sync command by itself, > outside of sup-config, it just dies without a backtrace, right? Correct. > Since this didn't happen with Ferret, my best guess is that the problem > lies somewhere in the bowels of Xapian or the bindings thereof: > > > xapian-bindings-ruby-1.0.17-2.fc11.x86_64 > > I would try and get the latest xapian-full gem. I have no experience > with the bindings Fedora distributes, but I know that that gem works for > me and for others. > > It's possible to install and run gems entirely out of your home > directory (at least in recent versions), so it should be possible to do > this without involving your sysadmin, if that's easier. > > Something like: > > gem install gemcutter > gem install xapian-full > > Ought to magically work, if your gems are new enough. Do I need to do something to make ruby use this xapian and not the Fedora xapian? How can I tell which it is using? > > He says the Fedora release will likely get there soon, but we could > > try to get it in advance if you think this will help. > > Let's wait on playing with Ruby versions until we have your Xapian > bindings locked down. I did some sleuthing and found that it hangs on the loop over all the messages in my first source (imap) after it gets through exactly seven of them. Specifically, it hangs at the top of the loop: Redwood::PollManager.each_message_from source do |m| Any ideas? 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