[EPEL-devel] retirement of ansible-2.9.x

2022-04-19 Thread Kevin Fenzi
Greetings. 

Just a reminder that ansible-core (The split out ansible 'engine') will
be landing in RHEL8.6 (and other el builds thereafter). Also, the
ansible 2.9.x ('ansible classic') package is going to going end of life
and no longer supported in that same timeframe.

So, at that time I will be retiring the ansible 2.9.x package in epel7.

In epel8 I will be converting the 'ansible' epel8 package into the
upstream ansible-5 meta collections package (which also pulls in
ansible-core).

epel7 and epel8 ansible users are advised to plan for this
retirement/change. 

Thank you, 

kevin


signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[EPEL-devel] Re: EPEL conflicts with Satellite 6 packages

2022-04-19 Thread Troy Dawson
On Mon, Apr 18, 2022 at 3:49 PM Amos  wrote:

> On Mon, Apr 18, 2022 at 4:57 PM Kevin Fenzi  wrote:
>
>>
>> Yeah, I'll echo smooge here. Can you expand on exactly what you are
>> hitting?
>>
>> I can't seem to find the orig thread from 2016 in my mailbox, so I'm
>> really not sure what the issue is here. ;(
>>
>> kevin
>>
>>
> Going back to the original thread:
>
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/772FVSHWG6XLEKDYFRSKKMB4IDNPDPRD/#replies
>
> We don't (at least as far as I'm aware) have any broken systems, but this
> is what can result:
>
> System without EPEL:
>
> qpid-proton-c.x86_640.28.0-3.el8
> @satellite-tools-6.8-for-rhel-8-x86_64-rpms
>
> System that has EPEL and is registered with our Satellite server:
>
> qpid-proton-c.x86_640.37.0-1.el8   @epel
>
>
> Right now this system with EPEL hasn't encountered issues, but every time
> we have experienced this in the past, the system becomes unpatchable.
> Since the original post is from 2016, I was just wondering if this issue
> had evolved at all.
>
>
> Thanks,
>
> Amos
>

I think this is a good question to bring to the people who maintain the
Satellite repo.
The vast majority of the EPEL community have no access to the Satellite
repo and do not even know what packages are in it.
It looks like it's been six years, and they (The Satellite repo
maintainers) haven't reached out to work with us, as far as I know.
If this is a problem, please reach out to them and let them know.

Troy
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure