Date: Fri, 7 Apr 2023 09:07:59 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Julien Cigar <julien@perdition.city> Cc: questions@freebsd.org Subject: Re: Poudriere and Python FLAVORS Message-ID: <A4DFBF06-89CF-456E-B6D4-4C2EA46E8141@gromit.dlib.vt.edu> In-Reply-To: <6amrdwe3seijb2qz7xjtbxkrldhkftrrfmsdqh3lopl7e4yx3k@u6bahg4f3s4l> References: <6amrdwe3seijb2qz7xjtbxkrldhkftrrfmsdqh3lopl7e4yx3k@u6bahg4f3s4l>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 7, 2023, at 7:52 AM, Julien Cigar <julien@perdition.city> wrote: > Hello,=20 >=20 > I'm building 2023Q2 through Poudriere with: > DEFAULT_VERSIONS+=3D python2=3D2.7 python3=3D3.11 python=3D3.11 = pgsql=3D13 php=3D8.1 >=20 > I'm getting tons of "Ignored: Unknown flavor 'py39', possible flavors: > py311" (see (1)) for my Python ports (I didn't specified any flavor=20 > @pyxx)=20 >=20 > I don't understand why: > - Why does Poudriere tries to build @py39 flavor by default when 3.11 = is the > default? > - Why py39 flavor is unknown althoug the default Python version for > 2023Q2 is 3.9? >=20 > Any idea ? :) I don't know whether this is the issue in your case, but I found when = setting the default Python flavour to 3.10 myself I would get the same = problems: ports would not build due to an "unknown" flavour. I discovered that in some cases, "USES=3D ... python:<version range>" in = a port Makefile would make it impossible to build with the default = flavour I had set in /etc/make.conf. A case in point: I wanted to build = sysutils/py-salt via Poudriere with a default Python flavour of 3.10. = It failed. Looking in the Makefile, I saw "USES=3D cpe python:3.6-3.9". = Most other ports tend to have "... python:3.6+", but this one said it = only worked with 3.6 to 3.9. Hence, trying to build it with 3.10 = failed. I knew that version of py-salt would build under 3.10, so ultimately = (after carrying my own local change to the Makefile for a while) = submitted a Bugzilla asking for it to be changed to "USES=3D cpe = python:3.6-3.10", which solved the building problem. So, you may have some similar Python ports or dependent ports that = specify they aren't compatible with Python 3.11, and that is causing the = warnings and errors. Cheers, Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A4DFBF06-89CF-456E-B6D4-4C2EA46E8141>