Fwd: Re: retirement of ansible-2.9.x

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



May 16, 2022 8:32:58 PM Maxwell G <gotmax@e.email>:

On Tuesday, April 19, 2022 3:14:56 PM CDT  Kevin Fenzi wrote:
> In epel8 I will be converting the 'ansible' epel8 package into the
> upstream ansible-5 meta collections package (which also pulls in
> ansible-core).
> 

Hi everyone,

I have rebased ansible to ansible 5 in epel8 and submitted a Bodhi update[1].
I would appreciate if you could help test the update and provide feedback. We
are also providing a newer version of ansible 5 in epel8-next that depends on
the newer version of ansible-core available in CentOS 8 Stream. Here[2] is the
Bodhi update for the epel8-next version.

[1]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-67f52f0700
[2]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-7083a5c511

I also branched ansible for epel9 and epel9-next. Here[3,4] are the Bodhi
updates for that.

[4]:https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-73e215eb5c
[5]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-3090b856c2

Remember that ansible 5 is just a bundle of ansible collections that are
released together, and it depends on ansible-core (the engine) which provides
the core modules, engine, and command line tools.  This provides the
"batteries-included" approach that users of ansible classic (ansible 2.9.x and
below) are used to. If you prefer a more minimalist approach, you can install
ansible-core alongside the specific collections you need. You can install
collections through EPEL's ansible-collection-* RPM packages or from Ansible
Galaxy. If you would like to do this, you can switch to ansible-core with `dnf
swap ansible ansible-core`.

-- 
Thanks,

Maxwell G (@gotmax23)
Pronouns: He/Him/His

Attachment: signature.asc
Description: PGP signature

_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux