There's already a bug report open:
https://bugs.gentoo.org/709050
Is there a reason you use mplayer-9999 from that repository?
There's also an mplayer-9999 in the main portage tree.
Am Di., 25. Feb. 2020 um 06:01 Uhr schrieb Dale <rdalek1...@gmail.com>:
> Howdy,
>
> I get this when I try to emerge anything. This is part of a string of
> commands so the emerge command itself is missing but its my usual emerge
> -auDN world. Here's the error.
>
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies - * ERROR: media-video/mplayer-9999::bircoph
> failed (depend phase):
> * git-2.eclass could not be found by inherit()
> *
> * Call stack:
> | * ebuild.sh, line 609: Called source
> '/var/lib/layman/bircoph/media-video/mplayer/mplayer-9999.ebuild'
> * mplayer-9999.ebuild, line 8: Called inherit 'flag-o-matic'
> 'git-2' 'multilib' 'subversion' 'toolchain-funcs'
> * ebuild.sh, line 290: Called die
> * The specific snippet of code:
> * [[ -z ${location} ]] && die "${1}.eclass could not be
> found by inherit()"
> *
> * If you need support, post the output of `emerge --info
> '=media-video/mplayer-9999::bircoph'`,
> * the complete build log and the output of `emerge -pqv
> '=media-video/mplayer-9999::bircoph'`.
> * Working directory: '/usr/lib64/python2.7/site-packages'
> * S: '/var/tmp/portage/media-video/mplayer-9999/work/mplayer-9999'
> ... done!
>
>
>
> It started when I synced about a week ago. I thought it was a ebuild
> with a typo and would be fixed by the time I synced again. I synced a
> few minutes ago and this is still there. Either something is wrong with
> the tree or I have something off on my end. Since I've never put a 9999
> ebuild in a overlay, I don't think it is me but one never knows about
> these things. ;-) Despite the error, emerge does continue on. It
> spits that out very early on.
>
> Ideas? Bug that needs reporting? Something wrong on my end somewhere?
>
> Dale
>
> :-) :-)
>
>
