On Tue, 10 Jul 2018 05:08:10 -0400, John Covici wrote: > In my last update which was about June 21 or so, lots of packages were > reinstalled to make python3.6 the default target for python3. I don't > have any targets like that in my make.conf, so it was done -- about > 200 reinstalls.
It was a profile change. > Now when I look at my latest update, a lot of them > are going back to 3.5 instead. What is going on here -- are the devs > a bit too hasty or what? There were problems with some packages not being compatible with 3.6. Since you have been running that profile for a while, it is unlikely you are affected, so you can keep the default at 3.6 by adding this to /etc/portage/profile/make.defaults PYTHON_TARGETS="python2_7 -python3_5 python3_6" PYTHON_SINGLE_TARGET="-python3_5 python3_6" > I am on the unstable, but this is rediculous. It's not ridiculous, it's exactly what the testing tree is for, to find problems like this. The testing tree changes quickly, by its very nature, leaving nearly three weeks between updates is probably a bit too long. -- Neil Bothwick We never really grow up; we only learn how to act in public.
pgpBB0GxIq7Ep.pgp
Description: OpenPGP digital signature
