From Newsgroup: muc.lists.freebsd.ports

Hello.

I'm looking for help on how to keep using Salt.

Recap:
_ sysutils/py-satl requires Python 3.11 and is marked broken with any
newer version;
_ 2026Q3 moves Python default to 3.12.

Since I build ports with Poudriere, I was hoping to be able to keep
building Salt with Python 3.11.
However I was not able to find a way.

Is this possible?
How do I do this?

Without a working Salt, 2026Q3 is simply a no go for us.

bye & Thanks
av.

P.S.
I'm aware of #296290 and read it all, but still it does not answer my question.


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports


--w5lLJdvh1h7gWY82
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Andrea,

Short answer: the port is going to move to Salt 3008. There's no
maintainable way to keep 3006 alive on 3.12+, the breakage is the
vendored Tornado calling ssl.match_hostname(), which was removed in
Python 3.12, and upstream only fixed that in 3007. So 3006 is a dead
end and I don't want to carry it indefinitely.

That said, until the 3008 port lands you can keep building 3006 on
Python 3.11 in Poudriere. The BROKEN marker is keyed on PYTHON_REL >=3D
31200, so building against 3.11 sidesteps it. Scope it to a dedicated
set so only that set drops to 3.11

lang/python311 is still in the tree on 2026Q3, so the dependency chain resolves. Treat this as a bridge, not a permanent solution.

Now the part you should know before you rely on 3008, because it
affects FreeBSD users specifically: 3008 moved a bunch of modules out
into separate salt-extensions. The zfs state is gone (moved to
saltext-zfs), and sysrc/freebsdservice currently have no upstream home
at all, saltext-freebsd doesn't exist yet. Alan and Fabian already hit
the missing ZFS state in testing, and Delta had to vendor the old
extensions by hand. So if your setup leans on ZFS states or FreeBSD service/sysrc management, plan for that gap.

There's a working 3008.1 patch attached to the PR (#296290). Since you
said you depend on Salt on FreeBSD and are willing to help, testing
that patch against your own states would be genuinely useful,
especially anything touching zfs/sysrc/service. That's exactly the
feedback that'll tell me whether an in-place 3008 update is enough or
whether we need to sort out the FreeBSD extensions first.

K.

On 07/12, Andrea Venturoli wrote:

Hello.
=20
I'm looking for help on how to keep using Salt.
=20
Recap:
_ sysutils/py-satl requires Python 3.11 and is marked broken with any new=

er

version;
_ 2026Q3 moves Python default to 3.12.
=20
Since I build ports with Poudriere, I was hoping to be able to keep build=

ing

Salt with Python 3.11.
However I was not able to find a way.
=20
Is this possible?
How do I do this?
=20
Without a working Salt, 2026Q3 is simply a no go for us.
=20
bye & Thanks
av.
=20
P.S.
I'm aware of #296290 and read it all, but still it does not answer my question.

--w5lLJdvh1h7gWY82
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQFPBAABCAA5FiEEJCHRFhEAQujKni1pDyI9/LMCykUFAmpUjCIbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwzAAoJEA8iPfyzAspF2LkIAJg6XMkOAfWzZGh13SSg 6Tq/4NuxFoyxVpLANXV88HOsNfeECoF8+v3CByv+CJ2AVX5kibfs9qyLcF/Flxyi BD1sobiTG++k9Mdh4CtR4yPgwY93WJoMClNKqdb6BqrhmQ6PTB1ZPFvvVIS88dCh FBg68+wxVa2n41vK9e7OjKipBByctztxRAD0lkqE5AFiCUOLaqgyVDXFqc+Xs71+ stW/6Fr9FxsXndQhauoiqFbsbONDaxlpHqHkV9qcCEkiC2H7rwSGHluB/um5fdPq j4RZocnaeS5MUu2hNEzyL2BD7k6B/9Vtc/7KN49QxHHVsk3l3Oo9gNbzIXLp0sna
/ZU=
=7mxs
-----END PGP SIGNATURE-----

--w5lLJdvh1h7gWY82--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

This is a multi-part message in MIME format. --------------5s7bMRFuIaecz0q9fE0mr3i3
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit

Dear Kirill,

I started some time to switch the administration to salt (not rolled
out, but I have virtual machines ready for testing).
I use ZFS and sysrc, so mostly what you asked for.

I applied the patch to 3008.1 but if I try to build it with poudriere I get:

[00:00:02] Ignoring
devel/py-more-itertools@py314 | py314-more-itertools-11.1.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-gitpython@py314 | py314-gitpython-3.1.50
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-looseversion@py314 | py314-looseversion-1.3.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-jmespath@py314 | py314-jmespath-1.1.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-cffi@py314 | py314-cffi-2.1.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-importlib-metadata@py314 | py314-importlib-metadata-8.7.1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-Jinja2@py314 | py314-Jinja2-3.1.6
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-opentelemetry-api@py314 | py314-opentelemetry-api-1.43.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-jaraco.functools@py314 | py314-jaraco.functools-4.5.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-jaraco.context@py314 | py314-jaraco.context-6.1.2
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-frozenlist@py314 | py314-frozenlist-1.8.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-pycparser@py314 | py314-pycparser-2.23
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-jaraco.text@py314 | py314-jaraco.text-4.2.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-msgpack@py314 | py314-msgpack-1.2.1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-timelib@py314 | py314-timelib-0.3.0_1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-python-dateutil@py314 | py314-python-dateutil-2.9.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-pyasn1@py314 | py314-pyasn1-0.6.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
net/py-libcloud@py314 | py314-libcloud-3.8.0_1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
dns/py-idna@py314 | py314-idna-3.18
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-setproctitle@py314 | py314-setproctitle-1.3.7
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Skipping
sysutils/py-salt | py314-salt-3008.1,1
: Dependent port
devel/py-looseversion@py314 | py314-looseversion-1.3.0
ignored
[00:00:02] Ignoring
devel/py-pyyaml@py314 | py314-pyyaml-6.0.3
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-xxhash@py314 | py314-xxhash-3.8.1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-opentelemetry-sdk@py314 | py314-opentelemetry-sdk-1.43.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-zipp@py314 | py314-zipp-3.23.1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
security/py-gnupg@py314 | py314-gnupg-3.1.1_1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
net/py-pyzmq@py314 | py314-pyzmq-27.1.0_1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
security/py-pycryptodomex@py314 | py314-pycryptodomex-3.23.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
security/py-truststore@py314 | py314-truststore-0.10.4
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-opentelemetry-exporter-otlp-proto-http@py314 | py314-opentelemetry-exporter-otlp-proto-http-1.43.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
sysutils/py-distro@py314 | py314-distro-1.9.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
sysutils/py-croniter@py314 | py314-croniter-6.2.2
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
textproc/py-markupsafe@py314 | py314-markupsafe-3.0.3
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
sysutils/py-filelock@py314 | py314-filelock-3.29.6
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
sysutils/py-psutil@py314 | py314-psutil-7.2.2_1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
security/py-cryptography@py314 | py314-cryptography-48.0.1,1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
www/py-tornado@py314 | py314-tornado-6.5.7
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
www/py-requests@py314 | py314-requests-2.34.2
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
security/py-pyopenssl@py314 | py314-pyopenssl-26.2.0,1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
net/py-urllib3@py314 | py314-urllib3-2.7.0,1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-virtualenv@py314 | py314-virtualenv-21.2.3
: Unknown flavor 'py314', possible flavors: py312

