From: Ben Walton <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue43] fails to start after running current next
Date: Mon, 04 Jan 2010 18:11:23 +0000 [thread overview]
Message-ID: <1262628683.67.0.115853254107.issue43@masanjin.net> (raw)
In-Reply-To: <1262628683.67.0.115853254107.issue43@masanjin.net>
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
parent reply other threads:[~2010-01-04 18:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1262628683.67.0.115853254107.issue43@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=1262628683.67.0.115853254107.issue43@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