From: Andrei Thorp <garoth@gmail.com>
To: Rich Lane <rlane@club.cc.cmu.edu>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup 0.12 released
Date: Tue, 25 Jan 2011 11:46:53 -0500 [thread overview]
Message-ID: <AANLkTi=QRBEFuj8EPHchoqDYL=SsAS2ZRt7=a-mM6tem@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik=GqXrK9WOtA7CQrU51Tyeq7AoBQ6rGHB4iepg@mail.gmail.com>
On Tue, Jan 25, 2011 at 11:24 AM, Andrei Thorp <garoth@gmail.com> wrote:
> On Mon, Jan 17, 2011 at 10:36 PM, Rich Lane <rlane@club.cc.cmu.edu> wrote:
>> Excerpts from Philipp Überbacher's message of Mon Jan 17 17:03:23 -0500 2011:
>>> There also seem to be huge problems building and installing sup 0.12,
>>> have a look here to get an idea how much frustration it already caused:
>>> http://aur.archlinux.org/packages.php?ID=26439
>>
>> I use Arch myself so I'm surprised there's been so much trouble
>> packaging for it. Does gettext need to be a gem dependency? I've
>> reconsidered the ncurses mess and master now requires ncursesw. I'm not
>> convinced an Arch package should be using xapian-full - I only made that
>> gem because I wanted the install process to be as simple as "gem install
>> sup". The normal Arch Xapian package should work fine.
>
> Hey there Rich. I'm the package maintainer there and have certainly
> had a never-ending cascade of trouble packaging it. Stuff ranging from
> dire lack of aur packages for the dependencies (which prompted me to
> write a system to automatically create them) to broken dependencies to
> massive Sup errors in the upgrade to Ruby 1.9.
>
> Anyway, I still can't get it to run even with 0.12.1. Here's the
> general situation (reposted partially from my comments there):
>
> * use ruby-xapian-full
> * need gettext to be a gem and not a regular install... -- pacman -Rd
> your ruby-gettext and sudo gem install ruby-gettext (STILL A PROBLEM,
> SHOULD TALK TO THE MAINTAINER OF THAT PACKAGE)
> * gem install sup:
> - Won't install in local mode (i.e. into your ~), fyi (not that I care a lot)
> - Still attempts to build ncurses (which fails)? Why's that? If I
> override and install it without dependencies it seems to use ncursesw
> happily enough.
> * The new package throws up this runtime error without a .sup directory:
>
> --- RuntimeError from thread: main
> can't modify frozen string
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/account.rb:54:in
> `force_encoding'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/account.rb:54:in
> `block in add_account'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/account.rb:54:in `each'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/account.rb:54:in `add_account'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/account.rb:38:in `initialize'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:613:in `new'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:613:in `init'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup.rb:164:in `start'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup:153:in `<module:Redwood>'
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup:69:in `<top (required)>'
> /usr/bin/sup:19:in `load'
> /usr/bin/sup:19:in `<main>'
>
> The above I've seen to be bug 98 on the bugtracker... but for whatever
> reason, the bugtracker has been down for a week or two on my end.
>
> What xapian package do you recommend using? Maybe that's the source of
> my problems.
It also likes to indulge in this error on occasion:
/usr/bin/ruby: symbol lookup error:
/usr/lib/ruby/gems/1.9.1/gems/ncursesw-1.2.4.1/lib/ncursesw_bin.so:
undefined symbol: STR2CSTR
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-01-25 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 7:07 [sup-devel] " Rich Lane
2011-01-17 10:44 ` [sup-talk] " Shadowfirebird
2011-01-17 22:03 ` Philipp Überbacher
2011-01-18 3:36 ` Rich Lane
2011-01-25 16:24 ` Andrei Thorp
2011-01-25 16:46 ` Andrei Thorp [this message]
2011-01-26 15:52 ` William Morgan
2011-01-26 18:22 ` Rich Lane
2011-01-26 19:11 ` William Morgan
2011-01-26 15:50 ` William Morgan
2011-01-27 18:51 ` Andrei Thorp
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='AANLkTi=QRBEFuj8EPHchoqDYL=SsAS2ZRt7=a-mM6tem@mail.gmail.com' \
--to=garoth@gmail.com \
--cc=rlane@club.cc.cmu.edu \
--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