That's odd. I have 6.0.12 installed, so EAPI 7 should not be a
problem. Note EAPI is applied per ebuild, not a system-wide thing.
What version of portage are you using?
On 2019.11.05 16:22, n952162 wrote:
I found the ebuild /file/ manifest command ... but got this:
//usr/portage/app-emulation/virtualbox # ebuild
/usr/portage/app-emulation/virtualbox/virtualbox-5.1.32.ebuild
manifest //
//!!! getFetchMap(): 'app-emulation/virtualbox-6.0.12' has unsupported
EAPI: '7'//
///usr/portage/app-emulation/virtualbox # /
I think I'm on EAPI 6.
On 11/05/19 22:08, n952162 wrote:
I found a copy of the ebuild on a different machine I have - it's a
x86
not an amd64 architect, but maybe it's architecture-agnostic. I
wonder
if I copy that to my amd64 machine (which has the tarball of the
package), will I need anything else?
On 11/05/19 21:44, Alarig Le Lay wrote:
If the version you want isn’t in the tree anymore, you can use
`ebuild
/path/to/it merge`
On mar. 5 nov. 21:41:39 2019, n952162 wrote:
Thank you for the suggestion.
I had version 5.1.32 installed - several components of that. When
I run
the command you suggest, it prompts:
/The following keyword changes are necessary to proceed://
//...//
//=app-emulation/virtualbox-5.2.34 ~amd64//
//
//Would you like to add these changes to your config files?
[Yes/No] //
/
I'm afraid it's going to want to start all over again.
On 11/05/19 21:24, Alarig Le Lay wrote:
emerge -vaA1 virtualbox
