dev-ruby/json:0 (dev-ruby/json-1.7.7::gentoo, installed) pulled in by <=dev-ruby/json-1.7.7[ruby_targets_ruby19] required by (app-admin/chef-10.24.0::gentoo, installed) (dev-ruby/json-1.8.0::gentoo, ebuild scheduled for merge) pulled in by =dev-ruby/json-1*[ruby_targets_ruby20] required by (dev-ruby/rdoc-4.0.1-r1::gentoo, ebuild scheduled for merge) >=dev-ruby/json-1.7.7[ruby_targets_ruby20] required by (dev-lang/ruby-2.0.0_p247-r1::gentoo, ebuild scheduled for merge) >=dev-ruby/json-1.4[ruby_targets_ruby20] required by (dev-ruby/rdoc-4.0.1-r1::gentoo, ebuild scheduled for merge) Reproducible: Always Steps to Reproduce: 1.emerge -upvD world 2. 3. Actual Results: dev-ruby/json:0 (dev-ruby/json-1.7.7::gentoo, installed) pulled in by <=dev-ruby/json-1.7.7[ruby_targets_ruby19] required by (app-admin/chef-10.24.0::gentoo, installed) (dev-ruby/json-1.8.0::gentoo, ebuild scheduled for merge) pulled in by =dev-ruby/json-1*[ruby_targets_ruby20] required by (dev-ruby/rdoc-4.0.1-r1::gentoo, ebuild scheduled for merge) >=dev-ruby/json-1.7.7[ruby_targets_ruby20] required by (dev-lang/ruby-2.0.0_p247-r1::gentoo, ebuild scheduled for merge) >=dev-ruby/json-1.4[ruby_targets_ruby20] required by (dev-ruby/rdoc-4.0.1-r1::gentoo, ebuild scheduled for merge) Expected Results: upgrade
Most likely this will need to be fixed on the chef side. As far as I'm aware all json-1.x versions are API-compatible, and the changes for 1.8.0 don't list anything that would obviously change that.
Upstream have merged in a pull request into master to bump the dependency limit up to json-1.8.1 - https://github.com/opscode/chef/pull/1179. We just need opscode to create a release now...
(In reply to Stephen Kirkby from comment #2) > Upstream have merged in a pull request into master to bump the dependency > limit up to json-1.8.1 - https://github.com/opscode/chef/pull/1179. We just > need opscode to create a release now... As you can see there are no actual code changes, as expected for an API compatible version. This can simply be changed on the chef side now to ~> json 1.4, and in fact this should be done to keep things working on Gentoo in the future. https://wiki.gentoo.org/wiki/Project:Ruby/Packaging_RubyGems#Version_numbers_and_slots
Upstream last week has backported the fix to its stable-10 branch, and tagged the 10.32.0 release (no announcement yet). Still need to update the ebuild in addition to (or separately from) doing the version bump. Upstream asks for > 1.4 < 1.8.1, which could bite us in the future, so maybe upstream's gemspec should be relaxed by the ebuild too.
Now it's broken: dependency.bad 40 app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/desktop) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/desktop) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/desktop/gnome) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/desktop/gnome) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/desktop/gnome/systemd) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/desktop/gnome/systemd) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/desktop/kde) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/desktop/kde) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/desktop/kde/systemd) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/desktop/kde/systemd) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/developer) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/developer) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~x86(default/linux/x86/13.0) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~x86(default/linux/x86/13.0) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~x86(default/linux/x86/13.0/desktop) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~x86(default/linux/x86/13.0/desktop) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~x86(default/linux/x86/13.0/desktop/gnome) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~x86(default/linux/x86/13.0/desktop/gnome) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~x86(default/linux/x86/13.0/desktop/gnome/systemd) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~x86(default/linux/x86/13.0/desktop/gnome/systemd) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~x86(default/linux/x86/13.0/desktop/kde) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~x86(default/linux/x86/13.0/desktop/kde) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~x86(default/linux/x86/13.0/desktop/kde/systemd) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~x86(default/linux/x86/13.0/desktop/kde/systemd) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~x86(default/linux/x86/13.0/developer) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~x86(default/linux/x86/13.0/developer) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(hardened/linux/amd64) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(hardened/linux/amd64) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(hardened/linux/amd64/no-multilib) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(hardened/linux/amd64/no-multilib) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(hardened/linux/amd64/no-multilib/selinux) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(hardened/linux/amd64/no-multilib/selinux) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~amd64(hardened/linux/amd64/selinux) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~amd64(hardened/linux/amd64/selinux) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~x86(hardened/linux/x86) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~x86(hardened/linux/x86) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: DEPEND: ~x86(hardened/linux/x86/selinux) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]'] app-admin/chef/chef-10.24.0.ebuild: RDEPEND: ~x86(hardened/linux/x86/selinux) ['<=dev-ruby/json-1.7.7[ruby_targets_ruby19]']
I've added back json 1.7.7 for now but this must really be fixed on the chef side. I've confirmed on IRC with chef developers that there is no technical basis for this json dependency and they are just trying to avoid bugs in future versions.
(In reply to Hans de Graaff from comment #6) > I've added back json 1.7.7 for now but this must really be fixed on the chef > side. I've confirmed on IRC with chef developers that there is no technical > basis for this json dependency and they are just trying to avoid bugs in > future versions. And you removed it again. This is confusing!
+ 11 Dec 2014; Patrick Lauer <patrick@gentoo.org> chef-10.24.0.ebuild: + Unrestrict dev-ruby/json dep #484348
*** Bug 532162 has been marked as a duplicate of this bug. ***
The older version was dropped and the one left in the tree doesn't restrict json dep to anything