On 11/02/2017 03:48 PM, Kevin Fenzi wrote:
On 11/02/2017 11:03 AM, Peter Rex wrote:
Thanks for the info, Ricardo. Hadn't found the retirement notice. Security,
I guess. I can't resist saying, though, that I regret using Ansible and my
assumption that one of the Es in EPEL stood for Enterprise. Oh well, live
and learn.
Sorry things didn't work out as you would have liked.
ansible1.9 was always intended as a short term 'bridge' to help give
folks more time to migrate to 2.0. When upstream stopped supporting it,
we retired it in EPEL as well. ansible is very very fast moving and
complex and there's no way we could backport even security fixes to an
out of date 1.9 version. Sorry.
You can of course still use 1.9 if you wish, just realize that it
doesn't get any bugfixes or security updates.
kevin
This highlights a problem I've occasionally had with EPEL, namely that
packages I depend on occasionally get removed. This especially causes
trouble when a package gets removed because it's now in RHEL, because it
takes a few months for CentOS and Scientific Linux to update. Perhaps
you could create an 'epel-unsupported' repo and move packages there
instead of removing them?
Thanks,
-Mat
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
