Please test and mark stable this slot of dev-lang/ruby and its dependencies. This is the first ruby slot that makes use of use.stable.mask to keep the ruby_targets_ruby22 USE flag masked on stable, so in addition to adding keywords you will also need to remove the ruby22 entry in your arch package.use.stable and make.defaults file. This is similar to how python slots work. In summary: use.stable.mask: remove ruby_targets_ruby22 entry make.defaults: remove the RUBY_TARGETS entry hppa: you will need to handle bug 603816 first
An automated check of this bug failed - repoman reported dependency errors (51 lines truncated): > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: alpha(default/linux/alpha/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: alpha(default/linux/alpha/13.0/desktop) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: alpha(default/linux/alpha/13.0/desktop/gnome) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]']
(In reply to Stabilization helper bot from comment #1) > An automated check of this bug failed - repoman reported dependency errors ... because the mandatory profile changes have not been taken into account. I have set sanity-check to + manually.
(In reply to Hans de Graaff from comment #2) > (In reply to Stabilization helper bot from comment #1) > > An automated check of this bug failed - repoman reported dependency errors > > ... because the mandatory profile changes have not been taken into account. > I have set sanity-check to + manually. I still get errors from repoman with that list: RepoMan scours the neighborhood... dependency.bad [fatal] 5 dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: alpha(default/linux/alpha/13.0) [ '>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: alpha(default/linux/alpha/13.0/desktop) [ '>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: alpha(default/linux/alpha/13.0/desktop/gnome) [ '>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: alpha(default/linux/alpha/13.0/desktop/gnome/systemd) [ '>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: alpha(default/linux/alpha/13.0/developer) [ '>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]']
Also, dev-ruby/json pulls in rdoc, which needs a newer eselect-ruby: !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: app-eselect/eselect-ruby:0 (app-eselect/eselect-ruby-20151229:0/0::gentoo, ebuild scheduled for merge) pulled in by =app-eselect/eselect-ruby-20151229 (Argument) (app-eselect/eselect-ruby-20161226:0/0::gentoo, ebuild scheduled for merge) pulled in by >=app-eselect/eselect-ruby-20161226 required by (dev-ruby/rdoc-5.1.0:0/0::gentoo, ebuild scheduled for merge) ^^ ^^^^^^^^
Disregard the previous two comments, that's what happens when you get the profile changes wrong. Stable on alpha.
An automated check of this bug failed - repoman reported dependency errors (46 lines truncated): > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: amd64(default/linux/amd64/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: amd64(default/linux/amd64/13.0/desktop) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: amd64(default/linux/amd64/13.0/desktop/gnome) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]']
amd64, x86 stable (as discussed on #gentoo-dev with ago)
An automated check of this bug failed - the following atom is unknown: virtual/rubygems-11t Please verify the atom list.
An automated check of this bug failed - repoman reported dependency errors (24 lines truncated): > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: arm(default/linux/arm/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: hppa(default/linux/hppa/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: ia64(default/linux/ia64/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]']
Stable for HPPA.
profiles $ grep -r ruby22 desc/ruby_targets.desc:ruby22 - Build with MRI Ruby 2.2.x base/make.defaults:RUBY_TARGETS="ruby21 ruby22" arch/sparc/use.stable.mask:ruby_targets_ruby22 arch/powerpc/ppc64/use.stable.mask:ruby_targets_ruby22 arch/powerpc/ppc32/use.stable.mask:ruby_targets_ruby22 arch/arm64/use.stable.mask:ruby_targets_ruby22 arch/ia64/use.stable.mask:ruby_targets_ruby22 arch/arm/use.stable.mask:ruby_targets_ruby22
commit 25be5ad266afa59aeffe4e4c51ea82daba236fe0 Author: Hans de Graaff <graaff@gentoo.org> Date: Mon Apr 17 10:07:05 2017 +0200 Move current ruby22 status into arch profiles, bug 615818 Mask ruby_targets_ruby22 in the use.stable.mask of each arch and set RUBY_TARGETS to ruby21 in the make.defaults for each arch. This makes it possible to update the defaults in the main profile for a stable ruby:2.2 slot and consequently to mark ruby:2.2 stable on each arch in turn making sure that users of that arch will not end up with conflicting settings (e.g. stable ruby:2.2 but RUBY_TARGETS="ruby21"). Each arch is expected to remove these temporary entries as they mark ruby:2.2 stable, as per the instructions in bug 615818.
An automated check of this bug failed - repoman reported dependency errors (23 lines truncated): > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: arm(default/linux/arm/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: ia64(default/linux/ia64/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: ia64(default/linux/ia64/13.0/desktop) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]']
ia64 won't proceed here because of bug 561780
An automated check of this bug failed - repoman reported dependency errors (18 lines truncated): > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: arm(default/linux/arm/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: ppc(default/linux/powerpc/ppc32/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: ppc(default/linux/powerpc/ppc32/13.0/desktop) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]']
ia64 stable (in bug #561780 we've decided to deviate from rest of arches and stabilize =dev-lang/ruby-2.2.7-r2)
Stable on ppc, ppc64 as discussed with ago on #gentoo-dev.
An automated check of this bug failed - repoman reported dependency errors (3 lines truncated): > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: arm(default/linux/arm/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: sparc(default/linux/sparc/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: sparc(default/linux/sparc/13.0/desktop) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]']
arm stable
An automated check of this bug failed - repoman reported dependency errors (2 lines truncated): > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: sparc(default/linux/sparc/13.0) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: sparc(default/linux/sparc/13.0/desktop) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]'] > dependency.bad dev-lang/ruby/ruby-2.2.6.ebuild: PDEPEND: sparc(default/linux/sparc/13.0/desktop/gnome) ['>=dev-ruby/minitest-5.4.3[ruby_targets_ruby22]', '>=dev-ruby/power_assert-0.2.2[ruby_targets_ruby22]', '>=dev-ruby/test-unit-3.0.8[ruby_targets_ruby22]', 'virtual/rubygems[ruby_targets_ruby22]', '>=dev-ruby/json-1.8.1[ruby_targets_ruby22]', '>=dev-ruby/rake-0.9.6[ruby_targets_ruby22]', '>=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22]']
sparc no longer has a stable dev-lang/ruby.
sparc stable (thanks to Rolf Eike Beer)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=45b7a797ad73967fc818f4923c248555d31f77cb commit 45b7a797ad73967fc818f4923c248555d31f77cb Author: Sergei Trofimovich <slyfox@gentoo.org> AuthorDate: 2017-11-30 20:13:10 +0000 Commit: Sergei Trofimovich <slyfox@gentoo.org> CommitDate: 2017-11-30 20:14:43 +0000 arch/sparc/use.stable.mask: unmask ruby_targets_ruby22, bug #615818 Bug: https://bugs.gentoo.org/615818 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> profiles/arch/sparc/make.defaults | 4 ---- profiles/arch/sparc/use.stable.mask | 4 ---- 2 files changed, 8 deletions(-)}
arm64 ruby stable keywords got removed on purpose a while back for now; we'll reintroduce them as needed in the short/mid-term future, and then just whatever we need in the deptree and what is latest stable on amd64 at the time. Nothing to do as part of this bug, so unCCing and closing as last.
