Date: Fri, 7 Apr 2023 16:09:42 +0200 From: Julien Cigar <julien@perdition.city> To: Matthew Seaman <matthew@FreeBSD.org> Cc: questions@freebsd.org Subject: Re: Poudriere and Python FLAVORS Message-ID: <zt6xfastbfa7l6egqxfhhguekeksslhgt3sebhu7cekpklpbow@y5bp6tp7ngjb> In-Reply-To: <f2bc5d0f-4174-a458-119a-b78bcf83f5db@FreeBSD.org> References: <6amrdwe3seijb2qz7xjtbxkrldhkftrrfmsdqh3lopl7e4yx3k@u6bahg4f3s4l> <f2bc5d0f-4174-a458-119a-b78bcf83f5db@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Fri, Apr 07, 2023 at 03:04:13PM +0100, Matthew Seaman wrote: > On 07/04/2023 12:52, Julien Cigar wrote: > > Hello, > > > > I'm building 2023Q2 through Poudriere with: > > DEFAULT_VERSIONS+= python2=2.7 python3=3.11 python=3.11 pgsql=13 php=8.1 > > > > I'm getting tons of "Ignored: Unknown flavor 'py39', possible flavors: > > py311" (see (1)) for my Python ports (I didn't specified any flavor > > @pyxx) > > > > 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? > > Do you have: > > BUILD_ALL_PYTHON_FLAVORS= yes no, I don't remember having read something about this knob.. is it documented somewhere? > > set in a make.conf file anywhere that poudriere could read? ie. somewhere > under /usr/local/etc/poudriere.d ? > > Equivalently some ports have a > > USE_PYTHON= allflavors > > setting which produces the same effect for just that port. There's only > about a dozen ports that do that in the whole tree, but they include some > really commonly used ones like py-setuptools. > > Either of those settings means poudriere will default to building modules > for all python versions from 3.7 to 3.11 that are supported by the module. > > If you only want version 3.11 of some modules, then you can add @3.11 to an > individual port's path in the list you specify, and only that flavour will > be built. > > Note that if a port is not specified explicitly in your list of ports to > build, but is automatically bought in to resolve dependencies for some other > port, then it effectively has the @3.11 thing built in, even if the port has > USE_PYTHON=allflavors set. > > I don't see how you are getting "Unknown flavor 'py39'" though. That means > some port has somehow ended up with a dependency on eg. net/py-pysocks@py39 > which shouldn't happen. Are you using a modified ports tree eg. with > overlaid or locally modified ports? no, it's the pristine clone of the 2023Q2 branch through git > > Cheers, > > Matthew > > > > > > > -- Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEnF27CBNtOraRNmgqCLYqJMpBHmkFAmQwJCYACgkQCLYqJMpB HmmuMA/9GJOR29I34V5Ap2EHcA61rmDo36Qet9U2X2xrMCQH1alayVotMz9eRURB tP+TZzVVG+QThYtcXpzDuDMRMf0ojoZOdhkoV+R4HD9Zu85nhxc0b/r5HWS9fY+x buAJ0keU8PROhUgkyUeUDJqhnfZ0QJ7emz1m9mViTB+Cv1bpdBzf0qgousqOtT/b RYjtLQesNVqrGvPVkkgd7q2w37nMShd7WsaanchXsb0fgEl0b0g+0cHx1R9Kk0Hq tqanXjFJnBTPdBwb/8Cjk0MYS3r4PgXiJYkCOHOvlobMEFnTSBiUg1faVhvxa3M1 vYe9Om6b125VtBsIBxIOLRzjQPOvhLUsg1xj53wMfpvEtXOWdf9vKnoK5zyle92Q 0jzZPhtO1Sg/QDTX9tLAp4RNyhQlpAAlQ2xi9qE5UJXdzUt8Us0+o6Y23kZ4DWkp OlAhEjzLOS27IiII1ki1V7GKaCaVZXAa0c7cPBVKcuwsjJjpffE9Rql60OMsmWVD P3CASyiC80DmR1eGv5fcaItr+YEIe6mq63s74Gg22oOWiYUfJARo25g7kcGmgZqH UggJ46ZkxwCYBMZGQV2sG0PdPst1PiPThX5owC7/O7sdYnIJ380CBAUobgM86YcV 8SrfUUSPKcC05/pwqUWuqicSaspaj5fkUTnyOXSgLp1ThZ71OfU= =doDt -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?zt6xfastbfa7l6egqxfhhguekeksslhgt3sebhu7cekpklpbow>