Subject: [sup-devel] [issue43] fails to start after running current next

From: Ben Walton <[email-masked]>
Date: Mon, 04 Jan 2010 18:11:23 +0000

New submission from Ben Walton <[email-masked]>:

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 <[email-masked]>
<http://masanjin.net/sup-bugs/issue43>
_________________________________________
_______________________________________________
Sup-devel mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-devel