08:26 <sheldonh> i am trying to make a dynamic ruby gem loader compatible with bundler. i use configuration to determine and install a list of gems that provide injectable dependencies. now i want to tell Bundler (in process) to allow these to be #require()'d. how?

10:42 <solars> hi - can anyone tell me how I could resolve this? https://gist.github.com/solars/ff29d01daa1cc5e93a1c I fail :)

10:55 <kgrz> Downgrade activeldap would be my first step

10:56 <kgrz> The activemodel version is locked at 3.0.9 because of the actionmailer version 3.0.9 being used. And activeldap requires atleast 3.1.0 of activemodel gem.

10:56 <kgrz> So either the actionmailer can be upgraded to use a version in 3.1 range, or activeldap version can be bumped down

11:10 <solars> I saw that actionmailer is locked, let me try v3.1

11:13 <solars> damn, now I get https://gist.github.com/solars/ff29d01daa1cc5e93a1c

12:35 <kgrz> ouch

13:09 <sheldonh> re my dynamic gem loader question, i think the answer is: http://starjuice.net/post/137805291335/dyanamic-provider-gem-loading

13:11 <sheldonh> solars: that's an unlikely version requirement (exactly this patch level)

13:13 <sheldonh> solars: my guess is you have this in your Gemfile: gem "seekda-comm", "= 2.1.2"

13:13 <sheldonh> solars: are you sure you really need an old, static version of that gem?

13:16 <sheldonh> solars: if you really can't adjust your software to work with a newer seekda-comm, your only option is to downgrade to version 3.0.9 of the rails-related gems

13:17 <sheldonh> solars: i am wrong. that should be 3.0.20. but in my experience, downgrading a rails application is seldom worth the effort

14:11 <sheldonh> solars: ah, looking back at your original problem (activeldap's lack of support for rails 3.0), i'd say your only real option here is to upgrade seekda-comm

14:47 <solars> hi, sorry was afk

14:47 <solars> I managed to get it working

14:48 <solars> seekda-comm is a custom gem we have, the app does not use rails itself, only some helper gems

21:41 <jyaworski> Hey. Has anyone gotten puppetserver's gem to work with bundle?

21:43 <jyaworski> Trying to run the installed bundler gem directly gives: bash: /var/lib/puppet/jruby-gems/bin/bundler: java: bad interpreter: No such file or directory

21:43 <jyaworski> Likely because the puppetserver wrapper does a bunch of environment var setting.

21:49 <jyaworski> I think I got it. 'puppetserver ruby `which bundle`' just runs the script with puppetserver's ruby.