[EPEL-devel] Re: Fast-moving packages in EPEL
On Tue, Oct 13, 2020 at 12:14:24PM +0200, Leon Fauster wrote: > Am 13.10.20 um 10:12 schrieb Christopher Engelhard: > > On 12.10.20 10:49, Leon Fauster wrote: > > > Not sure but IIRC EPEL should not depend on software collections ...? > > > > Can someone confirm that? If the package can't depend on php7.2+, then > > the question of how to deal with EPEL7 is moot. > > > > My recall was this > > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/DBAQB3V35TXPNUV4UKKHXUC52BENZJUQ/ It's changed a bit since then. We now allow scls if: * They only need to be used at build time (ie, the rpms produced do not require users to install/enable any scls) * They are approved by the epel steering comittee. So far we have only enabled devtoolset. (so for example, chromium uses devtoolset to build with a newer gcc, but does not require users to install or enable anything to use it). In the case of php, this would likely not work because it would require users to install/enable php to get the webserver module or cmd line. 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
[EPEL-devel] Re: Fast-moving packages in EPEL
On 13.10.20 12:14, Leon Fauster wrote: > My recall was this > > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/DBAQB3V35TXPNUV4UKKHXUC52BENZJUQ/ OK, thanks, that clears that up. So I'll go ahead and retire the EPEL7 package. Maybe I can put an updated one on Copr instead. Thanks to all of you, you helped tremendously. Christopher ___ 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
[EPEL-devel] Re: [EPEL7] Celery stack update & Python 3 enablement
On Mon, Oct 5, 2020 at 7:09 PM Kevin Fenzi wrote: > How big are the changes between 4.2.2 and 4.3? > So, I finally got back to this, sorry for the late reply. After reading through kombu 4.3 changelog [0], it seems the only truly breaking change is in SQLAlchemy transport ( I can be wrong, of course) which would require manual intervention in the database: "Added an index to the Message table for the SQLAlchemy transport." >From what I understand, using SQLAlchemy for celery/kombu is pretty niche and documentation mentions and most applications around the world I was able to find are using different backends for celery (RabbitMQ, Redis). The plan will be to leave the upgraded stack for a long time in testing, I was thinking about something like a month or two. I'll definitely send an announcement once the stack is in testing repo and then (week or two) before pushing it to epel stable. [0] https://docs.celeryproject.org/projects/kombu/en/v4.3.0/changelog.html ___ 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
