| 1 |
I then tried to repeat this process, to see if I could get libcap |
| 2 |
installed and so get further with virtualbox, but for some reason, my |
| 3 |
other computer - although it also has virtualbox installed, has |
| 4 |
libcap-2.24*-r2*.ebuild instead of libcap-2.24.ebuild and worse, a |
| 5 |
libcap-2.*25*.tar.xz !!! Ebuild on the crashed machine isn't taking it. |
| 6 |
|
| 7 |
|
| 8 |
On 11/05/19 22:30, n952162 wrote: |
| 9 |
> |
| 10 |
> I moved the virtualbox-6* ebuilds out of that directory and was able |
| 11 |
> to regenerate the Manifest! |
| 12 |
> |
| 13 |
> The ebuild file merge worked quite well ... unfortunately, I ended up |
| 14 |
> here: |
| 15 |
> |
| 16 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../x86_64-pc-linux-gnu/bin/ld: |
| 17 |
> cannot find /lib64/libcap.so.2 |
| 18 |
> |
| 19 |
> Apparently pcap also got it's libraries trashed ... |
| 20 |
> |
| 21 |
> |
| 22 |
> On 11/05/19 22:22, n952162 wrote: |
| 23 |
>> |
| 24 |
>> I found the ebuild /file/ manifest command ... but got this: |
| 25 |
>> |
| 26 |
>> //usr/portage/app-emulation/virtualbox # ebuild |
| 27 |
>> /usr/portage/app-emulation/virtualbox/virtualbox-5.1.32.ebuild |
| 28 |
>> manifest // |
| 29 |
>> //!!! getFetchMap(): 'app-emulation/virtualbox-6.0.12' has |
| 30 |
>> unsupported EAPI: '7'// |
| 31 |
>> ///usr/portage/app-emulation/virtualbox # / |
| 32 |
>> |
| 33 |
>> I think I'm on EAPI 6. |
| 34 |
>> |
| 35 |
>> |
| 36 |
>> On 11/05/19 22:08, n952162 wrote: |
| 37 |
>>> I found a copy of the ebuild on a different machine I have - it's a x86 |
| 38 |
>>> not an amd64 architect, but maybe it's architecture-agnostic. I wonder |
| 39 |
>>> if I copy that to my amd64 machine (which has the tarball of the |
| 40 |
>>> package), will I need anything else? |
| 41 |
>>> |
| 42 |
>>> |
| 43 |
>>> On 11/05/19 21:44, Alarig Le Lay wrote: |
| 44 |
>>>> If the version you want isn’t in the tree anymore, you can use `ebuild |
| 45 |
>>>> /path/to/it merge` |
| 46 |
>>>> |
| 47 |
>>>> On mar. 5 nov. 21:41:39 2019, n952162 wrote: |
| 48 |
>>>>> Thank you for the suggestion. |
| 49 |
>>>>> |
| 50 |
>>>>> I had version 5.1.32 installed - several components of that. When |
| 51 |
>>>>> I run |
| 52 |
>>>>> the command you suggest, it prompts: |
| 53 |
>>>>> |
| 54 |
>>>>> /The following keyword changes are necessary to proceed:// |
| 55 |
>>>>> //...// |
| 56 |
>>>>> //=app-emulation/virtualbox-5.2.34 ~amd64// |
| 57 |
>>>>> // |
| 58 |
>>>>> //Would you like to add these changes to your config files? |
| 59 |
>>>>> [Yes/No] // |
| 60 |
>>>>> / |
| 61 |
>>>>> |
| 62 |
>>>>> I'm afraid it's going to want to start all over again. |
| 63 |
>>>>> |
| 64 |
>>>>> |
| 65 |
>>>>> On 11/05/19 21:24, Alarig Le Lay wrote: |
| 66 |
>>>>>> emerge -vaA1 virtualbox |
| 67 |
>>> |
| 68 |
>>> |
| 69 |
>> |
| 70 |
> |
Archives