The Ansible Core team is not responsible for OS packaging. The only official packaging of ansible-core for upstream lives on pypi.org. From a downstream Red Hat perspective, ansible-core 2.11 is available to Ansible Automation Platform customers.
I will note that ansible-core has been accepted into the appstream for CentOS Stream, and will also be included in RHEL 8.6 and RHEL 9.0 starting in May. You will note that I mention the package name `ansible-core` several times here. In 2.10 the package was split into 2 parts, an `ansible-core` packaging containing the CLI tools, and a small number of plugins, and then the `ansible` package which bundles a large number of community maintained plugins. I do see ansible-core packages for Fedora listed at https://src.fedoraproject.org/rpms/ansible-core On Wed, Oct 27, 2021 at 1:31 AM Mark Mielke <[email protected]> wrote: > Hi all: > > This Pull Request was closed due to "The 2.9 release is only accepting > security fixes at this time in its lifecycle. As such, this PR does not > meet the requirements to be backported to 2.9.": > > https://github.com/ansible/ansible/pull/76146 > > 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> > > This seems to be a conflict between what the Ansible devel believe to be > user requirements, and what the users believe to be requirements. Something > is getting blocked in the middle - perhaps the move to collections? > > In any case, please re-review the true state of Ansible 2.9, and whether > or not it should be considered "current". If Ansible 2.9 is really no > longer current, is there effort being made by Ansible devel to ensure that > Ansible 2.11 and later are published to users on standard channels? > > I really don't want to fork Ansible 2.9 and manage my own patches. > Especially for simple patches like the one I referenced. > > Thanks, > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-devel/b8f8c34f-2012-410a-9289-5f97940e1774n%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-devel/b8f8c34f-2012-410a-9289-5f97940e1774n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Matt Martz @sivel sivel.net -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CAD8N0v_34X0Fw%3DSGRQ%2BYvCy-tAS1s7NMLAe5%3DnHJzHjZWJtpxA%40mail.gmail.com.
