From: William Morgan <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue40] ruby 1.9: lockfile gem failure
Date: Fri, 01 Jan 2010 19:05:26 +0000 [thread overview]
Message-ID: <1262372726.5.0.155183041676.issue40@masanjin.net> (raw)
In-Reply-To: <1262372726.5.0.155183041676.issue40@masanjin.net>
New submission from William Morgan <wmorgan-sup@masanjin.net>:
If the lock file is there, the lockfile gem dies with this error:
$XXX/ruby/gems/1.9.1/gems/lockfile-1.4.3/lib/lockfile.rb:475:in `load_lock_id':
undefined method `each' for #<String:0x00000002afa860> (NoMethodError)
It appears the gem is not 1.9-ready, so we'll need to work around it somehow.
----------
messages: 102
nosy: w
priority: bug
ruby_version: 1.9.1
status: unread
sup_version: git
title: ruby 1.9: lockfile gem failure
_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue40>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
parent reply other threads:[~2010-01-01 19:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1262372726.5.0.155183041676.issue40@masanjin.net>]
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=1262372726.5.0.155183041676.issue40@masanjin.net \
--to=sup-bugs@masanjin.net \
--cc=sup-devel@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