Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: col@baibell.org (Colin Bell)
Subject: [sup-talk] exception while syncing
Date: Thu, 01 Nov 2007 16:33:26 +1100	[thread overview]
Message-ID: <1193894943-sup-9567@lankhmar> (raw)
In-Reply-To: <47295D4F.9020101@gslab.com>

Excerpts from Manish Sapariya's message of Thu Nov 01 15:59:59 +1100 2007:
> Hi All,
> Is this known issue? If yes, can anyone suggest workaroud, if no
> where can log bug for this issue? Please let me know if you need
> more info in any case.
/usr/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser/multipart.rb:159:in
> `[]=': can't modify frozen string (TypeError)
>         from

Probably this problem from the FAQ
http://sup.rubyforge.org/FAQ.txt

P: I get some error message from Rubymail about frozen strings when
   importing messages with attachments.
S: The current solution is to directly modify RubyMail.
  Change line 159 of   multipart.rb to:
     chunk = chunk[0..start]
   This is because RubyMail hasn't been updated since like Ruby 1.8.2.
   Please bug Matt Lickey.


      reply	other threads:[~2007-11-01  5:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01  4:59 Manish Sapariya
2007-11-01  5:33 ` Colin Bell [this message]

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=1193894943-sup-9567@lankhmar \
    --to=col@baibell.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