Thanks, Herr Hambley, for quick response, Maybe I misunderstand your answer, but I think I understand the conditional bundle. On my dev system, I bundle and gen up a Gemfile.lck which has rb-fsevent based upon the local OS and commit to git. But when I deploy I get the error--as the lockfile is referring to a gem that isn't required on the server. If I comment out the conditional line in the bundle, the deploy executes okay. So I guess my options that I can think of include: git hook rake task to temporarily comment out the offending line in Gemfile, bundle and git commit remove the offending gem server task that reissues the bundle, or suppresses the error somehow
and I so much appreciate your work-(might I suggest adding filenames to each of the code fragment examples on https://github.com/capistrano/capistrano/blob/master/README.md and updating your copyright dates to 2014) I would do a pull request myself, but I don't know if I would be correct. On Saturday, January 4, 2014 3:07:37 PM UTC-6, Jay Thompson wrote: > > Versions: > > - Ruby 1.9.3 > - Capistrano 3.0.1 > - Rake / Rails / etc rails 3.x > > Platform: > > - Working on maxos > - Deploying to. debian or fedora > > Logs: > > - Please past logs (as completely as possible to a 3rd party pasting > service such as pastie.org) > > ....git checkout and deploy steps and then I get: > > EBUG [5f99ef42] You are trying to install in deployment mode after > changing > DEBUG [5f99ef42] your Gemfile. Run `bundle install` elsewhere and add > the > DEBUG [5f99ef42] updated Gemfile.lock to version control. > DEBUG [5f99ef42] > DEBUG [5f99ef42] You have deleted from the Gemfile: > DEBUG [5f99ef42] * rb-fsevent > cap aborted! > bundle stdout: Nothing written > bundle stderr: Nothing written > /usr/local/rvm/gems/ruby-1.9.3- > Files: > > - Capfile default > - deploy.rb default > - Stage files (production.rb, staging.rb) vanilla > > I have the following gemfile line in a test group > > > group :test do > > gem 'rb-fsevent', :require => false if RUBY_PLATFORM =~/darwin/i > > end > > Does somebody advise the appropriate workaround for this situation where > the conditional seems to create a Gemfile.lck that includes the OSX > specific gem, and the production server does not require it, and errors on > the bundle? > -- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/4e7ebf33-31f5-45e7-89ab-2363b19eab00%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
