Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: hollunder@lavabit.com
To: "sup-talk" <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Arch Linux sup now failing.
Date: Fri, 3 Sep 2010 13:57:38 -0400 (EDT)	[thread overview]
Message-ID: <1438.143.205.216.185.1283536658.squirrel@lavabit.com> (raw)
In-Reply-To: <1283520512-sup-6361@pk-desktop>

> 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 `<main>'
>>
>> 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


  reply	other threads:[~2010-09-03 17:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 13:13 Daren Lord
2010-09-03 13:33 ` Piotr Kempa
2010-09-03 17:57   ` hollunder [this message]
2010-09-03 18:13     ` Gaute Hope
2010-09-03 18:25       ` Gaute Hope
2010-09-03 23:01     ` carmen
2010-09-04  9:05       ` Philipp Überbacher
2010-09-03 15:26 ` Arian Kuschki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1438.143.205.216.185.1283536658.squirrel@lavabit.com \
    --to=hollunder@lavabit.com \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox