The development of paludis has quite stalled, so I don't think we should expect any new release. At the same time, the snapshot has a few important fixes, in particular related to gcc compatibility. Let's stabilize it.
An automated check of this bug failed - repoman reported dependency errors (73 lines truncated): > dependency.bad sys-apps/paludis/paludis-3.0.0_pre20170808.ebuild: DEPEND: amd64(default/linux/amd64/13.0) ['dev-lang/ruby:2.3', 'dev-ruby/syntax[ruby_targets_ruby23]'] > dependency.bad sys-apps/paludis/paludis-3.0.0_pre20170808.ebuild: RDEPEND: amd64(default/linux/amd64/13.0) ['dev-lang/ruby:2.3'] > dependency.bad sys-apps/paludis/paludis-3.0.0_pre20170808.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop) ['dev-lang/ruby:2.3', 'dev-ruby/syntax[ruby_targets_ruby23]']
UnCC-ing arches until we proceed with ruby:2.3.
Re-adding arches so we can unbreak the tree.
An automated check of this bug failed - repoman reported dependency errors (125 lines truncated): > dependency.bad sys-apps/paludis/paludis-2.6.0.ebuild: DEPEND: amd64(default/linux/amd64/17.0) ['<dev-libs/boost-1.63[python,python_targets_python2_7(-)?,-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),python_single_target_python2_7(+)]'] > dependency.bad sys-apps/paludis/paludis-2.6.0.ebuild: RDEPEND: amd64(default/linux/amd64/17.0) ['<dev-libs/boost-1.63[python,python_targets_python2_7(-)?,-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),python_single_target_python2_7(+)]'] > dependency.bad sys-apps/paludis/paludis-2.6.0.ebuild: DEPEND: amd64(default/linux/amd64/17.0) ['<dev-libs/boost-1.63[python,python_targets_python2_7(-)?,-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),python_single_target_python2_7(+)]']
Ignoring stable-bot, repoman is fine with amd64/x86 if 2.6.0 is taken out of the equation. $ repoman full RepoMan scours the neighborhood... ebuild.badheader 1 sys-apps/paludis/paludis-3.0.0_pre20170808.ebuild: Invalid Gentoo Copyright on line: 1 Note: use --include-dev (-d) to check dependencies for 'dev' profiles RepoMan sez: "You're only giving me a partial QA payment? I'll take it this time, but I'm not happy."
x86 stopped stabilization due to bug 649520.
Ok, let's skip x86 from this release and add a new snapshot for them.
Please target the new snapshot instead. It has only a few tiny changes compared to the previous one, and should fix the x86 issue.
x86 stable
amd64 stable
amd64 stabilized the wrong version (please read 'package list').