1 |
Am Mittwoch, 29. November 2017, 22:29:59 CET schrieb allan gottlieb: |
2 |
> On Wed, Nov 29 2017, Alan McKinnon wrote: |
3 |
[...] |
4 |
> >> Both 6430 and 7450 have the following content in |
5 |
> >> /etc/portage/package.use/systemd-cron |
6 |
> >> |
7 |
> >> # systemd-cron needs PYTHON_SINGLE_TARGET = 3.x. |
8 |
> >> sys-process/systemd-cron python_single_target_python3_4 |
9 |
[...] |
10 |
|
11 |
Isn't this the problem? PYTHON_TARGETS has switched to python3_5 but that's |
12 |
in conflict with the above (or should be, IIUC). Remove that or change it to |
13 |
"python_single_target_python3_5" (I would remove it; according to my git log, |
14 |
I removed a similar line in August when I noticed that the profiles already |
15 |
default to Python 3.x in $PYTHON_SINGLE_TARGETS). |
16 |
|
17 |
I admit, though, that I am surprised that one machine can apparently still go |
18 |
through with the upgrade. Does it also have systemd-cron installed? Or maybe |
19 |
I'm forgetting or missing something... |
20 |
|
21 |
HTH |
22 |
-- |
23 |
Marc Joliet |
24 |
-- |
25 |
"People who think they know everything really annoy those of us who know we |
26 |
don't" - Bjarne Stroustrup |