From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.66.147 with SMTP id n19cs176864bki; Fri, 3 Sep 2010 10:58:02 -0700 (PDT) Received: by 10.90.90.5 with SMTP id n5mr229097agb.153.1283536675728; Fri, 03 Sep 2010 10:57:55 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id n9si4744681ibn.93.2010.09.03.10.57.54; Fri, 03 Sep 2010 10:57:54 -0700 (PDT) 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; DomainKey-Status: bad (test mode) 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; domainkeys=hardfail (test mode) header.From=hollunder@lavabit.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id D3F7F19783D2; Fri, 3 Sep 2010 13:57:53 -0400 (EDT) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by rubyforge.org (Postfix) with ESMTP id 046721858372 for ; Fri, 3 Sep 2010 13:57:38 -0400 (EDT) Received: from d.earth.lavabit.com (d.earth.lavabit.com [192.168.111.13]) by karen.lavabit.com (Postfix) with ESMTP id 5D45D11B966 for ; Fri, 3 Sep 2010 12:57:38 -0500 (CDT) Received: from lavabit.com (40-72.249.41.lavabit.com [72.249.41.40]) by lavabit.com with ESMTP id HUJQLWEE8OMZ for ; Fri, 03 Sep 2010 12:57:38 -0500 Received: from 143.205.216.185 (SquirrelMail authenticated user hollunder@lavabit.com) by lavabit.com with HTTP; Fri, 3 Sep 2010 13:57:38 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lavabit; d=lavabit.com; b=bWga3pPFx3mn9HBGDAA6s+zXwEXJZShuJff0LXZjd1UDwXHQDmgJr2O2P7Wxc9WngXgWOkjSBF356TXUFN0R8AYGVAzP7/GyqUKOjWfE6Oo+x3/ZkMgTi4Ybw1vURBh7fNmgA284Vj2ZVAv8dri5SB5lHZdC0/WyXsJdFHlWe2o=; h=Message-ID:In-Reply-To:References:Date:Subject:From:To:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; Message-ID: <1438.143.205.216.185.1283536658.squirrel@lavabit.com> In-Reply-To: <1283520512-sup-6361@pk-desktop> References: <747172.93895.qm@web63905.mail.re1.yahoo.com> <1283520512-sup-6361@pk-desktop> Date: Fri, 3 Sep 2010 13:57:38 -0400 (EDT) From: hollunder@lavabit.com To: "sup-talk" User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Subject: Re: [sup-talk] Arch Linux sup now failing. 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 Daren Lord's message of 2010-09-03 15:13:40 +0200: >> There must have been an arch package update that is now causing my sup >> mail to >> fail with this error. >> >> /usr/lib/ruby/1.9.1/rubygems.rb:762:in `report_activate_error': Could >> not find >> RubyGem ncurses (>= 0) (Gem::LoadError) >> from /usr/lib/ruby/1.9.1/rubygems.rb:219:in `activate' >> from /usr/lib/ruby/1.9.1/rubygems.rb:254:in `block in activate' >> from /usr/lib/ruby/1.9.1/rubygems.rb:253:in `each' >> from /usr/lib/ruby/1.9.1/rubygems.rb:253:in `activate' >> from /usr/lib/ruby/1.9.1/rubygems.rb:1065:in `gem' >> from /usr/bin/sup:18:in `
' >> >> I have both ncurses and ncursesw installed through the aur branch. >> >> Any ideas? Use this at work so I am down right now. >> >> aur/ruby-ncurses 1.2.4-1 [installed] (17) >> This ruby extension makes most functions, constants, and external >> variables >> of the C library ncurses accessible >> >> from the Ruby programming language. >> aur/ruby-ncursesw 1.2.4.1-2 [installed] (17) >> Ruby wrapper for ncurses providing wide character support. >> >> Thanks, >> >> dalord >> > > Hi, I just had the same thing this morning. I reinstalled sup from aur > (there's been a new package version, upgraded me from 0.11-1 to 0.11-2) > and just in case backed ruby (upgraded recently to 1.9.2) to 1.9.1. I'm > not sure the latter was necessary but I'm up and running again. I'm > using this at work too so I have no time to experiment with upgrading > ruby, but I'll try when I get a chance (especially if somebody here can > confirm sup works with ruby 1.9.2 on their box). > > The new package release -2 depends on ruby-ncursesw instead of > ruby-ncurses the -1 depended on - this might have something to do with > the whole error (but it's just a guess). > > Try respawning sup from aur and if this doesn't help, downgrade ruby to > 1.9.1. > > Good luck! > Piotr The situation looks grim. I don't seem to have the 1.9.1 package anymore due to a recent cache cleaning. Read all the things I tried: http://aur.archlinux.org/packages.php?ID=26439 How can a stupid minor version change break things so badly? And no one knows what's wrong or how to solve this mess? I'm kinda pissed. Maybe we can get sup into community, so it's kinda supported and might get some testing that would catch this kind of breakage before it hits users. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk