dev-python/crossbar-17.6.1_p3 can not be installed with dev-python/twisted[http2]: partial crossbar RDEPEND: >=dev-python/twisted-17.5.0[${PYTHON_USEDEP}] <dev-python/hyper-h2-3.0.0[${PYTHON_USEDEP}] partial >=dev-python/twisted-17.5.0 RDEPEND: >=dev-python/hyper-h2-3.0.0[${PYTHON_USEDEP}] The crossbar 17.6.1 tag (and post3 tarball) requires h2-2.6.6 but the latest master requires 3.0.1. Perhaps even crossbar 17.6.1 will work find with h2-3.0.1. Reproducible: Always
hmm, I'll look into that in a few days. My initial install for crossbar was needed for our work buildbot which I am making into a multi-master system. For that I am creating a standalone system for the buildbot backend db and crossbar. I had no conflict in that case. There is also a new release of crossbar out in the last week (17.8.1_p1). I had a quick look, but there are a number of dependency updates and at least one new dep not in portage. I will see what I can do about it in the next week, but I make no promises. I have a very busy schedule this week. I have also created a simple init script for our works need, But it should be possible to extend it to do multiple realms. I also wonder if crossbar should not be in a different category, especially if I add the init script. It is a standalone server in its own right, especially as I know a little bit more about it now.
wow, a few days has turned into a month... :( I've just finished pkg-moving crossbar to net-misc, added conf.d and init.d scripts and sample config. Going over, the crossbar and twisted releases. Seems I can loosen the twisted dep up a bit to >=17.1.0. That will solve the initial dep conflict. But, the requirements-pinned.txt file shows h-2 at 2.6.2 with twisted-17.5.0. So likely the twisted dep is specifying h2 >=3.0.0 is tighter than it needed to be. But I cannot easily change that without patching twisted's internal Install_requires. I'm working on the crossbar-17.9.1 release now, that will solve it best as it wants h2 >=3.0.1
I'm getting numerous test failures with 17.9.1. Alternatively I've downgraded to 17.6.1_p3 with --nodeps option, edited the installed egginfo requires.txt for h2<=3.0.1 and all tests pass (when run as a user). So it does appear that they have overly restricted the dep. I won't apply a patch for that, but you can if you like. I'll keep working on the 17.9.1 release, it adds py3 support as well.
ok, after much anguish with crossbar-17.9.1 release test fails. It turns out that it needs the matching autobahn version due to new use of it's code. I've adjusted the 17.6.1_p3 ebuild dep and ended up adding both the 17.8.1 and 17.9.1 releases. There shouldn't be any more conflicts I hope. All are pushed to the tree now. Should not take long for the rsync servers to be caught up to get the changes via rsync
