lets get this stable and kill the whole 1.3.x series, that is the only package that blocks libtorrent-rasterbar PYTHON_COMPAT cleanup (py27 is on its way out in anyway).
Fine by me!
An automated check of this bug failed - repoman reported dependency errors (134 lines truncated): > dependency.bad net-p2p/deluge/deluge-2.0.3-r2.ebuild: RDEPEND: arm(default/linux/arm/17.0) ['dev-python/rencode[python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_8(-),python_single_target_python3_6(+)?,python_single_target_python3_7(+)?]'] > dependency.bad net-p2p/deluge/deluge-2.0.3-r2.ebuild: DEPEND: arm(default/linux/arm/17.0) ['net-libs/libtorrent-rasterbar[python,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_8(-),python_single_target_python3_6(+)?,python_single_target_python3_7(+)?]'] > dependency.bad net-p2p/deluge/deluge-2.0.3-r2.ebuild: RDEPEND: arm(default/linux/arm/17.0) ['dev-python/distro[python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_8(-),python_single_target_python3_6(+)?,python_single_target_python3_7(+)?]', 'dev-python/rencode[python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_8(-),python_single_target_python3_6(+)?,python_single_target_python3_7(+)?]', '>=dev-python/twisted-17.1.0[crypt,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_8(-),python_single_target_python3_6(+)?,python_single_target_python3_7(+)?]', 'dev-python/pygame[python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_8(-),python_single_target_python3_6(+)?,python_single_target_python3_7(+)?]', 'net-libs/libtorrent-rasterbar[python,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_8(-),python_single_target_python3_6(+)?,python_single_target_python3_7(+)?]']
It's not keyworded on arm/ppc. Where's the rekeywording bug?
An automated check of this bug failed - repoman reported dependency errors (8 lines truncated): > dependency.bad net-p2p/deluge/deluge-2.0.3-r2.ebuild: RDEPEND: x86(default/linux/x86/17.0) ['>=dev-python/twisted-17.1.0[crypt,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_8(-),python_single_target_python3_6(+)?,python_single_target_python3_7(+)?]'] > dependency.bad net-p2p/deluge/deluge-2.0.3-r2.ebuild: RDEPEND: x86(default/linux/x86/17.0/desktop) ['>=dev-python/twisted-17.1.0[crypt,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_8(-),python_single_target_python3_6(+)?,python_single_target_python3_7(+)?]'] > dependency.bad net-p2p/deluge/deluge-2.0.3-r2.ebuild: RDEPEND: x86(default/linux/x86/17.0/desktop/gnome) ['>=dev-python/twisted-17.1.0[crypt,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_8(-),python_single_target_python3_6(+)?,python_single_target_python3_7(+)?]']
I seem to remember that some new dependency was not present for arm/ppc, but I can't remember which one. I'll check ASAP.
not keyworded for sparc in version 2.0, also missing at least dev-python/distro
ping
arm/ppc are missing the following dependencies: dev-python/rencode dev-python/geoip-python (arm only, ppc has it)
We can go ahead for amd64 and x86, anyway, I think.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1920a10fb5bdcff8226016ddf023a53e0d11578c commit 1920a10fb5bdcff8226016ddf023a53e0d11578c Author: Richard Freeman <rich0@gentoo.org> AuthorDate: 2020-01-18 23:56:46 +0000 Commit: Richard Freeman <rich0@gentoo.org> CommitDate: 2020-01-18 23:56:46 +0000 net-p2p/deluge: amd64 stable Bug: https://bugs.gentoo.org/704986 Package-Manager: Portage-2.3.79, Repoman-2.3.16 Signed-off-by: Richard Freeman <rich0@gentoo.org> net-p2p/deluge/deluge-2.0.3-r2.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
An automated check of this bug succeeded - the previous repoman errors are now resolved.
Let's make it -r5, while we are at it: it's much improved.
If we don't want to wait that long (in case twisted-19.10.0 stabilisation is blocked for a longer time) then twisted-18.4.0 plus the dependencies listed in bug 705488 would be a possible intermediate step to get 2.0.3 done and cleanup old. But someone should establish wether tests do run successfully with 18.4.0.
amd64 stable
I suggest we simply drop x86 support from deluge for now, twisted seems to be pita here.
x86, ping.
Unable to check for sanity: > dependent bug #710566 has errors
All sanity-check issues have been resolved
x86 stable. Closing.
