On 12/05/2017 01:36 AM, Aurelien Bompard wrote: > Hey folks! > > I have a need for Python 3.5+ in EPEL (newest versions of Mailman 3 need > it), so I tried rebuilding it by taking advantage of our %python3_other_* > macros. There's a lot of packages that need to be built in the right order > to get to a full Python 3.6 build, and even much more packages that need > changes to use those macros. > I finally got to complete the build and its dependencies, and I uploaded > the packages here: > > https://abompard.fedorapeople.org/python36-epel/ > > In that directory there's also a "build-order.txt" file that lists which > packages should be rebuild, in which order, and with which options. > I'm totally willing to push the spec changes I've made to the maintainers > of course, if you think it's the right way to go. Cool. Thanks very much for working on this! > The main python36 packages carries an additional file to define the proper > %python3_other* macros, but it should actually be an update of the main > python-srpm-macros package. Yeah, or epel-rpm-macros... but I guess python makes more sense. > What do you think? Where should I go from here? Should I make pull requests > for the individual spec changes now? Well, IMHO it would be good to land any work that keeps working with 34, but we should probibly get some provenpackager(s) to drive all the rest of the changes and submitting one big update with all the python36 + rebuilds. We will need to also schedule and announce when the switch will take place, as after this lands the 34 versions of the packages will disappear and the 36 ones land... kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
