Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Andrei Thorp <garoth@gmail.com>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] Arch Linux Sup Package (Ruby 1.9.1 + Sup 0.9)
Date: Wed, 28 Oct 2009 20:32:00 -0400	[thread overview]
Message-ID: <80055d7c0910281732v60908755kd5b43464aaac30ce@mail.gmail.com> (raw)
In-Reply-To: <20091029000759.GA5109@gmail.com>

On Wed, Oct 28, 2009 at 8:07 PM, Sean Escriva <sean.escriva@gmail.com> 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
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  parent reply	other threads:[~2009-10-29  0:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 15:05 Andrei Thorp
2009-10-19  1:22 ` wagnerdm
     [not found] ` <20091029000759.GA5109@gmail.com>
2009-10-29  0:32   ` Andrei Thorp [this message]
2009-10-30 21:56     ` William Morgan
2009-10-30 22:02 ` William Morgan
2009-11-01 16:23 ` William Morgan
2009-11-06  1:58   ` 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=80055d7c0910281732v60908755kd5b43464aaac30ce@mail.gmail.com \
    --to=garoth@gmail.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