LWN: Comments on "EPEL 8.0 released"

EPEL 8.0 released

seyman — Tue, 12 Nov 2019 08:29:46 +0000

There's a request pending.

EPEL 8.0 released

msteele — Fri, 08 Nov 2019 19:14:43 +0000

Is there a plan to include rsnapshot in EPEL 8.0?

Python 3.7

yodermk — Thu, 15 Aug 2019 18:04:04 +0000

Another thought, I get that there are reasons Red Hat is hesitant (even though with Streams it's kind of the whole point of that). But it still leave a huge hole in the Python/*EL ecosystem.

Maybe the PSF should sponsor a project that maintains a quality YUM repo that always builds the latest Python for supported *EL/Fedora distros. For example, the PostgreSQL Global Development Group sponsors the excellent https://yum.postgresql.org/ to do just that for PostgreSQL. As such, I'm confident that as soon as PG 12 is released, I'll be able to easily leverage it. Yeah, I get the PSF is stretched too, but surely it is in their interest to have the latest Python readily available on *EL. I wonder if they could get sponsorship for it.

Python 3.7

dsommers — Thu, 15 Aug 2019 10:53:29 +0000

It's not that 3.7 necessarily is hard to package. But the whole "instrumentation" around it when Red Hat provides packages needs to be considered.

When Red Hat decides to package something and distribute it, they put a lot of resources into it. They will have allocated dedicated package maintainers for it, security teams are tasked to keep an eye on what happens with these packages, QA teams needs to allocate resources for testing and ensure regression tests are present and running. Then the release teams which needs to ensure packaging is done accordingly to the RHEL standards, that packages are installable, can be upgraded, downgraded and uninstalled without issues, etc. And on top of that, the support teams needs to get knowledge about this package. And all this is an effort which they dedicate for multiple years.

So with all this, it is a noticable cost for Red Hat to commit themselves to ship yet another Python release. I'm not saying it won't happen, but I would more expect it to happen at a later point where Python 2.x truly is dead and there are even more interesting Python releases which has stabilized.

Of course you can argue that the gap between 3.6 and 3.7 is so small lots of the current 3.6 efforts can be reused on 3.7. But then it comes into a prioritization challenge. If there are urgent issues needed to be solved in both 3.6 and 3.7, which should be resolved first? And will Red hat customers be happy if 3.7 gets priority when their own software stack depends on 3.6?

We can't solve all this in a discussion, and at least not here in the LWN comment section. But it is important to understand that when Red Hat ships a package, they're really highly committed to ensure it is maintainable over a longer time and strive to ensure it doesn't explode in the face of their users.

Python 3.7

yodermk — Thu, 15 Aug 2019 09:25:17 +0000

RHEL 7.7 has Python 3.6, not 3.7. 3.6 has been available via IUS and maybe other repos for a long time. I'm specifically wondering how it can be that no reputable repo has pushed 3.7 RPMs. Is it that much harder to package than 3.6?

Python 3.7

amacater — Thu, 15 Aug 2019 08:40:10 +0000

Python 3 is in RHEL 7.7, as just released. When CentOS get to package that once 8.0 is finished, Python 3 will be available just as it is upstream.

This _finally_ because 2.* dies next year and this is the last feature release for RHEL 7.* as it enters maintenance phase. [Maintenance phase 1 until 2020, 2 until 2024]
This point release was slightly earlier than expected

Just as EPEL 8 is significantly different from that for 7, so the release of SCL 8 for RHEL / EPEL 7 is the last in that form, I think.

Python 3.7

dowdle — Wed, 14 Aug 2019 23:48:38 +0000

podman, not docker, eh.

Python 3.7

yodermk — Wed, 14 Aug 2019 22:54:12 +0000

I do hope they get Python 3.7 packaged in the near future.

Bit of a rant: It's been out for over a year, and RPM packages don't even exist for EL7, much less EL8. No doubt there's huge demand for it.

It's not even in Red Hat Streams yet, and I thought the whole point of Streams was to get developers the latest languages and such in a timely manner. https://access.redhat.com/documentation/en-us/red_hat_ent...

So far the best Python 3.6 packages for *EL have been in the IUS repository, and its maintainer is shifting them to EPEL, and rightly so. I'm not sure how many other people are intending to work on that. I get that it's one of the more complex packages. I'd be willing to try to help but given its complexity am not confident in my packaging ability at that level. At minimum I can test and try to offer packaging tweaks, so guess I'll join the EPEL Python SIG.

Not blaming anyone, because it's no one's job in particular to provide this, just wondering how there could be such a huge gap in the *EL/Python ecosystem.

Googling for installing 3.7 on CentOS 7 invariably leads to articles telling you how to compile from source, which from a systems engineering perspective is an absolute non-starter. I guess Docker would be an option, and might be the best way to go, unless packages show up soon.

EPEL 8.0 released

cyperpunks — Wed, 14 Aug 2019 17:40:58 +0000

Great news, thanks!