Maybe some more ports will need flavor support to get that working?


Thanks
Matthias

Am 13.07.26 um 08:56 schrieb Kirill Ponomarev:

Hi Andrea,

Short answer: the port is going to move to Salt 3008. There's no
maintainable way to keep 3006 alive on 3.12+, the breakage is the
vendored Tornado calling ssl.match_hostname(), which was removed in
Python 3.12, and upstream only fixed that in 3007. So 3006 is a dead
end and I don't want to carry it indefinitely.

That said, until the 3008 port lands you can keep building 3006 on
Python 3.11 in Poudriere. The BROKEN marker is keyed on PYTHON_REL >=
31200, so building against 3.11 sidesteps it. Scope it to a dedicated
set so only that set drops to 3.11

lang/python311 is still in the tree on 2026Q3, so the dependency chain resolves. Treat this as a bridge, not a permanent solution.

Now the part you should know before you rely on 3008, because it
affects FreeBSD users specifically: 3008 moved a bunch of modules out
into separate salt-extensions. The zfs state is gone (moved to
saltext-zfs), and sysrc/freebsdservice currently have no upstream home
at all, saltext-freebsd doesn't exist yet. Alan and Fabian already hit
the missing ZFS state in testing, and Delta had to vendor the old
extensions by hand. So if your setup leans on ZFS states or FreeBSD service/sysrc management, plan for that gap.

There's a working 3008.1 patch attached to the PR (#296290). Since you
said you depend on Salt on FreeBSD and are willing to help, testing
that patch against your own states would be genuinely useful,
especially anything touching zfs/sysrc/service. That's exactly the
feedback that'll tell me whether an in-place 3008 update is enough or
whether we need to sort out the FreeBSD extensions first.

K.

On 07/12, Andrea Venturoli wrote:

Hello.

I'm looking for help on how to keep using Salt.

Recap:
_ sysutils/py-satl requires Python 3.11 and is marked broken with any newer >> version;
_ 2026Q3 moves Python default to 3.12.

Since I build ports with Poudriere, I was hoping to be able to keep building >> Salt with Python 3.11.
However I was not able to find a way.

Is this possible?
How do I do this?

Without a working Salt, 2026Q3 is simply a no go for us.

bye & Thanks
av.

P.S.
I'm aware of #296290 and read it all, but still it does not answer my
question.

--------------5s7bMRFuIaecz0q9fE0mr3i3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Kirill,</p>
<p>I started some time to switch the administration to salt (not
rolled out, but I have virtual machines ready for testing).<br>
I use ZFS and sysrc, so mostly what you asked for.</p>
<p>I applied the patch to 3008.1 but if I try to build it with
poudriere I get:<br>
</p>
<div style="font-family: monospace; white-space: pre;"><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-more-itertools@py314 | py314-more-itertools-11.1.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-gitpython@py314 | py314-gitpython-3.1.50</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-looseversion@py314 | py314-looseversion-1.3.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-jmespath@py314 | py314-jmespath-1.1.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-cffi@py314 | py314-cffi-2.1.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-importlib-metadata@py314 | py314-importlib-metadata-8.7.1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-Jinja2@py314 | py314-Jinja2-3.1.6</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-opentelemetry-api@py314 | py314-opentelemetry-api-1.43.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-jaraco.functools@py314 | py314-jaraco.functools-4.5.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-jaraco.context@py314 | py314-jaraco.context-6.1.2</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-frozenlist@py314 | py314-frozenlist-1.8.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-pycparser@py314 | py314-pycparser-2.23</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-jaraco.text@py314 | py314-jaraco.text-4.2.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-msgpack@py314 | py314-msgpack-1.2.1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-timelib@py314 | py314-timelib-0.3.0_1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-python-dateutil@py314 | py314-python-dateutil-2.9.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-pyasn1@py314 | py314-pyasn1-0.6.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">net/py-libcloud@py314 | py314-libcloud-3.8.0_1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">dns/py-idna@py314 | py314-idna-3.18</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-setproctitle@py314 | py314-setproctitle-1.3.7</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div
style="display: inline;color: rgb(235, 203, 139);font-weight: bold;">[00:00:02] Skipping </div> <div
style="display: inline;color: rgb(136, 192, 208);">sysutils/py-salt | py314-salt-3008.1,1</div><div
style="display: inline;color: rgb(235, 203, 139);font-weight: bold;">: Dependent port </div><div
style="display: inline;color: rgb(136, 192, 208);">devel/py-looseversion@py314 | py314-looseversion-1.3.0</div><div
style="display: inline;color: rgb(235, 203, 139);font-weight: bold;"> ignored</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-pyyaml@py314 | py314-pyyaml-6.0.3</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-xxhash@py314 | py314-xxhash-3.8.1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-opentelemetry-sdk@py314 | py314-opentelemetry-sdk-1.43.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-zipp@py314 | py314-zipp-3.23.1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">security/py-gnupg@py314 | py314-gnupg-3.1.1_1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">net/py-pyzmq@py314 | py314-pyzmq-27.1.0_1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">security/py-pycryptodomex@py314 | py314-pycryptodomex-3.23.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">security/py-truststore@py314 | py314-truststore-0.10.4</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-opentelemetry-exporter-otlp-proto-http@py314 | py314-opentelemetry-exporter-otlp-proto-http-1.43.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">sysutils/py-distro@py314 | py314-distro-1.9.0</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">sysutils/py-croniter@py314 | py314-croniter-6.2.2</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">textproc/py-markupsafe@py314 | py314-markupsafe-3.0.3</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">sysutils/py-filelock@py314 | py314-filelock-3.29.6</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">sysutils/py-psutil@py314 | py314-psutil-7.2.2_1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">security/py-cryptography@py314 | py314-cryptography-48.0.1,1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">www/py-tornado@py314 | py314-tornado-6.5.7</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">www/py-requests@py314 | py314-requests-2.34.2</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">security/py-pyopenssl@py314 | py314-pyopenssl-26.2.0,1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">net/py-urllib3@py314 | py314-urllib3-2.7.0,1</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312</div>
<div style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">[00:00:02] Ignoring </div> <div
style="display: inline;color: rgb(136, 192, 208);">devel/py-virtualenv@py314 | py314-virtualenv-21.2.3</div><div
style="display: inline;color: rgb(59, 66, 82);font-weight: bold;">: Unknown flavor 'py314', possible flavors: py312

</div><p style="display: inline; color: rgb(59, 66, 82);">Maybe some more ports will need flavor support to get that working?</p></div>
<p><br>
Thanks<br>
Matthias</p>
<div class="moz-cite-prefix">Am 13.07.26 um 08:56 schrieb Kirill
Ponomarev:<br>
</div>
<blockquote type="cite" cite="mid:alSMIuyOUs8fRq5D@krion.cc">
<pre wrap="" class="moz-quote-pre">Hi Andrea,

