From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.90.87.14 with SMTP id k14cs1368790agb;
        Fri, 1 Jan 2010 11:06:40 -0800 (PST)
Received: by 10.224.34.231 with SMTP id m39mr9881672qad.188.1262372798569;
        Fri, 01 Jan 2010 11:06:38 -0800 (PST)
Return-Path: <sup-devel-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id 30si23949444qyk.33.2010.01.01.11.06.38;
        Fri, 01 Jan 2010 11:06:38 -0800 (PST)
Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org
Received: from rubyforge.org (rubyforge.org [127.0.0.1])
	by rubyforge.org (Postfix) with ESMTP id 24C22167830B;
	Fri,  1 Jan 2010 14:06:38 -0500 (EST)
Received: from entry.masanjin.net (masanjin.net [209.20.72.13])
	by rubyforge.org (Postfix) with ESMTP id 8D53815B802A
	for <sup-devel@rubyforge.org>; Fri,  1 Jan 2010 14:05:29 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=entry.masanjin.net)
	by entry.masanjin.net with esmtp (Exim 4.69)
	(envelope-from <roundup-admin@masanjin.net>) id 1NQmoQ-0001Sy-Lt
	for sup-devel@rubyforge.org; Fri, 01 Jan 2010 11:05:29 -0800
MIME-Version: 1.0
To: sup-devel@rubyforge.org
From: William Morgan <sup-bugs@masanjin.net>
Date: Fri, 01 Jan 2010 19:05:26 +0000
Precedence: bulk
X-Roundup-Name: Sup issue tracker
X-Roundup-Loop: hello
X-Roundup-Version: 1.4.10
Message-Id: <1262372726.5.0.155183041676.issue40@masanjin.net>
X-Roundup-issue-status: unread
X-Roundup-issue-priority: bug
In-Reply-To: <1262372726.5.0.155183041676.issue40@masanjin.net>
Subject: [sup-devel] [issue40] ruby 1.9: lockfile gem failure
X-BeenThere: sup-devel@rubyforge.org
X-Mailman-Version: 2.1.12
Reply-To: Sup issue tracker <sup-bugs@masanjin.net>,
	Sup developer discussion <sup-devel@rubyforge.org>
List-Id: Sup developer discussion <sup-devel.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-devel>
List-Post: <mailto:sup-devel@rubyforge.org>
List-Help: <mailto:sup-devel-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-devel-bounces@rubyforge.org
Errors-To: sup-devel-bounces@rubyforge.org


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