|
|
Subject: Re: Rubygems Problems - msg#02648
List: ruby-talk
On Mar 31, 8:57 am, Dominic Sisneros <dsisn...@xxxxxxxxx> wrote:
> the update to mojombo-grit is the problem. Here is Aslax Hellesoy response
> to my inquiry on the rubygems mailing list
>
> 2009/3/31 Dominic Sisneros <dsisn...@xxxxxxxxx>
>
> > I did a gem cleanup and since then I have been getting the following error
> > whenever I try to use a gem
>
> I had the same problem yesterday, when I upgraded all my gems. It turns out,
> this error occurs if you have one broken gem.
I've tried to duplicate this but I can't. I installed grit 1.0.0, then
grit 1.1.0, then ran "gem clean", then fired up irb and loaded a gem.
I didn't have any problems.
I'm curious in what way the gem is broken. The require_paths appears
to just be set to 'lib', which is fine.
> My solution: Add a puts statement inside gem_path_searcher.rb to find out
> what gem is broken. Then uninstall it. (For me it was the latest
> mojombo-grit).
>
> And here is the result of the puts
>
> #<Gem::Specification name=mofo version=0.2.16>
> #<Gem::Specification name=mojombo-grit version=1.1.0>
> load error: C:/Documents and Settings/dominic e sisneros/.irbrc
This is interesting, and might be a clue as to the real problem. Could
spaces in the path name be an issue? I'm not sure. What does
your .irbc file look like? Also, do you have any non-ascii characters
in the path to the .irbc file?
> NoMethodError: undefined method `join' for nil:NilClass
Looks like spec.require_paths is returning nil, which is very odd.
Like I said, I can't duplicate this, and I'm not sure how that could
happen.
Regards,
Dan
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: Array read to seperate items
matt neuburg <matt@xxxxxxxxxxx> wrote:
> Stuart Clarke <stuart.clarke1986@xxxxxxxxx> wrote:
>
> > I have an array which gets data added to in a loop like so:
> >
> > a b c d e f
> > a b c d e f
> >
> > I am aware calling join("\n")on this array will separate each line of
> > the array with a new line, but I want to separate the individual items
> > and load them into there own arrays for example
> >
> > array a = a, a
> > array b = b, b
>
> Are you talking about something like this?
>
> arr = ["hey ho hey nonnie no", "bee bop a ding dong", "a b c d e"]
> arr = arr.map {|s| s.split(" ")}
> arr = arr.shift.zip(*arr)
Last line cute but unnecessary, forgot about "transpose" (see msg from
Rob B.):
arr = ["hey ho hey nonnie no", "bee bop a ding dong", "a b c d e"]
arr = arr.map {|s| s.split(" ")}.transpose
p arr
#=> [["hey", "bee", "a"], ["ho", "bop", "b"], ["hey", "a", "c"],
["nonnie", "ding", "d"], ["no", "dong", "e"]]
m.
--
matt neuburg, phd = matt@xxxxxxxxxxx, http://www.tidbits.com/matt/
Leopard - http://www.takecontrolbooks.com/leopard-customizing.html
AppleScript - http://www.amazon.com/gp/product/0596102119
Read TidBITS! It's free and smart. http://www.tidbits.com
Next Message by Date:
click to view message preview
xml-simp
I have dowunloaded the xml-simple-1.0.12.gem .
I used xml-simple to requie .
require 'xml-simple' But it doesn't work
Then I have given like this It works,
require 'xmlsimple'
My question is that,
How do i know it should be xmlsimple. But the gem file is
xml-simple-1.0.12.gem
--
Posted via http://www.ruby-forum.com/.
Previous Message by Thread:
click to view message preview
Re: Rubygems Problems
the update to mojombo-grit is the problem. Here is Aslax Hellesoy response
to my inquiry on the rubygems mailing list
2009/3/31 Dominic Sisneros <dsisnero@xxxxxxxxx>
> I did a gem cleanup and since then I have been getting the following error
> whenever I try to use a gem
>
I had the same problem yesterday, when I upgraded all my gems. It turns out,
this error occurs if you have one broken gem.
My solution: Add a puts statement inside gem_path_searcher.rb to find out
what gem is broken. Then uninstall it. (For me it was the latest
mojombo-grit).
And here is the result of the puts
#<Gem::Specification name=mofo version=0.2.16>
#<Gem::Specification name=mojombo-grit version=1.1.0>
load error: C:/Documents and Settings/dominic e sisneros/.irbrc
NoMethodError: undefined method `join' for nil:NilClass
Next Message by Thread:
click to view message preview
Re: Rubygems Problems
I am getting the exact same NoMethodError having to do with calling
'join' on a nil class. I'm on a linux machine with no spaces in path
names. I haven't had a chance to try printing stuff out in Rubygems
yet...
On 3/31/09, Daniel Berger <djberg96@xxxxxxxxx> wrote:
>
>
> On Mar 31, 8:57 am, Dominic Sisneros <dsisn...@xxxxxxxxx> wrote:
>> the update to mojombo-grit is the problem. Here is Aslax Hellesoy
>> response
>> to my inquiry on the rubygems mailing list
>>
>> 2009/3/31 Dominic Sisneros <dsisn...@xxxxxxxxx>
>>
>> > I did a gem cleanup and since then I have been getting the following
>> > error
>> > whenever I try to use a gem
>>
>> I had the same problem yesterday, when I upgraded all my gems. It turns
>> out,
>> this error occurs if you have one broken gem.
>
> I've tried to duplicate this but I can't. I installed grit 1.0.0, then
> grit 1.1.0, then ran "gem clean", then fired up irb and loaded a gem.
> I didn't have any problems.
>
> I'm curious in what way the gem is broken. The require_paths appears
> to just be set to 'lib', which is fine.
>
>> My solution: Add a puts statement inside gem_path_searcher.rb to find out
>> what gem is broken. Then uninstall it. (For me it was the latest
>> mojombo-grit).
>>
>> And here is the result of the puts
>>
>> #<Gem::Specification name=mofo version=0.2.16>
>> #<Gem::Specification name=mojombo-grit version=1.1.0>
>> load error: C:/Documents and Settings/dominic e sisneros/.irbrc
>
> This is interesting, and might be a clue as to the real problem. Could
> spaces in the path name be an issue? I'm not sure. What does
> your .irbc file look like? Also, do you have any non-ascii characters
> in the path to the .irbc file?
>
>> NoMethodError: undefined method `join' for nil:NilClass
>
> Looks like spec.require_paths is returning nil, which is very odd.
> Like I said, I can't duplicate this, and I'm not sure how that could
> happen.
>
> Regards,
>
> Dan
>
>
|
|