Short answer: the port is going to move to Salt 3008. There's no
maintainable way to keep 3006 alive on 3.12+, the breakage is the
vendored Tornado calling ssl.match_hostname(), which was removed in
Python 3.12, and upstream only fixed that in 3007. So 3006 is a dead
end and I don't want to carry it indefinitely.

That said, until the 3008 port lands you can keep building 3006 on
Python 3.11 in Poudriere. The BROKEN marker is keyed on PYTHON_REL &gt;=
31200, so building against 3.11 sidesteps it. Scope it to a dedicated
set so only that set drops to 3.11

lang/python311 is still in the tree on 2026Q3, so the dependency chain resolves. Treat this as a bridge, not a permanent solution.

Now the part you should know before you rely on 3008, because it
affects FreeBSD users specifically: 3008 moved a bunch of modules out
into separate salt-extensions. The zfs state is gone (moved to
saltext-zfs), and sysrc/freebsdservice currently have no upstream home
at all, saltext-freebsd doesn't exist yet. Alan and Fabian already hit
the missing ZFS state in testing, and Delta had to vendor the old
extensions by hand. So if your setup leans on ZFS states or FreeBSD service/sysrc management, plan for that gap.

There's a working 3008.1 patch attached to the PR (#296290). Since you
said you depend on Salt on FreeBSD and are willing to help, testing
that patch against your own states would be genuinely useful,
especially anything touching zfs/sysrc/service. That's exactly the
feedback that'll tell me whether an in-place 3008 update is enough or
whether we need to sort out the FreeBSD extensions first.

K.

On 07/12, Andrea Venturoli wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">Hello.

I'm looking for help on how to keep using Salt.

Recap:
_ sysutils/py-satl requires Python 3.11 and is marked broken with any newer version;
_ 2026Q3 moves Python default to 3.12.

Since I build ports with Poudriere, I was hoping to be able to keep building Salt with Python 3.11.
However I was not able to find a way.

Is this possible?
How do I do this?

Without a working Salt, 2026Q3 is simply a no go for us.

bye &amp; Thanks
av.

P.S.
I'm aware of #296290 and read it all, but still it does not answer my
question.
</pre>
</blockquote>
</blockquote>
</body>
</html>

--------------5s7bMRFuIaecz0q9fE0mr3i3--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

--7BjBrRGzFqYyjzdG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Matthias,

The issue is just the default python version your poudriere build is
using. The fix is to tell poudriere to build pith Python 3.14 as the
default. Add to your Poudriere make.conf:
# /usr/local/etc/poudriere.d/make.conf or a set-specific <set>-make.conf DEFAULT_VERSIONS+=3D python=3D3.14

If you don't want to flip your entire poudriere over to 3.14, scope it
to a dedicated set (-z salt314) and put the DEFAULT_VERSIONS line in salt314-make.conf instead of the global one. Since you run zfs and
sysrc, which is exactly the coverage I was hoping for, once it builds,
please try a real state.apply that touches zfs/sysrc/service and let
me know how it goes. Those are the modules 3008 moved out into
separate salt-extensions so that's the part I'm most unsure about
before committing to the in-place 3008 update.

On 07/13, Matthias Fechner wrote:

Dear Kirill,
=20
I started some time to switch the administration to salt (not rolled out,
but I have virtual machines ready for testing).
I use ZFS and sysrc, so mostly what you asked for.
=20
I applied the patch to 3008.1 but if I try to build it with poudriere I g=

et:

=20
[00:00:02] Ignoring
devel/py-more-itertools@py314 | py314-more-itertools-11.1.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-gitpython@py314 | py314-gitpython-3.1.50
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-looseversion@py314 | py314-looseversion-1.3.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-jmespath@py314 | py314-jmespath-1.1.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-cffi@py314 | py314-cffi-2.1.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-importlib-metadata@py314 | py314-importlib-metadata-8.7.1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-Jinja2@py314 | py314-Jinja2-3.1.6
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-opentelemetry-api@py314 | py314-opentelemetry-api-1.43.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-jaraco.functools@py314 | py314-jaraco.functools-4.5.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-jaraco.context@py314 | py314-jaraco.context-6.1.2
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-frozenlist@py314 | py314-frozenlist-1.8.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-pycparser@py314 | py314-pycparser-2.23
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-jaraco.text@py314 | py314-jaraco.text-4.2.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-msgpack@py314 | py314-msgpack-1.2.1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-timelib@py314 | py314-timelib-0.3.0_1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-python-dateutil@py314 | py314-python-dateutil-2.9.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-pyasn1@py314 | py314-pyasn1-0.6.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
net/py-libcloud@py314 | py314-libcloud-3.8.0_1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
dns/py-idna@py314 | py314-idna-3.18
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-setproctitle@py314 | py314-setproctitle-1.3.7
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Skipping
sysutils/py-salt | py314-salt-3008.1,1
: Dependent port
devel/py-looseversion@py314 | py314-looseversion-1.3.0
ignored
[00:00:02] Ignoring
devel/py-pyyaml@py314 | py314-pyyaml-6.0.3
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-xxhash@py314 | py314-xxhash-3.8.1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-opentelemetry-sdk@py314 | py314-opentelemetry-sdk-1.43.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-zipp@py314 | py314-zipp-3.23.1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
security/py-gnupg@py314 | py314-gnupg-3.1.1_1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
net/py-pyzmq@py314 | py314-pyzmq-27.1.0_1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
security/py-pycryptodomex@py314 | py314-pycryptodomex-3.23.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
security/py-truststore@py314 | py314-truststore-0.10.4
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-opentelemetry-exporter-otlp-proto-http@py314 | py314-opentelemetry-exporter-otlp-proto-http-1.43.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
sysutils/py-distro@py314 | py314-distro-1.9.0
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
sysutils/py-croniter@py314 | py314-croniter-6.2.2
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
textproc/py-markupsafe@py314 | py314-markupsafe-3.0.3
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
sysutils/py-filelock@py314 | py314-filelock-3.29.6
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
sysutils/py-psutil@py314 | py314-psutil-7.2.2_1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
security/py-cryptography@py314 | py314-cryptography-48.0.1,1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
www/py-tornado@py314 | py314-tornado-6.5.7
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
www/py-requests@py314 | py314-requests-2.34.2
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
security/py-pyopenssl@py314 | py314-pyopenssl-26.2.0,1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
net/py-urllib3@py314 | py314-urllib3-2.7.0,1
: Unknown flavor 'py314', possible flavors: py312
[00:00:02] Ignoring
devel/py-virtualenv@py314 | py314-virtualenv-21.2.3
: Unknown flavor 'py314', possible flavors: py312
=20
Maybe some more ports will need flavor support to get that working?
=20
=20
Thanks
Matthias
=20
Am 13.07.26 um 08:56 schrieb Kirill Ponomarev:

