From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs122630ebc; Mon, 25 Jan 2010 15:37:30 -0800 (PST) Received: by 10.91.55.26 with SMTP id h26mr314212agk.83.1264462649839; Mon, 25 Jan 2010 15:37:29 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 21si12038920gxk.5.2010.01.25.15.37.29; Mon, 25 Jan 2010 15:37:29 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-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-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 067D518582F9; Mon, 25 Jan 2010 18:37:29 -0500 (EST) Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.cmu.edu [128.237.157.88]) by rubyforge.org (Postfix) with ESMTP id E149318582F5 for ; Mon, 25 Jan 2010 18:37:24 -0500 (EST) Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69) (envelope-from ) id 1NZYUm-0000AI-Lh for sup-devel@rubyforge.org; Mon, 25 Jan 2010 18:37:24 -0500 From: Rich Lane To: sup-devel In-reply-to: <1264456949-sup-3@zyrg.net> References: <1264454003-sup-9657@masanjin.net> <1264456949-sup-3@zyrg.net> Date: Mon, 25 Jan 2010 18:37:24 -0500 Message-Id: <1264462577-sup-3137@zyrg.net> User-Agent: Sup/git Subject: Re: [sup-devel] Fwd: Re: Sup 0.10 released X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion 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-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Excerpts from Rich Lane's message of 2010-01-25 17:05:49 -0500: > Excerpts from William Morgan's message of 2010-01-25 16:19:13 -0500: > > I'm seeing a weird behavior with the xapian-full gem, and so is this > > guy. The installation claims it fails, but it actually succeeds. The > > spec file is not copied over after installation, so `gem list` doesn't > > show it, but if you require 'xapian' it actually does pick up the code, > > even after the failed installation. > > > > Ideas? > > This has been reported before but I haven't figured out what's going on. > I pushed the source of the xapian-full gem to git://github.com/rlane/xapian-full > in case anyone else wants to take a crack at this. I think I fixed it. Please try xapian-full 1.1.3.1 from gemcutter. _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel