app-admin/puppet/puppet-3.0.1.ebuild: DEPEND: ~hppa(default/linux/hppa/10.0) ['dev-ruby/hiera[ruby_targets_ruby18]', 'dev-ruby/hiera[ruby_targets_ruby19]'] app-admin/puppet/puppet-3.0.1.ebuild: DEPEND: ~ppc(default/linux/powerpc/ppc32/10.0) ['dev-ruby/hiera[ruby_targets_ruby18]', 'dev-ruby/hiera[ruby_targets_ruby19]'] app-admin/puppet/puppet-3.0.1.ebuild: DEPEND: ~sparc(default/linux/sparc/10.0) ['dev-ruby/hiera[ruby_targets_ruby18]', 'dev-ruby/hiera[ruby_targets_ruby19]']
Does hiera work when installed manually in hppa?
(In reply to comment #1) > Does hiera work when installed manually in hppa? I don't have access to hppa unfortunately.
adding hppa, maybe they can help verify, if verified, can we get it tagged?
Er, what went wrong here? You're not supposed to get this kind of breakage past repoman...
Marked ~hppa.
ppc done
I've updated puppet to 3.1, which is in testing now
3.2.2 now in tree for puppet 1.2.1 now in tree for hiera
sparc, any word on the re-keywording of hiera/puppet?
keyworded ~sparc for =app-admin/puppet-3.2.4 and =dev-ruby/hiera-1.2.1, removing sparc from cc
Ok, seems like it's all done, closing bug :D:D