Hi Andrea,
=20
Short answer: the port is going to move to Salt 3008. There's no maintainable way to keep 3006 alive on 3.12+, the breakage is the
vendored Tornado calling ssl.match_hostname(), which was removed in
Python 3.12, and upstream only fixed that in 3007. So 3006 is a dead
end and I don't want to carry it indefinitely.
=20
That said, until the 3008 port lands you can keep building 3006 on
Python 3.11 in Poudriere. The BROKEN marker is keyed on PYTHON_REL >=3D 31200, so building against 3.11 sidesteps it. Scope it to a dedicated
set so only that set drops to 3.11
=20
lang/python311 is still in the tree on 2026Q3, so the dependency chain resolves. Treat this as a bridge, not a permanent solution.
=20
Now the part you should know before you rely on 3008, because it
affects FreeBSD users specifically: 3008 moved a bunch of modules out
into separate salt-extensions. The zfs state is gone (moved to saltext-zfs), and sysrc/freebsdservice currently have no upstream home
at all, saltext-freebsd doesn't exist yet. Alan and Fabian already hit
the missing ZFS state in testing, and Delta had to vendor the old extensions by hand. So if your setup leans on ZFS states or FreeBSD service/sysrc management, plan for that gap.
=20
There's a working 3008.1 patch attached to the PR (#296290). Since you
said you depend on Salt on FreeBSD and are willing to help, testing
that patch against your own states would be genuinely useful,
especially anything touching zfs/sysrc/service. That's exactly the
feedback that'll tell me whether an in-place 3008 update is enough or whether we need to sort out the FreeBSD extensions first.
=20
K.
=20
On 07/12, Andrea Venturoli wrote:

Hello.
=20
I'm looking for help on how to keep using Salt.
=20
Recap:
_ sysutils/py-satl requires Python 3.11 and is marked broken with any=

newer

version;
_ 2026Q3 moves Python default to 3.12.
=20
Since I build ports with Poudriere, I was hoping to be able to keep b=

uilding

Salt with Python 3.11.
However I was not able to find a way.
=20
Is this possible?
How do I do this?
=20
Without a working Salt, 2026Q3 is simply a no go for us.
=20
bye & Thanks
av.
=20
P.S.
I'm aware of #296290 and read it all, but still it does not answer my question.

--7BjBrRGzFqYyjzdG
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQFPBAABCAA5FiEEJCHRFhEAQujKni1pDyI9/LMCykUFAmpUnxgbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwzAAoJEA8iPfyzAspFXtcH/RQ7z9CX+SiuYJgLYFO7 BqrjrXhkIAxE+pcaOlRBbm3f+9iAWmDtVjzh2QaAg8M99yPGBolgbBd5gjizZPPY GfS0D9LUWJYW0In5jCCf93cp5OjVRx0WTJDTbRLMjPVaKfOSrO5UYZtdsqfkPt0e twSSlDdvsRox1Bgu0/FdTj3IpuDZ/lJwlvI5GAxHdXsqfqOmZkvM8LThBxn8eq+I i6hHzaPc7wN6T+HM9G3LjBDHH2bK9yVFxAoiAiv4lMzh8I5AIdnqaQRXwDlPp6rM P1G616hDh+r6p7VImWa8j73j3ofGqhFMaiSKIUahGhMgvzRXbM3ibk0+fDSQ946E
LMk=
=VR8K
-----END PGP SIGNATURE-----

--7BjBrRGzFqYyjzdG--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On 7/13/26 08:56, Kirill Ponomarev wrote:

Hi Andrea,

Hello and thanks for answering.

That said, until the 3008 port lands you can keep building 3006 on
Python 3.11 in Poudriere. The BROKEN marker is keyed on PYTHON_REL >=
31200, so building against 3.11 sidesteps it. Scope it to a dedicated
set so only that set drops to 3.11

I tried, but I didn't succeed. This is probably ignorance on my part.
So I was asking: how do I do this exactly?
I tried "poudriere ... sysutils/py-salt@py311" and other commands, but
they all failed in some way.

There's a working 3008.1 patch attached to the PR (#296290). Since you
said you depend on Salt on FreeBSD and are willing to help, testing
that patch against your own states would be genuinely useful,
especially anything touching zfs/sysrc/service. That's exactly the
feedback that'll tell me whether an in-place 3008 update is enough or
whether we need to sort out the FreeBSD extensions first.

I will ASAP, but now I'd like to have a working 3006.

