Should be fixed (was: Why portmaster try to install python 3.6 when I have 3.4 set in /etc/make.conf?)

[Stefan Esser]

Am 10.01.18 um 17:29 schrieb Lev Serebryakov:
> 
>  I have system with pre-FLAVORed ports installed, and try to update
> ports with new version of "portmaster". My "/etc/make.conf" contains:
> 
> DEFAULT_VERSIONS+=      python2=2.7
> DEFAULT_VERSIONS+=      python3=3.4
> DEFAULT_VERSIONS+=      python=3.4
> 
>  But "portmaster -a" try to install python 3.6:
> 
> ===>>> All >> py34-pip-9.0.1 (12/12)
>         ===>>> The devel/py3-pip port moved to devel/py-pip at py36
>         ===>>> Reason: Moved to a flavored, generic, version
> ===>>> Currently installed version: py34-pip-9.0.1
> ===>>> Port directory: /usr/ports/devel/py-pip at py36
> ===>>> Launching 'make checksum' for devel/py-pip at py36 in background
> ===>>> Gathering dependency list for devel/py-pip at py36 from ports
> ===>>> Launching child to install devel/py-setuptools at py36
> ===>>> All >> py34-pip-9.0.1 >> devel/py-setuptools at py36 (13/13)
> ===>>> Port directory: /usr/ports/devel/py-setuptools at py36
> ===>>> Launching 'make checksum' for devel/py-setuptools at py36 in background
> ===>>> Gathering dependency list for devel/py-setuptools at py36 from ports
> ===>>> Launching child to install lang/python36
> ===>>> All >> py34-pip-9.0.1 >> devel/py-setuptools at py36 >>
> lang/python36 (14/14)
> 
>  What do I do wrong?

Please test with the (just committed) portmaster version 3.18_12.

Best regards, STefan