Hi Thanks for your response.. Basically, I don't know the "normal package review process".. where to push the packages?? and howto get the packages accepted... Regards Martin ----- Original meddelelse ----- Fra: "Kevin Fenzi" <kevin@xxxxxxxxx> Til: "epel-devel" <epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> Sendt: onsdag, 17. maj 2017 22:30:37 Emne: [EPEL-devel] Re: Pull request/Changes to CentOS Extras repo?? On 05/15/2017 06:05 AM, Martin Juhl wrote: > I have created this dependency repo: > > https://copr.fedorainfracloud.org/coprs/mrmeee/elcopr-depends/packages/ > > Containing: > > gcab - build dep for libappstream-glib > libappstream-glib - install dep for copr-backend (libappstream-glib-builder) > python-requests - build/install dep for copr-backend > python-urllib3 - build dep for python-requests in version 1.10.4, only 1.10.2 in CentOS > > Python packages needed for copr-frontend: > python34-blinker > python34-flask > python34-flask-sqlalchemy > python34-itsdangerous > python34-sphinx > python34-sqlalchemy > python34-werkzeug > > I think that the four packages on top needs to be added to the copr repo? > > The others we can probably get into EPEL with some work??? Do anyone know the exact procedure for getting them in??? Well, any of them that are not in RHEL: normal package review process. Any of them in RHEL that you need a python3 version for or whatever would need to be named differently from the RHEL version (python34-foo instead of python-foo), and normal review process. Does that answer the question for all of them? Or is there another case here? kevin _______________________________________________ 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
