Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Sup won't start after upgrade to ruby 1.8.7
Date: Tue, 03 Jun 2008 19:57:58 -0700	[thread overview]
Message-ID: <1212548156-sup-6578@entry> (raw)
In-Reply-To: <73bc18b90806030405w5d345b38p3f40542c870a5626@mail.gmail.com>

Reformatted excerpts from Benjamin Kircher's message of 2008-06-03:
> got an exception, which is attached. I'm running the git master branch
> on a Debian sid box. Today ruby and libncurses5 got updated and Sup
> won't start anymore.

Gah. This doesn't even make any sense:

> --- ArgumentError from thread: main
> wrong number of arguments (2 for 1)
> /home/benjamin/projects/sup/lib/sup/index.rb:422:in `respond_to?'
> /home/benjamin/projects/sup/lib/sup/index.rb:422:in `flatten'

There's no call to respond_to? in there.

I guess I should download 1.8.7 and see what they've done. Maybe Hash.[]
has changed?
-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2008-06-04  2:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 11:05 Benjamin Kircher
2008-06-04  2:57 ` William Morgan [this message]
2008-06-11 16:21   ` zak kriner

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=1212548156-sup-6578@entry \
    --to=wmorgan-sup@masanjin.net \
    /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