From: sean.escriva@gmail.com (Sean Escriva)
Subject: [sup-talk] Sup and Ruby 1.9.1 - deadlock?
Date: Tue, 15 Sep 2009 10:53:39 -0700 [thread overview]
Message-ID: <20090915175339.GA15735@gmail.com> (raw)
In-Reply-To: <1253030868-sup-8556@mithink>
Excerpts from Michael Hamann's message of Tue Sep 15 06:20:59 +0200 2009:
> Hi,
>
> as Arch Linux has decided to put Ruby 1.9.1 into the extra repository I've got
> Ruby 1.8 replaced by 1.9.1 today. I then tried reinstalling all dependencies of
> sup again with Ruby 1.9.1. I've also found a Ferret gem for Ruby 1.9.1 at
> http://pennysmalls.com/2009/03/24/ferret-on-ruby-191/.
I followed a similar path after the recent upgrade to no avail. In the
end I downgraded ruby back to 1.8.7_p160 from older arch packages
available here:
http://www.schlunix.org/archlinux/extra/os/x86_64/
I'd like a better solution, but I've become dependent on sup for daily
work.
> [..snip..]
next prev parent reply other threads:[~2009-09-15 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 16:20 Michael Hamann
2009-09-15 17:53 ` Sean Escriva [this message]
2009-09-15 21:24 ` Dusan
2009-09-15 20:32 ` Rich Lane
2009-09-26 14:48 ` William Morgan
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=20090915175339.GA15735@gmail.com \
--to=sean.escriva@gmail.com \
/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