From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs159578ebc; Tue, 26 Jan 2010 05:00:36 -0800 (PST) Received: by 10.101.136.27 with SMTP id o27mr9821963ann.93.1264510834972; Tue, 26 Jan 2010 05:00:34 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 2si13432835gxk.67.2010.01.26.05.00.34; Tue, 26 Jan 2010 05:00:34 -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 2E23F167832C; Tue, 26 Jan 2010 08:00:34 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id C3ADC1678310 for ; Tue, 26 Jan 2010 08:00:03 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1NZl1W-0000VC-QF for sup-talk@rubyforge.org; Tue, 26 Jan 2010 08:00:02 -0500 From: William Morgan To: sup-talk In-reply-to: <1264456502-sup-2092@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> <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> Date: Tue, 26 Jan 2010 08:00:02 -0500 Message-Id: <1264510235-sup-2915@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-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? 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. > 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. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk