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