On Tue, Jun 30, 2020 at 2:18 PM Christopher <ctubbsii@xxxxxxxxxxxxxxxxx> wrote: > > Hi, > > I know Fedora doesn't directly support Amazon Linux, but I was > wondering if the package maintainer for rpmconf on EPEL was aware that > the latest version doesn't work on Amazon Linux 2, which recently > updated to python-3.7, whereas rpmconf has a direct dependency on > python(abi)=3.6. If it's possible to use '>=3.6' instead, and the > package maintainer is willing to update it so it works with python 3.7 > on Amazon Linux 2, that would be great for my use case. You need to talk to Amazon. They have their own EPEL repository, inconsistently forked from EPEL and enabled with the "amazon-linux-extras" command, along with a variety of other not-really-yum-repo-managed tools like mock and ansible. It's problematic.. And don't let that incomplete EPEL channel get mixed with the official EPEL repository in your configurations. The time spent hunting for workarounds might be better spent migrating to RHEL or CentOS, which is likely to be more compatible with Fedora packages backported through EPEL. The decision to leapfrog to python 3.7 was problematic, since it also puts them ahead of RHEL 8 and CentOS 8's releases of python 3.6 and complicates EPEL support profoundly. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
