* [sup-devel] [issue43] fails to start after running current next
@ 2010-01-04 18:11 Ben Walton
0 siblings, 0 replies; only message in thread
From: Ben Walton @ 2010-01-04 18:11 UTC (permalink / raw)
To: sup-devel
New submission from Ben Walton <bwalton@artsci.utoronto.ca>:
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-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue43>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-01-04 18:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-01-04 18:11 [sup-devel] [issue43] fails to start after running current next Ben Walton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox