build environment: remove RUBYOPT

[mreinsch]

Still having some issue with bigtuna 0.1.4 and the build environment. In my case, RUBYOPT was set to: "-I/srv/dep/.rvm/gems/ruby-1.9.2-p180/gems/bundler-1.0.12/lib -rbundler/setup", which then causes the initial "bundler install" command to fail with: "Could not find activesupport-3.0.6 in any of the sources" or similar.

[michalbugno]

Are you sure it was the RUBYOPT issue? Remember that bundler may keep some settings in /.bundler folder and you may be using some incorrect bundle or something. Deleting the file inside folder could help.

[mreinsch]

I could reproduce the issue by setting RUBYOPT on the command line and running the "bundle install" command there on a fresh checkout. I also made sure that no .bundle directory exists. bigtuna also always creates a new clone from git before running the "bundle install" command.
I guess if you'd happen to have that version of rails installed as system gems, it wouldn't complain?

[michalbugno]

BigTuna doesn't alter the RUBYOPT env in any way. Did you try to run the command manually in the build dir and see if it works?

[mreinsch]

The RUBYOPT is coming from bundler. I'm running the delayed job with bundle exec, so it has the correct environment. So my suggestion would be to remove that from the environment before spawning a build command, as it interferes with it.