BTW, if 3008 requires Python 3.14, which isn't the default, I think I'll
get stuck on the same problem I have now with 3006/3.11 :(


bye & Thanks
av.


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On 7/12/26 20:10, Edward Sanford Sutton, III wrote:

Hello.

From /usr/ports/UPDATING:20260624 but with a presentation of applying
it to all poudriere builds you can run the following command:

echo "DEFAULT_VERSIONS+= python=3.11">>/usr/local/etc/poudriere.d/make.conf

So you are suggest I use Python 3.11 globally?
Isn't it possible to just use it for Salt (and of course its dependencies)? Can't two version of Python coexhist side by side on the same machine?

bye & Thanks
av.



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

--Oatg7GFSH7/ockSo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 07/13, Andrea Venturoli wrote:

On 7/13/26 08:56, Kirill Ponomarev wrote:

Hi Andrea,

=20
Hello and thanks for answering.
=20
=20
=20

That said, until the 3008 port lands you can keep building 3006 on
Python 3.11 in Poudriere. The BROKEN marker is keyed on PYTHON_REL >=3D 31200, so building against 3.11 sidesteps it. Scope it to a dedicated
set so only that set drops to 3.11

=20
I tried, but I didn't succeed. This is probably ignorance on my part.
So I was asking: how do I do this exactly?
I tried "poudriere ... sysutils/py-salt@py311" and other commands, but th=

ey

all failed in some way.

=20
You have to change the default for the build:

Create a set-specific make.conf (eg salt311):
# /usr/local/etc/poudriere.d/salt311-make.conf
DEFAULT_VERSIONS+=3D python=3D3.11

Build, passing the set with -z and no @flavor
poudriere bulk -j <yourjail> -p <yourtree> -z salt311 sysutils/py-salt

You can use that set as its own pkg repo eg.
=20

There's a working 3008.1 patch attached to the PR (#296290). Since you
said you depend on Salt on FreeBSD and are willing to help, testing
that patch against your own states would be genuinely useful,
especially anything touching zfs/sysrc/service. That's exactly the
feedback that'll tell me whether an in-place 3008 update is enough or whether we need to sort out the FreeBSD extensions first.

=20
I will ASAP, but now I'd like to have a working 3006.
=20
BTW, if 3008 requires Python 3.14, which isn't the default, I think I'll =

get

stuck on the same problem I have now with 3006/3.11 :(
=20
=20
bye & Thanks
av.
=20

--Oatg7GFSH7/ockSo
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQFPBAABCAA5FiEEJCHRFhEAQujKni1pDyI9/LMCykUFAmpUpsUbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwzAAoJEA8iPfyzAspF2UAIAKbL0DGFNde+cMV5JTRq 6X7fyMIamQW3Qv4vPkKmGJZdcDWpw2P8Gjss2LMbkCypLmnMCP+db77Nh+JfAJ5t iz+2p0VGVljwTuDAJ+5vFAyq+CCtgHP8Z3wHPZHEQ6j0ecI2RiLybPQYCqSqFtwW VXg0VlmwN7DmLjk8GmDlZVnkExUhw/noZHcmIavI6VGjtj9by4vTKsTtv6R9Lma1 o1US5/HkafRS0yi7+RAm/B32AQ2D3Ak8LXUoP9axHDDznu+mfNfdc/woJCyB9Vqc QngYHoUFdWoYzbMkpC0564uqq2Z9QqwXTOMVt3HElFBv3BByJZTPyWdAr8JIb46s
TsM=
=unim
-----END PGP SIGNATURE-----

--Oatg7GFSH7/ockSo--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Mon, 13 Jul 2026 10:33:37 +0200 Andrea Venturoli wrote:

On 7/13/26 08:56, Kirill Ponomarev wrote:

Hi Andrea,

Hello and thanks for answering.

That said, until the 3008 port lands you can keep building 3006 on
Python 3.11 in Poudriere. The BROKEN marker is keyed on PYTHON_REL >=
31200, so building against 3.11 sidesteps it. Scope it to a dedicated
set so only that set drops to 3.11

I tried, but I didn't succeed. This is probably ignorance on my part.
So I was asking: how do I do this exactly?
I tried "poudriere ... sysutils/py-salt@py311" and other commands, but
they all failed in some way.

In sysutils/py-salt/Makefile line 38, replace "python" with "python:3.11".


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

--xsqQjfjBrtJYVyTY
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 07/13, Matthias Fechner wrote:

Hi Kirill,
=20
Am 13.07.26 um 10:17 schrieb Kirill Ponomarev:

The issue is just the default python version your poudriere build is
using. The fix is to tell poudriere to build pith Python 3.14 as the default. Add to your Poudriere make.conf:
# /usr/local/etc/poudriere.d/make.conf or a set-specific <set>-make.conf DEFAULT_VERSIONS+=3D python=3D3.14
=20
If you don't want to flip your entire poudriere over to 3.14, scope it
to a dedicated set (-z salt314) and put the DEFAULT_VERSIONS line in salt314-make.conf instead of the global one. Since you run zfs and
sysrc, which is exactly the coverage I was hoping for, once it builds, please try a real state.apply that touches zfs/sysrc/service and let
me know how it goes. Those are the modules 3008 moved out into
separate salt-extensions so that's the part I'm most unsure about
before committing to the in-place 3008 update.

=20
thanks, after rust is compiled ;) I see another error.
Here the build log: https://pkg.fechner.net/build.html?mastername=3D150amd64-gitlab-salt314&b=

uild=3D2026-07-13_16h10m35s

=20
Problem is currently:=A0 =A0 =A0www/py-aiohttp@py314
=20
Is that=A0 maybe not compatible with python 3.14?

www/py-aiohttp is not a dependency of salt, not in the 3008
RUN_DEPENDS, and nothing in salt's dependency chain. It's building
because your set is 150amd64-gitlab-salt314, so it's coming from the
gitlab side of the bulk, not from salt.

K.

--xsqQjfjBrtJYVyTY
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQFPBAABCAA5FiEEJCHRFhEAQujKni1pDyI9/LMCykUFAmpVB4UbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwzAAoJEA8iPfyzAspFOtgH/jN9ecnKmda9zvQizenH mSy56hN9N6bAtEs4GXydO0m9ehJ99YjbRs8c+3DyrVf3ffz+hMc3CG+73kfUXvJN m5pJ8xF1Rh2IMvIAWr3soVuFWAxtrkyzEDJ14RmRwtMJhgsqPBIux9APB9yNU0gx 2UpthjklyjASzZppcl0tcV15SyTcZmgDhFJCJ7CTmB0gHWRl0IxNoKQdUmswTSB9 5tA2uppYa1X6iynH6lV8PVKsV8k2TjIkngwpb1nLSP3KVF1T2DbYG8NxRIDYGG9c jKCW9PDNdihoXGeYb47KJr27V6FyTgfm5nt5jDqZ1iY++ChI9371asi4utIe/EVt
YNA=
=3p+c
-----END PGP SIGNATURE-----

--xsqQjfjBrtJYVyTY--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

This is a multi-part message in MIME format. --------------f325r6LHLotDw65fNg9d67uL
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit

Am 13.07.26 um 17:43 schrieb Kirill Ponomarev:

www/py-aiohttp is not a dependency of salt, not in the 3008
RUN_DEPENDS, and nothing in salt's dependency chain. It's building
because your set is 150amd64-gitlab-salt314, so it's coming from the
gitlab side of the bulk, not from salt.

I execute poudriere with:

poudriere bulk -t -r -p gitlab -j 150amd64 -z salt314 sysutils/py-salt
I think it is pulled in by:
security/py-google-auth/Makefile
...
OPTIONS_DEFAULT=AIOHTTP PYJWT REQUESTS
...
AIOHTTP_RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}aiohttp>=3.8.0<4.0.0:www/py-aiohttp@${PY_FLAVOR}
Kind regards
Matthias
--------------f325r6LHLotDw65fNg9d67uL
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Am 13.07.26 um 17:43 schrieb Kirill
Ponomarev:<br>
</div>
<blockquote type="cite" cite="mid:alUHhVTKljwfOrdX@krion.cc">
<pre wrap="" class="moz-quote-pre">www/py-aiohttp is not a dependency of salt, not in the 3008
RUN_DEPENDS, and nothing in salt's dependency chain. It's building
because your set is 150amd64-gitlab-salt314, so it's coming from the
gitlab side of the bulk, not from salt.</pre>
</blockquote>
<p>I execute poudriere with:</p>
<pre wrap="" class="moz-quote-pre"></pre>
<div style="font-family: monospace; white-space: pre;">poudriere bulk -t -r -p gitlab -j 150amd64 -z salt314 sysutils/py-salt</div>
<div style="font-family: monospace; white-space: pre;">
</div>
<div style="font-family: monospace; white-space: pre;">I think it is pulled in by:<div
style="font-family: monospace; white-space: pre;"><div
style="display: inline;text-decoration-line: underline;text-decoration-style: solid;">security/py-google-auth/Makefile</div></div><div
style="font-family: monospace; white-space: pre;"><div
style="display: inline;text-decoration-line: underline;text-decoration-style: solid;">...</div></div><div
style="font-family: monospace; white-space: pre;"><div
style="display: inline;text-decoration-line: underline;text-decoration-style: solid;"><div
style="font-family: monospace; white-space: pre;">OPTIONS_DEFAULT=AIOHTTP PYJWT REQUESTS</div><div
style="font-family: monospace; white-space: pre;">...</div><div
style="font-family: monospace; white-space: pre;">AIOHTTP_RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}aiohttp&gt;=3.8.0&lt;4.0.0:www/py-aiohttp@${PY_FLAVOR}</div><div
style="font-family: monospace; white-space: pre;">
</div><div style="font-family: monospace; white-space: pre;">Kind regards</div><div
style="font-family: monospace; white-space: pre;">Matthias</div></div></div></div>
</body>
</html>

