On Thu, Jun 11, 2020 at 3:36 PM n952162 <[email protected]> wrote: > > On 2020-06-11 14:47, Rich Freeman wrote: > > On Thu, Jun 11, 2020 at 4:10 AM Neil Bothwick <[email protected]> wrote: > > > > Most likely what you're probably going to end up wanting to try is: > > USE="python_targets_python3_6 -python_targets_python3_7" emerge -p1v > > sys-apps/portage > > (Remove the -p if the output of that looks sane.) > > > > That will temporarily adjust the python dependency settings for just > > that one command. You shouldn't use that USE setting any further > > after that - this is just to get portage updated once to allow python > > to be updated in the future - you don't want to stick with 3.6 forever > > and in a little while you won't even have that option. > > > I tried that: > > These are the packages that would be merged, in order: > > Calculating dependencies . ... done! > > !!! All ebuilds that could satisfy > ">=app-crypt/openpgp-keys-gentoo-release-20180706" have been masked. > !!! One of the following masked packages is required to complete your > request: > - app-crypt/openpgp-keys-gentoo-release-20191030::gentoo (masked by: EAPI 7) > > The current version of portage supports EAPI '6'. You must upgrade to a > newer version of portage before EAPI masked packages can be installed. > (dependency required by > "sys-apps/portage-9999::gentoo[-build,rsync-verify]" [ebuild]) > (dependency required by "sys-apps/portage" [argument])
Why are you installing portage-9999 now? This is going to be masked unless you've jumped through some hoops. Try: USE="python_targets_python3_6 -python_targets_python3_7 -rsync-verify" emerge -p1v =sys-apps/portage-2.3.99-r2 This should force the current stable version of portage and disable key verification so that you don't need those keys. You should also determine how you've unmasked portage-9999. I'd grep for portage in any of the config files in /etc/portage and remove it from anything in package.unmask or package.accept_keywords or package.keywords. -- Rich
