Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
To: fedzor <fedzor@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] help installing on FC17 on 64bit
Date: Tue, 22 Jan 2013 21:14:25 +0100	[thread overview]
Message-ID: <CAMiZLn3iYci=-iUM44kmtFYNF1QFExkMySzBZnf7sTwrYrNaRQ@mail.gmail.com> (raw)
In-Reply-To: <EECD4B7D-1CE9-4287-BCA3-D427465A49D2@gmail.com>

On Tue, Jan 22, 2013 at 8:23 PM, fedzor <fedzor@gmail.com> wrote:
> I'm getting a similar error. Why does this have to be, though? Why is this error coming up in the first place?

class Iconv is redefined in util.rb [0]. If you 'require "iconv"' over
that, there will be a conflict (which one is the real one). I really
don't know how to work around this one; the "easy" solution would be
to uninstall the iconv gem, but this isn't really long-term. If you
have time and courage, you should remove the custom Iconv class and
replace it with the Decoder[1] class from heliotrope. It's a
continuation of this Iconv class, taking into account the tricky 1.9.

[0] https://github.com/sup-heliotrope/sup/blob/dd129e12603f5c77846c5fa624b8f118d53fbd0e/lib/sup/util.rb#L661
[1] https://github.com/sup-heliotrope/sup/pull/1#issuecomment-12415689
--
Matthieu RAKOTOJAONA
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


      parent reply	other threads:[~2013-01-22 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 15:12 Philippe LeCavalier
2013-01-14 17:23 ` Mark Alexander
2013-01-22 19:23   ` fedzor
2013-01-22 19:51     ` Philippe LeCavalier
2013-01-22 20:14     ` Matthieu Rakotojaona [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='CAMiZLn3iYci=-iUM44kmtFYNF1QFExkMySzBZnf7sTwrYrNaRQ@mail.gmail.com' \
    --to=matthieu.rakotojaona@gmail.com \
    --cc=fedzor@gmail.com \
    --cc=sup-talk@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