--------------f325r6LHLotDw65fNg9d67uL--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

This is a multi-part message in MIME format. --------------cAMAKVUrv8NM0BJcFlTPiwMq
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit

it is pulled in by the last line in salt:

${PYTHON_PKGNAMEPREFIX}opentelemetry-exporter-otlp-proto-http>0:devel/py-opentelemetry-exporter-otlp-proto-http@${PY_FLAVOR}
which brings in:
GCP_AUTH_RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}opentelemetry-exporter-credential-provider-gcp>=0.59b0:devel/py-opentelemetry-exporter-credential-provider-gcp@${PY_FLAVOR}
Which brings in: ${PYTHON_PKGNAMEPREFIX}google-auth>=2.25:security/py-google-auth@${PY_FLAVOR which then pulls:
AIOHTTP_RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}aiohttp>=3.8.0<4.0.0:www/py-aiohttp@${PY_FLAVOR}
Maybe you set some custom options to disable that or do you not use that patch?
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=272214&action=diff


Am 13.07.26 um 18:00 schrieb Matthias Fechner:

Am 13.07.26 um 17:43 schrieb Kirill Ponomarev:

www/py-aiohttp is not a dependency of salt, not in the 3008
RUN_DEPENDS, and nothing in salt's dependency chain. It's building
because your set is 150amd64-gitlab-salt314, so it's coming from the
gitlab side of the bulk, not from salt.

I execute poudriere with:

poudriere bulk -t -r -p gitlab -j 150amd64 -z salt314 sysutils/py-salt
I think it is pulled in by:
security/py-google-auth/Makefile
...
OPTIONS_DEFAULT=AIOHTTP PYJWT REQUESTS
...
AIOHTTP_RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}aiohttp>=3.8.0<4.0.0:www/py-aiohttp@${PY_FLAVOR}
Kind regards
Matthias

--------------cAMAKVUrv8NM0BJcFlTPiwMq
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>it is pulled in by the last line in salt:<br>
</p>
<div style="font-family: monospace; white-space: pre;">${PYTHON_PKGNAMEPREFIX}opentelemetry-exporter-otlp-proto-http&gt;0:devel/py-opentelemetry-exporter-otlp-proto-http@${PY_FLAVOR}</div>
<div style="font-family: monospace; white-space: pre;">
</div>
<div style="font-family: monospace; white-space: pre;">which brings in: <div style="font-family: monospace; white-space: pre;">GCP_AUTH_RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}opentelemetry-exporter-credential-provider-gcp&gt;=0.59b0:devel/py-opentelemetry-exporter-credential-provider-gcp@${PY_FLAVOR}</div><div
style="font-family: monospace; white-space: pre;">
</div><div style="font-family: monospace; white-space: pre;">Which brings in: <div style="font-family: monospace; white-space: pre;">${PYTHON_PKGNAMEPREFIX}google-auth&gt;=2.25:security/py-google-auth@${PY_FLAVOR</div><div
style="font-family: monospace; white-space: pre;">
</div><div style="font-family: monospace; white-space: pre;">which then pulls: <div style="font-family: monospace; white-space: pre;">AIOHTTP_RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}aiohttp&gt;=3.8.0&lt;4.0.0:www/py-aiohttp@${PY_FLAVOR}</div>
</div>Maybe you set some custom options to disable that or do you not use that patch?
<a class="moz-txt-link-freetext" href="https://bugs.freebsd.org/bugzilla/attachment.cgi?id=272214&amp;action=diff">https://bugs.freebsd.org/bugzilla/attachment.cgi?id=272214&amp;action=diff</a></div>
</div>
<p><br>
</p>
<div class="moz-cite-prefix">Am 13.07.26 um 18:00 schrieb Matthias
Fechner:<br>
</div>
<blockquote type="cite"
cite="mid:fa06c6b3-3a1e-4ffa-95fe-2f2b3ace1843@fechner.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">Am 13.07.26 um 17:43 schrieb Kirill
Ponomarev:<br>
</div>
<blockquote type="cite" cite="mid:alUHhVTKljwfOrdX@krion.cc">
<pre wrap="" class="moz-quote-pre">www/py-aiohttp is not a dependency of salt, not in the 3008
RUN_DEPENDS, and nothing in salt's dependency chain. It's building
because your set is 150amd64-gitlab-salt314, so it's coming from the
gitlab side of the bulk, not from salt.</pre>
</blockquote>
<p>I execute poudriere with:</p>
<div style="font-family: monospace; white-space: pre;">poudriere bulk -t -r -p gitlab -j 150amd64 -z salt314 sysutils/py-salt</div>
<div style="font-family: monospace; white-space: pre;">
</div>
<div style="font-family: monospace; white-space: pre;">I think it is pulled in by:<div
style="font-family: monospace; white-space: pre;"><div
style="display: inline;text-decoration-line: underline;text-decoration-style: solid;">security/py-google-auth/Makefile</div></div><div
style="font-family: monospace; white-space: pre;"><div
style="display: inline;text-decoration-line: underline;text-decoration-style: solid;">...</div></div><div
style="font-family: monospace; white-space: pre;"><div
style="display: inline;text-decoration-line: underline;text-decoration-style: solid;"><div
style="font-family: monospace; white-space: pre;">OPTIONS_DEFAULT=AIOHTTP PYJWT REQUESTS</div><div
style="font-family: monospace; white-space: pre;">...</div><div
style="font-family: monospace; white-space: pre;">AIOHTTP_RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}aiohttp&gt;=3.8.0&lt;4.0.0:www/py-aiohttp@${PY_FLAVOR}</div><div
style="font-family: monospace; white-space: pre;">
</div><div style="font-family: monospace; white-space: pre;">Kind regards</div><div
style="font-family: monospace; white-space: pre;">Matthias</div></div></div></div>
</blockquote>
</body>
</html>

--------------cAMAKVUrv8NM0BJcFlTPiwMq--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

--vubrcpVwGk2QeCLR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 07/13, Matthias Fechner wrote:

it is pulled in by the last line in salt:
=20
${PYTHON_PKGNAMEPREFIX}opentelemetry-exporter-otlp-proto-http>0:devel/py-=

opentelemetry-exporter-otlp-proto-http@${PY_FLAVOR}

which brings in:
GCP_AUTH_RUN_DEPENDS=3D ${PYTHON_PKGNAMEPREFIX}opentelemetry-exporter-cre=

dential-provider-gcp>=3D0.59b0:devel/py-opentelemetry-exporter-credential-p= rovider-gcp@${PY_FLAVOR}

