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