ruby-ng galore.
hmmm.... Diego running without FEATURES="test"? !!! All ebuilds that could satisfy ">=dev-ruby/hoe-2.6.0[ruby_targets_ruby18]" have been masked. !!! One of the following masked packages is required to complete your request: - dev-ruby/hoe-2.6.1 (masked by: ~x86 keyword) - dev-ruby/hoe-2.6.0-r1 (masked by: ~x86 keyword) (dependency required by "dev-ruby/zentest-4.3.3" [ebuild])
I should be clearer... whenever I open a bug for ruby-ng, it's meant to be recursive :P
(In reply to comment #2) > I should be clearer... whenever I open a bug for ruby-ng, it's meant to be > recursive :P I was just about to drag ruby-enterprise with it, are you sure (y/N)? Seriously, which hoe I should stabilize? (separate bug preferred), and please check for unwanted ruby-enterprise deps. I tried locally with hoe-2.6.1, and it dragger ruby-enterprise (repoman).
Gha sorry about that; 2.6.0-r1 is cleaned to go :)
am I missing something or shouldn't we remove ree18 for hoe-seattlerb and zentest? # emerge -1 =dev-ruby/zentest-4.3.3 -pv These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] virtual/ruby-minitest-0 RUBY_TARGETS="jruby* ruby18" 0 kB [ebuild U ] dev-ruby/hoe-2.6.0-r1 [2.5.0] USE="test -doc" RUBY_TARGETS="jruby* ruby18" 112 kB [ebuild N ] dev-ruby/hoe-seattlerb-1.2.2 USE="test -doc" RUBY_TARGETS="jruby ruby18 -ree18 (-ruby19)" 11 kB [ebuild N ] dev-ruby/zentest-4.3.3 USE="test -doc" RUBY_TARGETS="jruby ruby18 -ree18 (-ruby19)" 60 kB
I get the same failure as in bug #323059 in my x86 chroot, but not amd64 chroot.
stable x86, thanks Markus, totally fine here
(In reply to comment #7) > stable x86, thanks Markus, totally fine here I reverted the stable keyword for zentest, as it ultimately pulls in packages that want Ruby Enterprise stable. I am not willing to research the whole dependency tree and report back. Please make a sane list of ebuilds to mark stable (even if this means 100 Ruby packages at once).
For amd64 and x86 my suggestion would be to wait until we stabilize ruby-enterprise. Other arches do not have ruby-enterprise keyworded at all and can continue.
We will do it in bug 333867
x86 stable
ia64 stable
DEPEND.bad 7 dev-ruby/zentest/zentest-4.3.3.ebuild: amd64(hardened/linux/amd64) ['>=dev-ruby/hoe-2.6.0[ruby_targets_ruby18]', 'dev-ruby/hoe-seattlerb[ruby_targets_ruby18]', '>=dev-ruby/hoe-2.6.0[ruby_targets_ruby18]', 'dev-ruby/hoe-seattlerb[ruby_targets_ruby18]', '>=dev-ruby/hoe-2.6.0[ruby_targets_jruby]', 'dev-ruby/hoe-seattlerb[ruby_targets_jruby]', '>=dev-ruby/hoe-2.6.0[ruby_targets_jruby]', 'dev-ruby/hoe-seattlerb[ruby_targets_jruby]'] dev-ruby/zentest/zentest-4.3.3.ebuild: amd64(default/linux/amd64/10.0/server) ['>=dev-ruby/hoe-2.6.0[ruby_targets_ruby18]', 'dev-ruby/hoe-seattlerb[ruby_targets_ruby18]', '>=dev-ruby/hoe-2.6.0[ruby_targets_ruby18]', 'dev-ruby/hoe-seattlerb[ruby_targets_ruby18]', '>=dev-ruby/hoe-2.6.0[ruby_targets_jruby]', 'dev-ruby/hoe-seattlerb[ruby_targets_jruby]', '>=dev-ruby/hoe-2.6.0[ruby_targets_jruby]', 'dev-ruby/hoe-seattlerb[ruby_targets_jruby]'] Which versions of hoe-seattlerb and hoe should I stabilize?
(In reply to comment #13) > Which versions of hoe-seattlerb and hoe should I stabilize? The other arches have stabilized hoe-2.6.0-r1 and hoe-seattlerb-1.2.2, so it's probably best to stabilize those versions also for amd64.
ppc64 stable
amd64 done
Obsoleted by bug 354609
