On Wed, Apr 11, 2018 at 12:58 AM, Todd Zullinger <tmz@xxxxxxxxx> wrote: > James Hogarth wrote: >> I was under the impression that as of 2.4.0 in EL7 we removed ansible >> from EPEL7 since Red Hat included it in their extras repo, and EPEL >> policy is not to conflict. >> >> I was surprised just now to see ansible 2.5.0 on a test centos system, >> when it wasn't in extras, and on a little bit of a search found: >> >> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-7ef392255b >> >> Of course this is a bit of an issue for CentOS/RHEL users that have >> need for the Red Hat ansible as they have been upgraded, and RH will >> need to epoch bump (or release 2.5.1 and we pull this from EPEL7 then) >> to ensure they get it from the right repo. >> >> With a branch retirement shouldn't this have been blocked in koji? > > Red Hat announced today that Ansible was being deprecated > from the extras channel. Their advice is that those who > have "previously installed Ansible and its dependencies from > the Extras channel are advised to enable and update from the > Ansible Engine channel, or uninstall the packages as future > errata will not be provided from the Extras channel." > > https://access.redhat.com/errata/RHSA-2018:1075 > > Given that, I believe it is reasonable to see ansible return > to EPEL. This was discussed in previous EPEL meetings a > bit, so I'm sure it was known to at least some of the folks > involved. There probably should be an announcement sent to the epel announce list then it gets to a wider audience so more people know this. _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
