Hi,
Builds started to fail suddenly:
Installing gem dependencies: nokogiri (~> 1.15), aws-sdk-cloudformation (~> 1.0) You have already activated logger 1.5.0, but your Gemfile requires logger 1.6.6. Since logger is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports logger as a default gem. (Gem::LoadError)
Getting the same issue on my builds
$ rvm use $(travis_internal_ruby) --fuzzy do ruby -S gem install dpl -v 2.0.5.1
Successfully installed mime-0.4.4
Successfully installed json_pure-2.8.1
Successfully installed excon-0.112.0
Successfully installed travis-packagecloud-ruby-1.1.0
Successfully installed regstry-1.0.15
Successfully installed travis-cl-1.2.4
Successfully installed dpl-2.0.5.1
7 gems installed
dpl.1
Install deployment dependencies
Installing deployment dependencies
Installing gem dependencies: nokogiri (~> 1.15), aws-sdk-elasticbeanstalk (~> 1), aws-sdk-s3 (~> 1), rubyzip (~> 2.3), pathspec (~> 1.1)
GemWrappers: Can not wrap not executable file: /home/travis/.rvm/gems/ruby-3.3.5/bin/racc.lock
GemWrappers: Can not wrap not executable file: /home/travis/.rvm/gems/ruby-3.3.5/bin/racc.lock
GemWrappers: Can not wrap not executable file: /home/travis/.rvm/gems/ruby-3.3.5/bin/racc.lock
GemWrappers: Can not wrap not executable file: /home/travis/.rvm/gems/ruby-3.3.5/bin/racc.lock
You have already activated logger 1.6.0, but your Gemfile requires logger 1.6.6. Since logger is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports logger as a default gem. (Gem::LoadError)
failed to deploy
The comment below (adding gem install nokogiri and gem install logger) fixes the issue for now. My config uses jammy and node_js
Adding the below works for me now:
before_install:
- gem install nokogiri
- gem install logger
This worked for me. Thank you!
Hey all,
When using dpl v2, it’s recommended you add edge: true in your .travis.yml file. We are currently working on a fix and will provide updates soon.
If it helps, I’m seeing this during the deploy step of a node_js build on Focal
Does upgrading to a newer Linux distro fix this?
Our team is also having the same issue. Upgrading to jammy did not help. edge: true did.
Now I’m getting:
You have already activated logger 1.6.6, but your Gemfile requires logger 1.7.0. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)
We are having the same issue. adding edge: true worked yesterday when the error message was
You have already activated logger 1.6.0, but your Gemfile requires logger 1.6.6. Since logger is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports logger as a default gem. (Gem::LoadError)
but today, the error message is
You have already activated logger 1.6.6, but your Gemfile requires logger 1.7.0. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)
EDIT:
removing edge: true made it work once, then error again. 
Running into the same issue with jammy and edge: true, have not found a workaround yet.
Gonna add my team to the list of stuck people. Tried upgrading the OS to Jammy, using edge:true and also force installing logger with gem install logger -v 1.7.0 on before_install step
According to what we researched, Logger was recently updated and current version of the dpl gem had removed the hard dependency on Logger
+1
Same thing happening in my case also. Yesterday the build was working, using the edge: true workaround for the 1.6.0-1.6.6 bug. Today I’m getting the 1.6.6-1.7.0 bug.
Tried upgrading to dist: jammy, removing edge: true, force installing logger 1.7.0 with
before_deploy:
- rvm use $(travis_internal_ruby) --fuzzy do ruby -S gem uninstall logger -v 1.6.6
- rvm use $(travis_internal_ruby) --fuzzy do ruby -S gem install logger -v 1.7.0
and running the above commands as a script, and no luck so far
Haven’t confirmed it worked for all of our projects, but this helped:
before_install:
- gem update --system
Already managed to deploy some projects
Thanks for sharing, can confirm this works for our deploys (for now :-P).