Which brings in: ${PYTHON_PKGNAMEPREFIX}google-auth>=3D2.25:security/py-google-auth@${PY_F=

LAVOR

which then pulls:
AIOHTTP_RUN_DEPENDS=3D ${PYTHON_PKGNAMEPREFIX}aiohttp>=3D3.8.0<4.0.0:www/py-aiohttp@${PY_FLAVOR} Maybe you set some custom options to disable that or do you not use that patch? https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D272214&action=3Ddiff

=20
You're right, I'd checked with make run-depends-list, which only
shows direct deps, so I missed the transitive pull. When I tested the
patch on 2026-06-28, the tree had py-aiohttp-3.13.5_1, which compiles
fine under python 3.14. On 2026-07-08 sunpoet bumped aiohttp to
3.14.1 and that version doesn't build against python 3.14, probably
it's an upstream bug. You can disable the GCP_AUTH option on
devel/py-opentelemetry-exporter-otlp-proto-http in your set, that
drops the whole google-auth/aiohttp subtree and lets the build
proceed I guess.

--vubrcpVwGk2QeCLR
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQFPBAABCAA5FiEEJCHRFhEAQujKni1pDyI9/LMCykUFAmpVHqkbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwzAAoJEA8iPfyzAspFpBgH/2Z52AvN0MYbxwzN2ccn 5KBEeJTLqiUBw/S58oKEi0O22ZmL0CHdGVP56Qo7LYotfjCT7zffm7xwizw0s08t w3gIVOYhit2VZ4SNJXy7WQqJLWlsZnKz1fxcGzGIoRS6vGv7MOW5Azx0JzdHyYq6 W4A6ZrWpuppmaz7Mh0qlYx1jvOikXIdgN0SdhOpyIbGobBL8vP0mW6k2hVlFWbau +0FnZbzYUYwk0s3fDP5l06ASeYhdlbGAiXjjHjyjBRjRU4cJNCulA/c6v1LXOuMz rhziaM3sSwuDsAaX9kcZZiZgWhdfdxSNaheFfSm9tHhFJPoRRwvCUSmFE7qwtDHX
Su8=
=QJK3
-----END PGP SIGNATURE-----

--vubrcpVwGk2QeCLR--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

This is a multi-part message in MIME format. --------------GPfNgUGyt3vEhTBOA0GdkbuO
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit

Am 13.07.26 um 19:21 schrieb Kirill Ponomarev:

You're right, I'd checked with make run-depends-list, which only
shows direct deps, so I missed the transitive pull. When I tested the
patch on 2026-06-28, the tree had py-aiohttp-3.13.5_1, which compiles
fine under python 3.14. On 2026-07-08 sunpoet bumped aiohttp to
3.14.1 and that version doesn't build against python 3.14, probably
it's an upstream bug. You can disable the GCP_AUTH option on
devel/py-opentelemetry-exporter-otlp-proto-http in your set, that
drops the whole google-auth/aiohttp subtree and lets the build
proceed I guess.

I disabled it now with:

poudriere options -z salt314 devel/py-opentelemetry-exporter-otlp-proto-http Hit CTRL+c after devel/py-opentelemetry-exporter-otlp-proto-http was stored. Build is now fine. I will test it today if I have a waiting gap ;) I
keep you posted.
Matthias


--------------GPfNgUGyt3vEhTBOA0GdkbuO
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Am 13.07.26 um 19:21 schrieb Kirill
Ponomarev:<br>
</div>
<blockquote type="cite" cite="mid:alUeqewfV1eYyuST@krion.cc">
<pre class="moz-quote-pre" wrap=""> You're right, I'd checked with make run-depends-list, which only
shows direct deps, so I missed the transitive pull. When I tested the
patch on 2026-06-28, the tree had py-aiohttp-3.13.5_1, which compiles
fine under python 3.14. On 2026-07-08 sunpoet bumped aiohttp to
3.14.1 and that version doesn't build against python 3.14, probably
it's an upstream bug. You can disable the GCP_AUTH option on
devel/py-opentelemetry-exporter-otlp-proto-http in your set, that
drops the whole google-auth/aiohttp subtree and lets the build
proceed I guess.</pre>
</blockquote>
<p>I disabled it now with:<br>
</p>
<div style="font-family: monospace; white-space: pre;">poudriere options -z salt314 devel/py-opentelemetry-exporter-otlp-proto-http</div>
<div style="font-family: monospace; white-space: pre;">
</div>
<div style="font-family: monospace; white-space: pre;">Hit CTRL+c after devel/py-opentelemetry-exporter-otlp-proto-http was stored.</div>
<div style="font-family: monospace; white-space: pre;">
</div>
<div style="font-family: monospace; white-space: pre;">Build is now fine.
I will test it today if I have a waiting gap ;)

I keep you posted.</div>
<div style="font-family: monospace; white-space: pre;">
</div>
<div style="font-family: monospace; white-space: pre;">Matthias</div>
<p><br>
</p>
</body>
</html>

--------------GPfNgUGyt3vEhTBOA0GdkbuO--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

This is a multi-part message in MIME format. --------------VozOGzwMuTd9As2tOSQPTPAK
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit

Am 14.07.26 um 06:52 schrieb Matthias Fechner:

I disabled it now with:

poudriere options -z salt314
devel/py-opentelemetry-exporter-otlp-proto-http
Hit CTRL+c after devel/py-opentelemetry-exporter-otlp-proto-http was
stored.
Build is now fine. I will test it today if I have a waiting gap ;) I
keep you posted.

do you know if some path has changed the master is reading the state files?
I have not used salt now for some time, but it seems that the minion
does not find the state (not the master does).

If I execute on the minion:

salt-call -l debug state.apply common
I see:
...
[DEBUG ] Loading private key [DEBUG ] Loading public key [DEBUG ]
Finished gathering pillar data for state run [INFO ] Loading fresh
modules for state activity [DEBUG ] The functions from module 'jinja'
are being loaded by dir() on the loaded module [DEBUG ] LazyLoaded jinja.render [DEBUG ] The functions from module 'yaml' are being loaded
by dir() on the loaded module [DEBUG ] LazyLoaded yaml.render [DEBUG ]
Could not find file 'salt://common.sls' in saltenv 'base' [DEBUG ] Could
not find file 'salt://common/init.sls' in saltenv 'base'
The states are existing on the master.
ls -las /usr/local/etc/salt/states/common/ total 0 0 drwxr-xr-x 1
vagrant vagrant 58 Feb 21 11:20 . 0 drwxr-xr-x 1 vagrant vagrant 262 Mar
30 08:30 .. 0 drwxr-xr-x 1 vagrant vagrant 88 Jul 13 10:29 files 0
-rwxrwxrwx 1 vagrant vagrant 780 Feb 2 16:52 init.sls 0 -rwxrwxrwx 1
vagrant vagrant 1428 Nov 21 2025 map.jinja 0 -rwxrwxrwx 1 vagrant
vagrant 689 Nov 23 2025 pkg.sls
I see exactly the same behavior if I execute salt-call from the master.

Is there additional configuration required compared to the older version?

Thanks
Matthias

