On Wed, 11 Apr 2018, 01:13 James Hogarth, <james.hogarth(a)gmail.com> wrote:
On Wed, 11 Apr 2018, 00:59 Todd Zullinger, <tmz(a)pobox.com> 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:
> > 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."
> Given that, I believe it is reasonable to see ansible
> 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
Cheers for the info.
It wasn't mentioned on the devel list, I didn't see it in the 7.5 release
notes and it was still in extras when I checked a short while ago.
In that case yes I agree it makes total sense to return to epel7
I wonder why they dropped it when the whole point of them bringing it in
to begin with was for Satellite and Tower to have it in the standard RHEL
Seems so pointless to have only had one release there!
And having read the bugzilla entry now... they moved it to its own product
channel that all RHEL subscribers have access to...
Again this feels so very pointless.