From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.13.12 with SMTP id z12cs1219122ebz; Mon, 4 Jan 2010 10:32:29 -0800 (PST) Received: by 10.229.24.195 with SMTP id w3mr1275581qcb.38.1262629948865; Mon, 04 Jan 2010 10:32:28 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 37si31810196qyk.20.2010.01.04.10.32.28; Mon, 04 Jan 2010 10:32:28 -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 17AC11779940; Mon, 4 Jan 2010 13:32:28 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 151A5185828E for ; Mon, 4 Jan 2010 13:11:26 -0500 (EST) Received: from localhost ([127.0.0.1] helo=entry.masanjin.net) by entry.masanjin.net with esmtp (Exim 4.69) (envelope-from ) id 1NRrOl-0006DV-S5 for sup-devel@rubyforge.org; Mon, 04 Jan 2010 10:11:26 -0800 MIME-Version: 1.0 To: sup-devel@rubyforge.org From: Ben Walton Date: Mon, 04 Jan 2010 18:11:23 +0000 Precedence: bulk X-Roundup-Name: Sup issue tracker X-Roundup-Loop: hello X-Roundup-Version: 1.4.10 Message-Id: <1262628683.67.0.115853254107.issue43@masanjin.net> X-Roundup-issue-status: unread X-Roundup-issue-priority: bug In-Reply-To: <1262628683.67.0.115853254107.issue43@masanjin.net> Subject: [sup-devel] [issue43] fails to start after running current next X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Reply-To: Sup issue tracker , Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Ben Walton : Sup failed to start after updating to next (sha1: a1669), which is where the ruby-1.9-encoding branch was merged. It seems that my ruby doesn't like the :BINARY suffix on the file open mode introduced by commit a6bb5. Removing :BINARY from the mode parameter works for me. Eg: wr:BINARY -> wb, ab:BINARY -> ab, etc. -Ben ---------- messages: 108 nosy: bwalton priority: bug ruby_version: 1.8.5 status: unread sup_version: next/a1669 title: fails to start after running current next _________________________________________ Sup issue tracker _________________________________________ _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel