Subject: Re: [sup-talk] Arch Linux Sup Package (Ruby 1.9.1 + Sup 0.9)

From: Andrei Thorp <[email-masked]>
Date: Wed, 28 Oct 2009 20:32:00 -0400

On Wed, Oct 28, 2009 at 8:07 PM, Sean Escriva <[email-masked]> wrote:
>
> On Sun, Oct 18, 2009 at 11:05:57AM -0400, Andrei Thorp wrote:
>> Hello. Remember me? ;)
>>
>> Anyway, I've rolled the 0.9 package for Arch Linux in the
>> AUR (community repos). It works, but:
>>  - Ruby 1.9.1 has pretty screwed up dependencies for Sup. Ncurses and ferret in
>>    particular were broken (at least in Arch.)
>>  - The package is a big ol' pile of hacks.
>>  - Ferret index is disabled (sorry for removing it early, but Ruby 1.9.1 is the
>>    reality for us in Arch.)
>>  - I've applyed Lloyd's patch for fixing the UTF-8 check.
>>  - There seem to be a few small bugs.
>>
>> Anyway, I'd appreciate some suggestions. The package is viewable here:
>> http://aur.archlinux.org/packages.php?ID=26439
>
> I gave the sup package a try today. I had previously put all the new
> ruby stuff on Hold. It didn't work for me. I post my output on the
> aur page.
>
> Any tips are appreciated, thanks.

Trace on AUR:

>    tried this today and everything installs fine, trying to run sup gives:
>
>    /usr/lib/ruby/gems/1.9.1/gems/lockfile-1.4.3/lib/lockfile.rb:475:in `load_lock_id': undefined method `each' for #<String:0x00000002f544d8> (NoMethodError)
>    from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:26:in `lockinfo_on_disk'
>    from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/index.rb:40:in `rescue in lock'
>    from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/index.rb:37:in `lock'
>    from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:520:in `method_missing'
>    from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/interactive-lock.rb:26:in `lock_interactively'
>    from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/bin/sup-sync:115:in `<top (required)>'
>    from /usr/bin/supbin/sup-sync:19:in `load'
>    from /usr/bin/supbin/sup-sync:19:in `<main>'

Delete comment

Hmm... works for me. Could you please give me a few more details:
- 64 bit or 32 bit? Any other system specs worth noting?
- This happens immediately on run or do you need to perform some action?
- Please try running sup while in ~. I've found some bugs occasionally
if you're in some strange directory.
- While building my package, does it say that it is rolling lockfile
for you? It seems your lockfile's a bit screwy rather than Sup. If
lockfile already exists on the system, my package might not roll a new
one.
- That said, try removing the lockfile gem and installing a fresh one
using the "gem" utility.

The error up there doesn't really make sense. Each not defined on
buffer strings? Seems unlikely. You could also try running the
commands in my build step manually and install yourself the sup
dependencies that I list + the dependencies in the Arch repos and see
if sup does something then. This would be more serious debugging.

Anyway, for now, I can't reproduce the error on my system, and I'm
fully up to date with the Arch repos. I don't really know what to say.

Did you remember to switch your indexes to Xapian and so on?

Good luck,

-Andrei Thorp
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: William Morgan <[email-masked]>
Date: Fri, 30 Oct 2009 15:02:00 -0700

Reformatted excerpts from Andrei Thorp's message of 2009-10-18:
> AUR (community repos).

Very cool, thank you! I am very interested in moving to 1.9 so I'm
doubly happy someone else is doing the work. :)

> - I've set Xapian to the default by wrapping all of Sup's binaries
> with the SUP_INDEX variable in a script.

Seems fine. Eventually this will be the default.

>  - q no longer works properly. It prompts you with the regular yes/no
>  option as to whether you really want to quit. Neither y nor n seem to
>  have any effect; it is still possible to quit with Q.

Now that's weird. Do multi-commands (like ,n in thread-view-mode) work?
If not, we can insert some debugging code in BufferManager#ask_getch to
see what's going on?

>  - Will that patch get applied? It seems reasonable on a surface level.

Yes. Sorry, I'm very behind on patches.

> Once I do manage to get it set up, I'll continue testing. I'm not sure,
> but I'm getting the impression that rather little testing has been done
> with the new Ruby as it's not quite mainstream yet.

Which makes it perfect a complement to Sup. :)
-- 
William <[email-masked]>
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Andrei Thorp <[email-masked]>
Date: Thu, 5 Nov 2009 20:58:27 -0500

Sorry, William. I've been busy and haven't monitered the list. I'll
probably set up a proper mail system tonight so I don't screw this up
again.

> Which patch was this? The only "Lloyd patch" one I'm aware of is:
> http://github.com/lloyd/sup/commit/d07986419b87053b41f7ed4bd7b6d1e537704864

No, that's not it... the patch that I applied is
http://aur.archlinux.org/packages/sup/sup/fix-utf8-hack.patch. At
least' that's my copy of it that I uploaded to the AUR. I'm assuming
that Lloyd still has this in his repos somewhere. I'm not sure this
patch is strictly necessary, but at the time I was under the
impression that it seemed reasonable. Admittedly, I'm not a great Ruby
programmer.

Ah, here it is.
http://github.com/lloyd/sup/commit/e32c48c4abfb921c60d337354634cd905f7e9149

>> buffer strings?
>It makes sense to me. There's no String#each in Ruby 1.9, so this is
>probably a (trivially fixable) bug in the lockfile gem for 1.9.

I'm still not sure why this bug doesn't happen for me. Oh wait!
Discovery! Sean left a comment on my AUR page stating, "It was just a
stale lock file. removed ~/.sup/lock and it started up nicely." So
never mind that, lockfile's fine in 1.9.

As for trying things like ,n, I'll give it a whirl tonight. I need to
set up my mail... I've been busy/putting it off :).

Cheers!

-Andrei Thorp

---

From: [email-masked]
Date: Sun, 18 Oct 2009 21:22:12 -0400

Quoting Andrei Thorp <[email-masked]>:

>  - Ferret index is disabled (sorry for removing it early, but Ruby  
> 1.9.1 is the reality for us in Arch.)

As long as your comfortable with AUR, there are a ruby1.8 and  
rubygems1.8 packages available.
~d
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: William Morgan <[email-masked]>
Date: Fri, 30 Oct 2009 14:56:53 -0700

> >    from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:26:in `lockinfo_on_disk'
[snip]

> Hmm... works for me. Could you please give me a few more details:
[snip]

---

From: Andrei Thorp <[email-masked]>
Date: Sun, 18 Oct 2009 11:05:57 -0400

Hello. Remember me? ;)

Some of the sketchier things:
 - I've set Xapian to the default by wrapping all of Sup's binaries with the
   SUP_INDEX variable in a script.
 - q no longer works properly. It prompts you with the regular yes/no option
   as to whether you really want to quit. Neither y nor n seem to have any
   effect; it is still possible to quit with Q.
 - Will that patch get applied? It seems reasonable on a surface level.

Anyway, as some of you can probably tell, I don't have Sup set up at the
moment. I'm working on it. Regardless, managing mail is a nightmare just now!
Once I do manage to get it set up, I'll continue testing. I'm not sure,
but I'm getting the impression that rather little testing has been done
with the new Ruby as it's not quite mainstream yet.

-Andrei "Garoth" Thorp

---

From: William Morgan <[email-masked]>
Date: Sun, 01 Nov 2009 08:23:03 -0800

which a) I don't quite understand, and b) isn't about utf8.
-- 
William <[email-masked]>
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk