Hi Again... So... I forgot that python34 comes from EPEL, so the CentOS guys can't enable python3 builds... So I guess these builds should be done in EPEL?? I haven't got a list, but it's stuff like: python-blinker-1.3-2.el7.src.rpm python-sqlalchemy-0.9.8-1.el7.src.rpm They are already 95% prepared for building python packages (needs to replace python3->python34).. Can we get these builds into EPEL in some way??? Regards Martin ----- Original meddelelse ----- Fra: "mj" <mj@xxxxxxxxxxxx> Til: "epel-devel" <epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> Sendt: tirsdag, 28. marts 2017 17:06:09 Emne: [EPEL-devel] Re: Pull request/Changes to CentOS Extras repo?? Hi Stephen Thanks for the response.. I'll try to connect to the CentOS guys... Regards Martin ----- Original meddelelse ----- Fra: "Stephen John Smoogen" <smooge@xxxxxxxxx> Til: "epel-devel" <epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> Sendt: tirsdag, 28. marts 2017 16:27:39 Emne: [EPEL-devel] Re: Pull request/Changes to CentOS Extras repo?? On 28 March 2017 at 05:41, Martin Juhl <mj@xxxxxxxxxxxx> wrote: > Hi guys... > > I have some packages in the Extras repo, that I would like to be built for python3 as well as python2... > > I can provide the changes for the spec files, but what is the official way to commit changes / pull requests???? > > I would of cource then become the package manager of these packages... (we need them in the COPR project) > Hi Martin, Sorry I was not online in IRC when you tried to contact us last night. I think I am a little confused by the request. The CentOS extras is not connected to EPEL and packages in there are maintained by the CentOS developers. The list to raise this is at centos-devel@xxxxxxxxxx Or are you needing for some sort of packages to be put into EPEL from the CentOS extras that would be python 3 based? If so what packages are they? You would need to work out with the Fedora owner on how to make versions that work with python3 in EPEL. > Regards > > Martin Juhl > _______________________________________________ > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
