1 |
On 2/13/21 8:42 PM, Dan Egli wrote: |
2 |
> On 2/13/2021 2:41 PM, Steven Lembark wrote: |
3 |
> |
4 |
> [snip] |
5 |
>> Bumps into not having sys-apps/portage-9999::gentoo: |
6 |
>> # $emerge dev-db/pgmodeler |
7 |
>> Calculating dependencies... done! |
8 |
>> |
9 |
>> !!! All ebuilds that could satisfy |
10 |
>> "sys-apps/portage[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]" |
11 |
>> have been masked. |
12 |
>> !!! One of the following masked packages is required to complete your |
13 |
>> request: |
14 |
>> - sys-apps/portage-9999::gentoo (masked by: missing keyword) |
15 |
> |
16 |
> Portage-9999 is risky since it's VERY MUCH still developmental. BUT, if |
17 |
> you really want it, add this to your package.accept_keywords: |
18 |
> sys-apps/portage ** |
19 |
> |
20 |
> Include the two stars. That will override missing keyword. It may be |
21 |
> better to specify a full token rather than a shortcut. In that case use: |
22 |
> =sys-apps/portage-9999 ** |
23 |
> |
24 |
The portage-9999 suggestion seems like a red herring to me. More likely |
25 |
the reason the portage ebuild does not satisfy the dependency is because |
26 |
it is installed with different python_targets/python_single_target than |
27 |
what the consuming package wants. |