You are not logged in.
Hello, I need help. Today my sup failed, and it relies heavily on ruby, and among other things on ruby-ncurses.
This is a gem that is installed by the ruby-ncurses package from our (it used to be available from community I think but it disappeared somehow). Anyway, when installing the package from aur it goes well, but then later sup complains that it can't find the gem.
When I do gem list, there's no ncurses there (although there are other gems).
I even tried removing the aur package (with -Rd because sup depends on it) and do "sudo gem install ncurses" but it fails to compile and I know next to nothing about ruby to debug the problem.
Don't really know what to do, except that I'm without my email at work and it's going to end badly for me if I don't fix it soon
Can you help?
Thanks!
Offline
Okay, I didn't solve this but I worked around it - just updated sup, which was relying on ruby-ncurses. The new build relies on ruby-ncursesw and voila, there's no problem anymore. But for people relying on ruby-ncurses there still may be a problem...
Offline
I am having a similar issue. What exactly was it that you did to resolve this problem?
Offline
What I did:
1. yaourt -S sup
(this pulled the new sup package from aur, and that new package depends on ruby-ncursesw, so naturally that package was built as a dependency by yaourt automatically).
2. (this step may be optional, I haven't checked it so your mileage may vary) - I downgraded ruby from 1.9.2 (a recent update, so I was suspicious) to 1.9.1 version which I still had laying around in /var/cache/pacman/pkg
And that's it, sup works!
Offline
Well turns out ruby-ncursesw is incompatible with ruby 1.9.2 as I suspected, so I was right in downgrading ruby.
The only thing worrying now is if ruby-ncursesw gem is supported by somebody at all and somebody may fix it to be compatible with the new ruby. Otherwise we, sup users (and other people using ruby-ncursesw) will be stuck on 1.9.1 ruby forever
Offline
Is there any update on this issue yet? I just ran into the same problem.
Offline
AFAIK, the ruby 1.9.2 Arch package is broken somehow. You can't require 'rubygems' and you can't require any gems at all (IIRC)
Anyway, I just use 1.9.1 for now...
This silver ladybug at line 28...
Offline
Anyway, I just use 1.9.1 for now...
Ok, I'm going to try this.
Offline
@lolilolicon - Rubygems are now built into Ruby 1.9.2, meaning you no longer need to "require 'rubygems'" in your code.
If you're getting a Rubygems error I've posted a possible solution here https://bbs.archlinux.org/viewtopic.php?id=104198
However I don't think ruby-ncursesw is 1.9.2-compatible yet.
Offline