1 |
That's odd. I have 6.0.12 installed, so EAPI 7 should not be a |
2 |
problem. Note EAPI is applied per ebuild, not a system-wide thing. |
3 |
|
4 |
What version of portage are you using? |
5 |
|
6 |
On 2019.11.05 16:22, n952162 wrote: |
7 |
> I found the ebuild /file/ manifest command ... but got this: |
8 |
> |
9 |
> //usr/portage/app-emulation/virtualbox # ebuild |
10 |
> /usr/portage/app-emulation/virtualbox/virtualbox-5.1.32.ebuild |
11 |
> manifest // |
12 |
> //!!! getFetchMap(): 'app-emulation/virtualbox-6.0.12' has unsupported |
13 |
> EAPI: '7'// |
14 |
> ///usr/portage/app-emulation/virtualbox # / |
15 |
> |
16 |
> I think I'm on EAPI 6. |
17 |
> |
18 |
> |
19 |
> On 11/05/19 22:08, n952162 wrote: |
20 |
>> I found a copy of the ebuild on a different machine I have - it's a |
21 |
>> x86 |
22 |
>> not an amd64 architect, but maybe it's architecture-agnostic. I |
23 |
>> wonder |
24 |
>> if I copy that to my amd64 machine (which has the tarball of the |
25 |
>> package), will I need anything else? |
26 |
>> |
27 |
>> |
28 |
>> On 11/05/19 21:44, Alarig Le Lay wrote: |
29 |
>>> If the version you want isn’t in the tree anymore, you can use |
30 |
>>> `ebuild |
31 |
>>> /path/to/it merge` |
32 |
>>> |
33 |
>>> On mar. 5 nov. 21:41:39 2019, n952162 wrote: |
34 |
>>>> Thank you for the suggestion. |
35 |
>>>> |
36 |
>>>> I had version 5.1.32 installed - several components of that. When |
37 |
>>>> I run |
38 |
>>>> the command you suggest, it prompts: |
39 |
>>>> |
40 |
>>>> /The following keyword changes are necessary to proceed:// |
41 |
>>>> //...// |
42 |
>>>> //=app-emulation/virtualbox-5.2.34 ~amd64// |
43 |
>>>> // |
44 |
>>>> //Would you like to add these changes to your config files? |
45 |
>>>> [Yes/No] // |
46 |
>>>> / |
47 |
>>>> |
48 |
>>>> I'm afraid it's going to want to start all over again. |
49 |
>>>> |
50 |
>>>> |
51 |
>>>> On 11/05/19 21:24, Alarig Le Lay wrote: |
52 |
>>>>> emerge -vaA1 virtualbox |
53 |
>> |
54 |
>> |
55 |
> |