Re: [sup-talk] Sup 0.12 released

From: Andrei Thorp <garoth@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup 0.12 released
Date: Thu, 27 Jan 2011 13:51:49 -0500	[thread overview]
Message-ID: <AANLkTi=MTP05C-ZVVi=q5+giXctgfZNtwGrgPQ_t6Ljn@mail.gmail.com> (raw)
In-Reply-To: <1296056218-sup-3756@masanjin.net>

On Wed, Jan 26, 2011 at 10:50 AM, William Morgan
<wmorgan-sup@masanjin.net> wrote:
> Hi Andrei,
>
> These problems are all 1.9 related. But I'm very interested in getting
> Sup working with 1.9, so let's see if we can figure something out.
>
> Reformatted excerpts from Andrei Thorp's message of 2011-01-25:
>> * use ruby-xapian-full
>
> You may not need this; see Rich's comments earlier.

Yeah, I tried it with regular xapian-ruby-bindings, but sup seems to
insist on wanting "ruby-full" as a dependency. However, I haven't
checked this just now, so I might be misremembering!

>
>> * 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)
>
> Perhaps the package has not been updated to 1.9?

The package is up to date, I think. It's just doing an actual source
download and compile, so it's being installed in a non-gem format, if
I understand correctly. Sup then doesn't find it. This should be
something I can sort out myself though amongst the AUR. Again, not
100% sure on this one.

>> * gem install sup:
>>   - Won't install in local mode (i.e. into your ~), fyi (not that I care a lot)
>
> What is ther error? Sup shouldn't care where its source files go.

Yeah, ignore this. I think rubygems changed the behaviour I used to
remember where if you weren't sudo'd, it'd install as your local user
in ~/.gems or something. Nothing to worry about.

>>   - 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.
>
> This is weird. Sup doesn't depend on the ncurses gem any more. And that
> gem doesn't build under 1.9. Sup now depends on the ncursesw gem (which
> Rich has been releasing newer versions of) which *does* support 1.9.

I did experience this, but for whatever reason, gem is taking ages at
the moment so I can't test. Anyway, it doesn't matter for the package,
since I ignore gem dependencies during install and get them from the
Arch repos instead.

>> * 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'
>
> This is the most troubling. I will see if I can figure out what's going
> on here. I've seen this before and it's another symptom of Ruby 1.9
> string insanity.
>
>> 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.
>
> Due to spam reasons I've shut it down, at least for the time being.

Ew, spam :(

>> What xapian package do you recommend using? Maybe that's the source of
>> my problems.
>
> I suspect not, given the above.

PHENOMENAL NEWS! For the first time in ages, Sup now works properly on
Archlinux with ruby 1.9. The update to ncursesw fixes the frozen
string issue, and sup seems to be running properly! Fantastic! Ahh,
it's so pretty and blue. :D

Anyway, so hopefully things should be smoother now since Ruby should
be more stable and its libs are finally catching up. It's been a bit
of a pain to get sup to run on Arch in the past, but hopefully that's
largely behind us now. Thanks everyone.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk