20:55 <btmike> any sles geeks here? I'm running into some issues trying to install foreman-proxy on sles 11.3 via git/bundler.

21:04 <btmike> *crickets*

21:12 <btmike> I'm just gonna rattle off the problem, maybe someone else can answer. Here's what I'm getting:

21:12 <btmike> L055-LDAP-1V:/usr/share/foreman-proxy # bundle install Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine. Your Gemfile lists the gem rdoc (>= 0) more than once. You should probably keep only one of them. While it's not a problem now, it could cause errors if you change the version of just one of them later. Your Gemfi

21:12 <btmike> feh

21:12 <btmike> ...

21:12 <btmike> extconf.rb:27: augeas-devel not installed (RuntimeError) To see why this extension failed to compile, please check the mkmf.log which can be found here: /usr/share/foreman-proxy/vendor/ruby/1.8/extensions/x86_64-linux/1.8/ruby-augeas-0.5.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /usr/share/foreman-proxy/vendor/ruby/1.8/gems/ruby-augeas-0.5.0 for inspection. Results logged to /usr/share/foreman-proxy

21:12 <btmike> thing is

21:12 <btmike> augeas IS installed:

21:13 <btmike> zypper shows augeas and ruby 1.8-rubygem-ruby-augeas packages installed

21:13 <btmike> moreover this WAS working

21:13 <btmike> but I just wanted to try to reinstall it with the --path=vendor variable

21:13 <btmike> which of course I find out after the fact is remembered >_>

21:14 <btmike> now it's acting like augeas isn't installed, so I'm kind of at a loss.

21:14 <indirect> btmike: using --path means you have just explicitly told Bundler to NOT use the ruby-1.8-rubygems-ruby-augeas package

21:15 <indirect> as far as I can tell, this is just Bundler doing what you told it to do

21:15 <btmike> hm

21:15 <btmike> any way I can get it back to default behavior?

21:16 <indirect> btmike: sure, run `bundle install --system`

21:16 <btmike> still getting an error with respect to ruby-augeas unfortunately

21:16 <btmike> I guess I could try a zypper remove and reinstall that way

21:17 <btmike> then rerun bundle

21:17 <indirect> "an error" isn't really helpful for debugging purposes, could you be more specific?

21:17 <btmike> understood; it's the same error as before:

21:17 <btmike> extconf.rb:27: augeas-devel not installed (RuntimeError) To see why this extension failed to compile, please check the mkmf.log which can be found here: /usr/lib64/ruby/gems/1.8/extensions/x86_64-linux/1.8/ruby-augeas-0.5.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /usr/lib64/ruby/gems/1.8/gems/ruby-augeas-0.5.0 for inspection. Results logged to /usr/lib64/ruby/gems/1.8/extensions/x86_64-linux/1.8/rub

21:17 <indirect> I don't know where your package manager installs the augeas gem

21:18 <indirect> but if Bundler is trying to install your bundle to the same place as the package manager has already installed the gem, it will just use the installed one instead

21:18 <indirect> and not try to compile (which seems to be what is failing)

21:19 <btmike> full error output: http://pastie.org/10737740

21:20 <indirect> the error is very explicit: "extconf.rb:27: augeas-devel not installed"

21:20 <indirect> if you want to compile the augeas gem, you need to have augeas-devel installed

21:21 <btmike> hm

21:21 <btmike> that said I do have that installed via zypper as well

21:21 <indirect> then it doesn't know where to look, I guess

21:21 <indirect> but I can't give you specific advice about how to compile a certain gem

21:22 <btmike> sounds correct to me. Not sure how to tell it where to look. This is my first experience working with bundler, tbh.

21:22 <indirect> gems can run literally any arbitrary code they want to

21:22 <indirect> Bundler just invokes the install process for each gem

21:22 <indirect> if you're having trouble with a particular gem, you need to talk to the gem author(s)

21:22 <btmike> fair enough, thanks for the heads up with --system though

21:22 <indirect> no problem

21:22 <btmike> take it easy

21:22 <indirect> in general, you can see config by running `bundle config`

21:23 <indirect> and you can delete all config with `rm -rf .bundle/config`

21:23 <indirect> er, `rm -rf .bundle`

21:23 <indirect> hope you figure it out!