Things don't work that quickly. We have processes that need to be
followed for packages to be reviewed and such. If you are not already
a Fedora packager there will need to be steps to become one. In the
mean time, the first step would be to contact the package owners of
python-blinker and python-sqlalchemy to see if they can work out a way
to get the sub-packages into EPEL quickly.
On 30 March 2017 at 07:21, Martin Juhl <mj(a)casalogic.dk> wrote:
Ok
So I will create the new sources/SPECS...
When should I commit the files to???
Regards
Martin
----- Original meddelelse -----
Fra: "Tuomo Soini" <tis(a)foobar.fi>
Til: "epel-devel" <epel-devel(a)lists.fedoraproject.org>
Sendt: torsdag, 30. marts 2017 13:19:32
Emne: [EPEL-devel] Re: Pull request/Changes to CentOS Extras repo??
On Thu, 30 Mar 2017 12:41:35 +0200 (CEST)
Martin Juhl <mj(a)casalogic.dk> wrote:
> 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???
These are both rhel7 base packages so only way to get them to epel7 is
to create new sources python3-blinker and python3-sqlalchemy. Which
ones do generate python34 variants of these packages and not
python2/python variants.
--
Tuomo Soini <tis(a)foobar.fi>
Foobar Linux services
+358 40 5240030
Foobar Oy <
http://foobar.fi/>
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
--
Stephen J Smoogen.