| 1 |
2018-07-10 12:28 GMT+03:00 Neil Bothwick <neil@××××××××××.uk>: |
| 2 |
> On Tue, 10 Jul 2018 05:08:10 -0400, John Covici wrote: |
| 3 |
> |
| 4 |
>> In my last update which was about June 21 or so, lots of packages were |
| 5 |
>> reinstalled to make python3.6 the default target for python3. I don't |
| 6 |
>> have any targets like that in my make.conf, so it was done -- about |
| 7 |
>> 200 reinstalls. |
| 8 |
> |
| 9 |
> It was a profile change. |
| 10 |
> |
| 11 |
>> Now when I look at my latest update, a lot of them |
| 12 |
>> are going back to 3.5 instead. What is going on here -- are the devs |
| 13 |
>> a bit too hasty or what? |
| 14 |
> |
| 15 |
> There were problems with some packages not being compatible with 3.6. |
| 16 |
> Since you have been running that profile for a while, it is unlikely you |
| 17 |
> are affected, so you can keep the default at 3.6 by adding this |
| 18 |
> to /etc/portage/profile/make.defaults |
| 19 |
> |
| 20 |
> PYTHON_TARGETS="python2_7 -python3_5 python3_6" |
| 21 |
> PYTHON_SINGLE_TARGET="-python3_5 python3_6" |
| 22 |
> |
| 23 |
>> I am on the unstable, but this is rediculous. |
| 24 |
> |
| 25 |
> It's not ridiculous, it's exactly what the testing tree is for, to find |
| 26 |
> problems like this. The testing tree changes quickly, by its very nature, |
| 27 |
> leaving nearly three weeks between updates is probably a bit too long. |
| 28 |
|
| 29 |
The same happened in stable as well. |
Archives