Master branch is in a bit of flux, however you can try to try pulling again
and remove backgroundrb related scripts from script directory and run rake
backgroundrb:setup and you should be good to go.



On Wed, Apr 15, 2009 at 9:32 PM, Sylvain Desbureaux <
[email protected]> wrote:

> I tried with ruby 1.8 and I have the same error message
> Perhaps it's because of rails 2.3.2 ?
>
> 2009/4/15 Sylvain Desbureaux <[email protected]>
>
> Hi all,
>> I have currently jruby 1.2.0 and rails 2.3.2
>> I installed chronic and packet
>> I then installed backgroundrb with the following command:
>> script/plugin install http://github.com/gnufied/backgroundrb.git (I'm
>> behind a proxy so I can't clone...)
>> the install did well (it's installed in vendor/plugin)
>> so I did the setup and the migration
>> but when I try to start the server, I have the following error:
>> /path/to/jruby-1.2.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> `const_missing': uninitialized constant BackgrounDRb::MasterProxy
>> (NameError)
>>     from script/backgroundrb:33
>>
>>
>> Any idea why?
>>
>> Thanks,
>>
>> Sylvain
>>
>
>
> _______________________________________________
> Backgroundrb-devel mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel
>



-- 
Let them talk of their oriental summer climes of everlasting conservatories;
give me the privilege of making my own summer with my own coals.

http://gnufied.org
_______________________________________________
Backgroundrb-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/backgroundrb-devel

Reply via email to