Ansible in EPEL 8

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

 



Hello EPEL users and developers,


RHEL 8.8 was released yesterday,
so I have updated ansible in EPEL 8 from 6.3.0 to 7.2.0 to match RHEL
8.8's ansible-core bump from 2.13.3 to 2.14.2.
Each ansible major version is tied to a specific major version of
ansible-core, and we keep them in sync.

Along with this change, RHEL 8.8 builds ansible-core for the python3.11
stack instead of the python39 stack that it was previously built for.
Therefore, ansible in EPEL 8 is now built for python3.11 as well.

I also updated ansible-collection-community-general to 7.0.0 as per the
discussions in [1].

Here is the Bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-ca07fe358c
Please help test and give karma.

Until this update is pushed to stable, you may receive an error like
this when running dnf upgrade

```
Error:
 Problem: package ansible-6.3.0-2.el8.1.noarch requires python3.9dist(ansible-core) >= 2.13.3, but none of the providers can be installed
  - cannot install both ansible-core-2.14.2-3.el8.x86_64 and ansible-core-2.13.3-2.el8_7.x86_64
  - cannot install both ansible-core-2.14.2-3.el8.x86_64 and ansible-core-2.13.3-1.el8.x86_64
  - cannot install the best update candidate for package ansible-core-2.13.3-2.el8_7.x86_64
  - cannot install the best update candidate for package ansible-6.3.0-2.el8.1.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
```

There are a couple potential solutions:

1. Run
     $ dnf upgrade --exclude ansible-core
   to skip ansible-core and upgrade everything else.
2. Later today or tomorrow, you'll be able to install
   ansible 7.2.0 from testing with
     $ dnf upgrade --refresh --enablerepo=epel-testing ansible ansible-core
   and then run a plain `dnf upgrade` as usual.

Note that EPEL tracks RHEL and not rebuilds. Some rebuilds may lag
behind RHEL and not yet have 8.8 content. Our goal is to get packages
out as soon as possible so we don't break updates for RHEL users.

[1] https://lists.fedoraproject.org/archives/search?q=A+coordinated+plan+for+ansible-collection+updates+in+EPEL%3F&page=1&mlist=epel-devel%40lists.fedoraproject.org&sortÚte-asc

--
Happy automating,


Maxwell G (@gotmax23)
Pronouns: He/They
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue




[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