Please branch and build breezy in epel8. PS. Following the EPEL package requests guidelines. If there are no takers I'm interested in being co-maintainer of this package in order to build it for EPEL.
As a co-maintainer of this package, I am not interested in maintaining it in EPEL myself.
Will you be able to branch and build Breezy in epel8? As per the package request guidelines, if there's no response to this in a couple of weeks, I'll contact epel-devel to see if someone wants to do this, or otherwise volunteer to do it myself.
Hi, sorry for a late reply. I'm not interested in maintaining Breezy in EPEL.
Björn, note that there is a handful of dependencies that would need to be packaged together with breezy.
I'm aware, as I've had to deal with that for the in-house build we are currently using (and would like to eliminate by me contributing it to EPEL instead). I think the most complicated part will be the dependency on a newer python-Cython than what's currently in EPEL and/or Powertools. As far as I can work out so far it's only build time dependencies that are necessary to be added.
Could be solved by using Python 3.8 or even 3.9.
I will look into if we could use Python 3.8/3.9 with Cython as a build dependency only for the Cython-to-C step, or if this would mean needing to make Breezy as a whole depend on 3.8/3.9.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.