r10k requires semantic_puppet0 and puppet_forge, puppet_forge requires semantic_puppet

Stefan Bethke stb at lassitu.de
Mon Jul 3 20:23:08 UTC 2017


Hey,

my r10k broke today:
/usr/local/lib/ruby/site_ruby/2.3/rubygems/specification.rb:1436:in `block in activate_dependencies': can't satisfy 'semantic_puppet (~> 0.1.0)', already activated 'semantic_puppet-1.0.0' (Gem::LoadError)
	from /usr/local/lib/ruby/site_ruby/2.3/rubygems/specification.rb:1428:in `each'
	from /usr/local/lib/ruby/site_ruby/2.3/rubygems/specification.rb:1428:in `activate_dependencies'
	from /usr/local/lib/ruby/site_ruby/2.3/rubygems/specification.rb:1410:in `activate'
	from /usr/local/lib/ruby/site_ruby/2.3/rubygems.rb:300:in `block in activate_bin_path'
	from /usr/local/lib/ruby/site_ruby/2.3/rubygems.rb:300:in `synchronize'
	from /usr/local/lib/ruby/site_ruby/2.3/rubygems.rb:300:in `activate_bin_path'
	from /usr/local/bin/r10k:23:in `<main>’

r10k wants semantic_puppet 0.1.0:
https://github.com/puppetlabs/r10k/blob/master/r10k.gemspec
s.add_dependency 'semantic_puppet', '~> 0.1.0‘

puppet_forge wants semantic_puppet 1.0.0:
https://github.com/puppetlabs/forge-ruby/blame/master/puppet_forge.gemspec
spec.add_dependency 'semantic_puppet', '~> 1.0‘

Any suggestions?  I’ll roll back to the previous package, but I’d rather have current packages that do work together properly.

This change was introduced in r444847, which updated puppet_forge to 2.2.7, which in turn bumped the semantic_puppet version.


Stefan

-- 
Stefan Bethke <stb at lassitu.de>   Fon +49 151 14070811



More information about the freebsd-ruby mailing list