On Mon, Apr 18, 2022 at 3:49 PM Amos <a.goo0h@xxxxxxxxx> wrote:
On Mon, Apr 18, 2022 at 4:57 PM Kevin Fenzi <kevin@xxxxxxxxx> 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. ;(
kevinGoing back to the original thread: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_64 0.28.0-3.el8 @satellite-tools-6.8-for-rhel-8-x86_64-rpmsSystem that has EPEL and is registered with our Satellite server:qpid-proton-c.x86_64 0.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@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 on the list, report it: https://pagure.io/fedora-infrastructure
