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