From: fedzor <fedzor@gmail.com>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] help installing on FC17 on 64bit
Date: Tue, 22 Jan 2013 14:23:50 -0500 [thread overview]
Message-ID: <EECD4B7D-1CE9-4287-BCA3-D427465A49D2@gmail.com> (raw)
In-Reply-To: <1358183706-sup-7745@bloovis.org>
I'm getting a similar error. Why does this have to be, though? Why is this error coming up in the first place?
I'm posing the question now but I'll investigate shortly.
On Jan 14, 2013, at 12:23 PM, Mark Alexander wrote:
> Excerpts from Philippe LeCavalier's message of Mon Jan 14 10:12:58 -0500 2013:
>> /usr/share/rubygems/rubygems/custom_require.rb:36:in `require': superclass
>> mismatch for class Iconv (TypeError)
>
> I vaguely recall running into this when experimenting with sup on
> Linux Mint 13 and got around the problem with the following patch. I
> was just trying to see if it would even run at all on a new version of
> Mint (I normally use sup on a machine running Mint 10). On this
> experimental machine I had no mail in the index, and this was a patch
> against my copy of the sup git repository, not against any installed
> package. So no guarantees that this will work.
>
> diff --git a/bin/sup b/bin/sup
> index ad7a0d1..8e87a83 100755
> --- a/bin/sup
> +++ b/bin/sup
> @@ -19,6 +19,7 @@ end
>
> require 'fileutils'
> require 'trollop'
> +require 'iconv'
> require "sup"; Redwood::check_library_version_against "git"
>
> if ENV['SUP_PROFILE']
> _______________________________________________
> sup-talk mailing list
> sup-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2013-01-22 19:47 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 [this message]
2013-01-22 19:51 ` Philippe LeCavalier
2013-01-22 20:14 ` Matthieu Rakotojaona
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=EECD4B7D-1CE9-4287-BCA3-D427465A49D2@gmail.com \
--to=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