On Thu, Oct 28, 2021 at 4:14 PM Kevin Fenzi <ke...@scrye.com> wrote: > > However, availability of releases beyond Ansible 2.9 for regular users > is > > limited: > > - EPEL 7: ansible-2.9.25-1.el7.noarch.rpm > > < > https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/a/ansible-2.9.25-1.el7.noarch.rpm > > > > - EPEL 8: ansible-2.9.25-1.el8.noarch.rpm > > < > https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/Packages/a/ansible-2.9.25-1.el8.noarch.rpm > > > > - Fedora 34: ansible-2.9.25-1.fc34.noarch.rpm > > < > https://dl.fedoraproject.org/pub/fedora/linux/updates/34/Everything/x86_64/Packages/a/ansible-2.9.25-1.fc34.noarch.rpm > > > f34 does now have ansible-core also (It was in updates-testing). > So, a bit of information from me (The Fedora/EPEL ansible maintainer).
Thank you very much, Kevin. Now that I know it is available, I will help with testing ansible-core. Please let me know if you need any other help. I would much rather contribute to your work (and upstream Ansible), then maintain a local patch and selfishly rebase your work. :-) > First, feel free to file a bug ( bugzilla.redhat.com / Fedora / ansible) > and I can look at adding that PR into the next round of 2.9.x updates I > send out. We are already carrying one for Rocky Linux, so it only seems > fair to include others if asked. I think it is a small failure for individual packagers to have to maintain their own downstream patch sets long-term in isolation to each other, sharing changes using some channel outside the Github Ansible project, rather than contributing them to the Github Ansible project and directly collaborating between packagers. However, in many cases - it is the path of least resistance. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=2018369 > As far as versions and plans for Fedora / EPEL: > > * We are working on a new 'ansible' package thats all the collections > from ansible 5: https://fedoraproject.org/wiki/Changes/Ansible5 > That will replace the old ansible-2.9.x package in Fedora 36 and require > ansible-core for engine. > > * ansible-core is available in f34/35/36 and will soon be available in > rhel8 and rhel9. epel7 will likely stick on the last 2.9.x version for a > while until it becomes untenable. Hopefully folks will have moved their > control hosts by then. > This sounds great, and the transition plan sounds smart as well. EPEL 7 and staying on Ansible 2.9.x makes sense to me as it is nearing end-of-life, and is one of the reasons why I think small patches such as supporting new targets like Oracle Linux 8, should still be permitted. * There's a number of ansible collections packaged up in Fedora/epel: > ansible-collection-ansible-netcommon.noarch > ansible-collection-ansible-posix.noarch > ansible-collection-ansible-utils.noarch > ansible-collection-chocolatey-chocolatey.noarch > ansible-collection-community-general.noarch > ansible-collection-community-kubernetes.noarch > ansible-collection-community-mysql.noarch > ansible-collection-containers-podman.noarch > ansible-collection-google-cloud.noarch > ansible-collection-microsoft-sql.noarch > ansible-collection-netbox-netbox.noarch > > and move as folks add them. You're welcome to install ansible-core and > any collections you need from there or galaxy. > > Hope that helps some. > Yes, it does. Thank you! -- Mark Mielke <mark.mie...@gmail.com> -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CALm7yL2DhE3Ts%3DxhcZW7k%2B7wy_MNWUOUnx283qc02Jfwt2WbmQ%40mail.gmail.com.
