From: anonymous <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue98] `force_encoding': can't modify frozen string (RuntimeError) - On first start
Date: Mon, 03 May 2010 19:40:16 +0000 [thread overview]
Message-ID: <1272915616.88.0.00422065712816.issue98@masanjin.net> (raw)
In-Reply-To: <1272915616.88.0.00422065712816.issue98@masanjin.net>
New submission from anonymous:
Hello,
If I start sup or sup-config the very first time, the following error occurs:
/usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/account.rb:53:in
`force_encoding': can't modify frozen string (RuntimeError)
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/account.rb:53:in `block in
add_account'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/account.rb:53:in `each'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/account.rb:53:in `add_account'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/account.rb:37:in `initialize'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/util.rb:574:in `new'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/util.rb:574:in `init'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup.rb:126:in `start'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/bin/sup-config:115:in `<top
(required)>'
from /usr/bin/sup-config:19:in `load'
from /usr/bin/sup-config:19:in `<main>'
If I then run the command again, it is working, thus there exists an ~/.sup
directory. I can reproduce this error by removing the ~/.sup directory and
re-run it again. This 'cant modify frozen string'-issue can not be resolved by
applying the lines to multipart.rb mentioned in the FAQ.
Best regards
----------
messages: 222
nosy: anonymous
priority: bug
ruby_version: 1.9.1_p378
status: unread
sup_version: 0.11
title: `force_encoding': can't modify frozen string (RuntimeError) - On first start
_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue98>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
parent reply other threads:[~2010-05-03 19:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1272915616.88.0.00422065712816.issue98@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=1272915616.88.0.00422065712816.issue98@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