| 1 |
On Thu, Nov 30 2017, Marc Joliet wrote: |
| 2 |
|
| 3 |
> Am Mittwoch, 29. November 2017, 22:29:59 CET schrieb allan gottlieb: |
| 4 |
>> On Wed, Nov 29 2017, Alan McKinnon wrote: |
| 5 |
> [...] |
| 6 |
>> >> Both 6430 and 7450 have the following content in |
| 7 |
>> >> /etc/portage/package.use/systemd-cron |
| 8 |
>> >> |
| 9 |
>> >> # systemd-cron needs PYTHON_SINGLE_TARGET = 3.x. |
| 10 |
>> >> sys-process/systemd-cron python_single_target_python3_4 |
| 11 |
> [...] |
| 12 |
> |
| 13 |
> Isn't this the problem? PYTHON_TARGETS has switched to python3_5 but that's |
| 14 |
> in conflict with the above (or should be, IIUC). Remove that or change it to |
| 15 |
> "python_single_target_python3_5" (I would remove it; according to my git log, |
| 16 |
> I removed a similar line in August when I noticed that the profiles already |
| 17 |
> default to Python 3.x in $PYTHON_SINGLE_TARGETS). |
| 18 |
> |
| 19 |
> I admit, though, that I am surprised that one machine can apparently still go |
| 20 |
> through with the upgrade. Does it also have systemd-cron installed? Or maybe |
| 21 |
> I'm forgetting or missing something... |
| 22 |
> |
| 23 |
> HTH |
| 24 |
|
| 25 |
Bingo! |
| 26 |
|
| 27 |
1. The 6430 does not have systemd-cron so was unaffected |
| 28 |
|
| 29 |
2. I commented out the package.use line for systemd-cron in the 7450, |
| 30 |
which does use systemd-cron, and it seems willing to do the update |
| 31 |
world. (The 6430 is a backup, I will do the update on it first.) |
| 32 |
|
| 33 |
thank you very much. |
| 34 |
allan |
Archives