Created attachment 246226 [details] Update to 8.6.1 sysutils/ansible 8.6.1 builds and installs with py39-setuptools-68.2.2 but fails to configure with py39-setuptools-63.1.0_1.
This version also requires default python of 3.10.
^Triage: [tags] in issue Titles are deprecated. ^Triage: Reporter is committer, assign accordingly.
The latest port updates, 9.0.1, 9.1.0, and 9.2.0 have been committed to a branch, locally, pending PR/270358 resolution.
If people want I can post the latest patch. Just let me know.
My local ansible ports tree (using python3.10) is at sysutils/ansible 9.5.1 and sysutils/py-ansible-core 2.16.6. Waiting for python3.10 to become default so I can push the 15 pending commits.
https://github.com/ansible-collections/ansible.utils/pull/338 is a showstopper for me now that py-netaddr has been updated to 1.2.1. Now I get this error if I use ansible.utils.ipaddr('private') filter: An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: 'IPNetwork' object has no attribute 'is_private'
Comment on attachment 246226 [details] Update to 8.6.1 Don't use this patch. It requires python 3.10. I only opened this ticket as a dependency on PR/270358. The patch has been obsoleted because 9.5.1 will be committed when python3.10 becomes default.
(In reply to Einar Bjarni Halldórsson from comment #6) Your issue is not related to this bug.
(In reply to Cy Schubert from comment #8) My issue is related to this bug, because right now the version of ansible in ports is not compatible with py-netaddr in ports. So there is pressure to get ansible updated soon.
(In reply to Einar Bjarni Halldórsson from comment #9) Unfortunately pushing the commits in my ansible ports branch is impossible until PR/270358, PR/270510, and PR/272134 are resolved. PR/270510 is an exp-run to verify if the ports tree works with python3.10. As we can see python3.10 breaks a good many ports. You may wish to add yourself to the watch list for each of the listed PRs. I have build tested sysutils/ansible with the upstream patch applied. Hopefully that provides some relief. Can you please open a new PR for the new bug report so I can reference it in the commit.
I'll push out a point fix without a PR. I'll simply reference your name and email address in the commit.
(In reply to Cy Schubert from comment #10) Just to let you know, the latest ansible-9.5.1-tar.gz still contains the old ansible_collections/ansible/utils/plugins/plugin_utils/base/ipaddr_utils.py. Updating to the latest sysutils/ansible will not address your problem. ansible-collections as of May 15 in this ports r9.5.1 tarball has not imported the latest ansible.utils. The only path forward is a point patch that still applies to the latest port in my ansible branch. Rather than discuss this issue here, polluting the discussion regarding the update, please open a new PR. We can discuss there. I'll await the PR before committing the fix for you.