--------------VozOGzwMuTd9As2tOSQPTPAK
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Am 14.07.26 um 06:52 schrieb Matthias
Fechner:<br>
</div>
<blockquote type="cite"
cite="mid:456a1002-a918-4d99-ba81-650a001fe2f1@fechner.net">
<p>I disabled it now with:<br>
</p>
<div style="font-family: monospace; white-space: pre;">poudriere options -z salt314 devel/py-opentelemetry-exporter-otlp-proto-http</div>
<div style="font-family: monospace; white-space: pre;">
</div>
<div style="font-family: monospace; white-space: pre;">Hit CTRL+c after devel/py-opentelemetry-exporter-otlp-proto-http was stored.</div>
<div style="font-family: monospace; white-space: pre;">
</div>
<div style="font-family: monospace; white-space: pre;">Build is now fine. I will test it today if I have a waiting gap ;)

I keep you posted.</div>
</blockquote>
<p>do you know if some path has changed the master is reading the
state files?<br>
I have not used salt now for some time, but it seems that the
minion does not find the state (not the master does).<br>
<br>
If I execute on the minion:<br>
</p>
<div style="font-family: monospace; white-space: pre;">salt-call -l debug state.apply common</div>
<div style="font-family: monospace; white-space: pre;">
</div>
<div style="font-family: monospace; white-space: pre;">I see:</div>
<div style="font-family: monospace; white-space: pre;">...<div
style="font-family: monospace; white-space: pre;">[DEBUG ] Loading private key
[DEBUG ] Loading public key
[DEBUG ] Finished gathering pillar data for state run
[INFO ] Loading fresh modules for state activity
[DEBUG ] The functions from module 'jinja' are being loaded by dir() on the loaded module
[DEBUG ] LazyLoaded jinja.render
[DEBUG ] The functions from module 'yaml' are being loaded by dir() on the loaded module
[DEBUG ] LazyLoaded yaml.render
[DEBUG ] Could not find file 'salt://common.sls' in saltenv 'base'
[DEBUG ] Could not find file 'salt://common/init.sls' in saltenv 'base'</div><div
style="font-family: monospace; white-space: pre;">
</div><div style="font-family: monospace; white-space: pre;">The states are existing on the master.</div><div
style="font-family: monospace; white-space: pre;"><div
style="font-family: monospace; white-space: pre;">ls -las /usr/local/etc/salt/states/common/
total 0
0 drwxr-xr-x 1 vagrant vagrant 58 Feb 21 11:20 .
0 drwxr-xr-x 1 vagrant vagrant 262 Mar 30 08:30 ..
0 drwxr-xr-x 1 vagrant vagrant 88 Jul 13 10:29 files
0 -rwxrwxrwx 1 vagrant vagrant 780 Feb 2 16:52 init.sls
0 -rwxrwxrwx 1 vagrant vagrant 1428 Nov 21 2025 map.jinja
0 -rwxrwxrwx 1 vagrant vagrant 689 Nov 23 2025 pkg.sls</div>
</div>I see exactly the same behavior if I execute salt-call from the master.</div>
<p>Is there additional configuration required compared to the older
version?<br>
<br>
Thanks<br>
Matthias</p>
</body>
</html>

--------------VozOGzwMuTd9As2tOSQPTPAK--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On 7/13/26 14:51, Miroslav Lachman wrote:

Hello.

poudriere testport -j myjail -p myports sysutils/py-salt@py311

I had tried this, as it would be the quickest way, but unfortunately it doesn't work.

# poudriere bulk -v -j 151amd64 sysutils/py-salt@py311
[00:00:00] Creating the reference jail... done
[00:00:00] Mounting system devices for 151amd64-default
[00:00:00] Stashing existing package repository
[00:00:00] Mounting ccache from: /ccache
[00:00:00] Mounting ports from: /usr/ports/
[00:00:00] Mounting packages from: /usr/local/poudriere/data/packages/151amd64-default
[00:00:00] Mounting distfiles from: /usr/ports/distfiles
[00:00:00] Copying /var/db/ports from: /usr/local/etc/poudriere.d/options [00:00:01] Appending to make.conf: /usr/local/etc/poudriere.d/make.conf /etc/resolv.conf -> /usr/local/poudriere/data/.m/151amd64-default/ref/etc/resolv.conf
[00:00:01] Starting jail 151amd64-default
Updating /var/run/os-release done.
[00:00:01] Will build as nobody:nobody (65534:65534)
[00:00:02] Logs: /usr/local/poudriere/data/logs/bulk/151amd64-default/2026-07-19_09h20m49s
[00:00:02] Loading MOVED for /usr/local/poudriere/data/.m/151amd64-default/ref/usr/ports
[00:00:02] Ports supports: FLAVORS SUBPACKAGES SELECTED_OPTIONS
[00:00:02] Inspecting ports tree for modifications to git checkout... yes [00:00:02] Ports top-level git hash: c6f86138dd11063977cbcd2d03210df01a6e7dff (dirty)
[00:00:02] Gathering ports metadata
[00:00:03] Calculating ports order and dependencies
[00:00:03] Trimming IGNORED and blacklisted ports
[00:00:03] Ignoring sysutils/py-salt@py311 | py311-salt-3006.26,1: Unknown flavor 'py311', possible flavors: py312

BTW, Poudriere insist on writing "[00:00:03] Ignoring" and ": Unknown
flavor 'py311', possible flavors: py312" in black.
I use XFCE terminal with a black background and these texts become
invisible.
Is there a way to teach Poudriere to stop using black?

I didn't test it, not sure if it works for Salt, but it works for some
other ports.

I tried with a few other ports (e.g. dns/py-publicsuffix2), but they all
fail.
Can you tell one that works, so I can test?



bye & Thanks
av.


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Sun, 19 Jul 2026 09:33:06 +0200 Andrea Venturoli wrote:

On 7/13/26 11:00, T-|l Coosemans wrote:

Hello.

In sysutils/py-salt/Makefile line 38, replace "python" with "python:3.11".

Doesn't work.

root@poudriere:~ # poudriere bulk -v -j 151amd64 sysutils/py-salt
[...]
[00:00:42] Ignored ports: devel/py-Jinja2@py311
devel/py-jaraco.text@py311 devel/py-msgpack@py311
devel/py-jmespath@py311 devel/py-cffi@py311 devel/py-frozenlist@py311 devel/py-pyyaml@py311 net/py-libcloud@py311 misc/py-progressbar@py311 net/py-pyzmq@py311 security/py-pycryptodomex@py311
sysutils/py-croniter@py311 devel/py-virtualenv@py311
sysutils/py-psutil@py311 sysutils/py-distro@py311 www/py-tornado@py311 textproc/py-markupsafe@py311 security/py-cryptography@py311 www/py-requests@py311 devel/py-immutables@py311 devel/py-timelib@py311 devel/py-looseversion@py311 devel/py-backports@py311
devel/py-pyinotify@py311

It seems this solution gets poudriere going, but moves the problem to
the dependent ports :(

Is there something else wrong?

Try adding "allflavors" to the USE_PYTHON variable in the port Makefile
of all the ignored ports listed above.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2