The ebuild is forcing an hard dependency on dev-libs/libgit2:0/24 resulting in an unresolved conflict with dev-python/pygit2 because Portage doesn't have any more a <dev-python/pygit2-0.25.0: !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-libs/libgit2:0 (dev-libs/libgit2-0.24.6:0/24::libressl, ebuild scheduled for merge) pulled in by <dev-libs/libgit2-0.25:0= required by (dev-lang/julia-0.6.1-r1:0/0::gentoo, ebuild scheduled for merge) ^ ^^^^^^^ (dev-libs/libgit2-0.25.1:0/25::libressl, installed) pulled in by =dev-libs/libgit2-0.25* required by (dev-python/pygit2-0.25.0:0/0::gentoo, installed) ^ ^^^^^
does the same apply to the -9999 ebuild?
> does the same apply to the -9999 ebuild? no, -9999 doesn't have the conflict; but I can't use the HEAD version of Julia either, because at the moment the branch is quite broken and unstable.
I can confirm that this is a problem: # equery depends libgit2 * These packages depend on libgit2: dev-lang/julia-0.6.1-r1 (<dev-libs/libgit2-0.25:0) # eix libgit2 [U] dev-libs/libgit2 Available versions: 0.26.0(0/26) **9999(0/26) {examples gssapi libressl +ssh test +threads trace} Installed versions: 0.24.6(0/24)(03:45:14 PM 02/08/2018)(-examples -gssapi -libressl -ssh -test -threads -trace) Homepage: https://libgit2.github.com/ Description: A linkable library for Git So it seems that either the older libgit2 has to be kept around, or the dependency needs an update.
Given that maintainer didn't care to reply for 3 months now, and the breakage now blocks git mirrors from updating, I would go for treecleaning.
Updated dependency to have a valid tree again.
