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