1 |
I get the following result: |
2 |
# emerge -pv1 olefile |
3 |
|
4 |
|
5 |
These are the packages that would be merged, in order: |
6 |
Calculating dependencies... done! |
7 |
[ebuild R ] dev-python/olefile-0.46::gentoo USE="-doc" |
8 |
PYTHON_TARGETS="python2_7 python3_6 (-pypy3) (-python3_7*) (-python3_8)" 0 |
9 |
KiB |
10 |
Total: 1 package (1 reinstall), Size of downloads: 0 KiB |
11 |
|
12 |
It seems to be in line with the interpretation I've come up with. |
13 |
|
14 |
Best regards |
15 |
Mickaël Bucas |
16 |
|
17 |
Le mar. 7 janv. 2020 à 16:18, Franz Fellner <alpine.art.de@×××××.com> a |
18 |
écrit : |
19 |
|
20 |
> And what if you change the line to "dev-python/olefile amd64"? |
21 |
> |
22 |
> Am Di., 7. Jan. 2020 um 17:10 Uhr schrieb Mickaël Bucas <mbucas@×××××.com |
23 |
> >: |
24 |
> |
25 |
>> Hi Franz |
26 |
>> |
27 |
>> Thanks for your reply. |
28 |
>> |
29 |
>> However your assumption is incorrect: these two commands are run on the |
30 |
>> same machine, with only the keyword on "olefile" changed. |
31 |
>> Thinking a bit more about it, Python 3.7 isn't stable yet, so I also have |
32 |
>> "=dev-lang/python-3.7* ~amd64" in package.accept_keyword. |
33 |
>> |
34 |
>> I've been able to reproduce this behavior in a chroot based on stage 3 |
35 |
>> with the minimum packages installed. |
36 |
>> I have in make.conf |
37 |
>> PYTHON_TARGETS="python2_7 python3_6 python3_7" |
38 |
>> In /var/lib/portage/world |
39 |
>> dev-lang/python:3.7 |
40 |
>> dev-python/olefile |
41 |
>> In /etc/portage/package.accept_keywords |
42 |
>> dev-python/olefile ~amd64 |
43 |
>> =dev-lang/python-3.7* ~amd64 |
44 |
>> dev-python/setuptools ~amd64 |
45 |
>> dev-python/certifi ~amd64 |
46 |
>> |
47 |
>> And emerge says : |
48 |
>> # emerge -pv1 olefile |
49 |
>> These are the packages that would be merged, in order: |
50 |
>> Calculating dependencies... done! |
51 |
>> [ebuild R ] dev-python/olefile-0.46::gentoo USE="-doc" |
52 |
>> PYTHON_TARGETS="python2_7 python3_6 python3_7 -pypy3 -python3_8" 0 KiB |
53 |
>> Total: 1 package (1 reinstall), Size of downloads: 0 KiB |
54 |
>> |
55 |
>> When I remove " dev-python/olefile ~amd64", Python 3.7 would be disabled : |
56 |
>> # emerge -pv1 olefile |
57 |
>> These are the packages that would be merged, in order: |
58 |
>> Calculating dependencies... done! |
59 |
>> [ebuild R ] dev-python/olefile-0.46::gentoo USE="-doc" |
60 |
>> PYTHON_TARGETS="python2_7 python3_6 (-pypy3) (-python3_7*) (-python3_8)" 0 |
61 |
>> KiB |
62 |
>> Total: 1 package (1 reinstall), Size of downloads: 0 KiB |
63 |
>> |
64 |
>> This is still puzzling me, but one interpretation may be : |
65 |
>> I you enable the unstable ~amd64 keyword on a package, the stable version |
66 |
>> of said package is allowed to run on the unstable version of the Python |
67 |
>> interpreter. |
68 |
>> |
69 |
>> This seems to be the intended behavior, as I found that at least 40 |
70 |
>> Python packages on each of my 2 systems are stable and have Python 3.7 |
71 |
>> enabled (I keyworded all of them sometime in the past...) |
72 |
>> |
73 |
>> Thanks |
74 |
>> Best regards |
75 |
>> Mickaël Bucas |
76 |
>> |
77 |
>> Le mar. 7 janv. 2020 à 08:08, Franz Fellner <alpine.art.de@×××××.com> a |
78 |
>> écrit : |
79 |
>> |
80 |
>>> I assume those emerge commands weren't done on one machine but come from |
81 |
>>> those two different machines. |
82 |
>>> This change in USE Flags can't come from that line in |
83 |
>>> package.accept_keywords. |
84 |
>>> This is a change in PYTHON_TARGETS in make.conf, package.use or |
85 |
>>> package.env. |
86 |
>>> Carefully go through those config files/directories, I am sure you will |
87 |
>>> find the offending line. |
88 |
>>> |
89 |
>>> Regards |
90 |
>>> Franz |
91 |
>>> |
92 |
>>> Am Fr., 3. Jan. 2020 um 11:44 Uhr schrieb Mickaël Bucas < |
93 |
>>> mbucas@×××××.com>: |
94 |
>>> |
95 |
>>>> Hello |
96 |
>>>> |
97 |
>>>> For some time I've been wondering why I had a difference on |
98 |
>>>> dev-python/olefile-0.46 between 2 machines : one was installed with |
99 |
>>>> python_targets_python3_7, the other wasn't. |
100 |
>>>> And I finally pinpointed it to package.accept_keywords containing |
101 |
>>>> "dev-python/olefile ~amd64" on one of the machines only |
102 |
>>>> |
103 |
>>>> At the time of writing, dev-python/olefile-0.46 is the stable version, |
104 |
>>>> and KEYWORDS contains "amd64" (no tilde) among others. |
105 |
>>>> |
106 |
>>>> When package.accept_keywords doesn't contain "dev-python/olefile |
107 |
>>>> ~amd64", I get : |
108 |
>>>> emerge -pv1 --verbose-conflicts olefile |
109 |
>>>> These are the packages that would be merged, in order: |
110 |
>>>> Calculating dependencies... done! |
111 |
>>>> [ebuild R ] dev-python/olefile-0.46::gentoo USE="-doc" |
112 |
>>>> PYTHON_TARGETS="python2_7 python3_6 (-pypy3) (-python3_7) (-python3_8)" 0 |
113 |
>>>> KiB |
114 |
>>>> Total: 1 package (1 reinstall), Size of downloads: 0 KiB |
115 |
>>>> |
116 |
>>>> => Python 3.7 is disabled |
117 |
>>>> |
118 |
>>>> When package.accept_keywords contains "dev-python/olefile ~amd64", I |
119 |
>>>> get : |
120 |
>>>> emerge -pv1 olefile |
121 |
>>>> These are the packages that would be merged, in order: |
122 |
>>>> Calculating dependencies... done! |
123 |
>>>> [ebuild R ] dev-python/olefile-0.46::gentoo USE="-doc" |
124 |
>>>> PYTHON_TARGETS="python2_7 python3_6 python3_7* -pypy3 -python3_8" 0 KiB |
125 |
>>>> Total: 1 package (1 reinstall), Size of downloads: 0 KiB |
126 |
>>>> |
127 |
>>>> => Python 3.7 is enabled |
128 |
>>>> |
129 |
>>>> It seems really really strange to me for the same version of a stable |
130 |
>>>> package to be "influenced" by keywording. |
131 |
>>>> Is it a bug or a feature ? |
132 |
>>>> Did I do something wrong ? |
133 |
>>>> |
134 |
>>>> Thanks |
135 |
>>>> Best regards |
136 |
>>>> Mickaël Bucas |
137 |
>>>> |
138 |
>>> |