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@casalogic.dk Til: "epel-devel" epel-devel@lists.fedoraproject.org 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@gmail.com Til: "epel-devel" epel-devel@lists.fedoraproject.org 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@casalogic.dk 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@centos.org

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@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org

Ok

So I will create the new sources/SPECS...

When should I commit the files to???

Regards

Martin

----- Original meddelelse ----- Fra: "Tuomo Soini" tis@foobar.fi Til: "epel-devel" epel-devel@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@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.

...

...

...

...

"SJS" == Stephen John Smoogen smooge@gmail.com writes:

SJS> Things don't work that quickly.

Well, they can work pretty quickly when the stars align.

SJS> We have processes that need to be followed for packages to be SJS> reviewed and such.

I would argue that reviews aren't actually needed due to the exemption about different versions of existing packages. I guess maybe that's stretching it just slightly (since that's mainly about adding, say, python-sqlalchemy1.1 without review instead of python3-sqlalchemy), but I would be perfectly happy to click the necessary button there.

The only finesse involved is making sure that package gets blocked in Fedora so that it only makes it into EPEL. That's no different from any other EPEL-only package.

SJS> If you are not already a Fedora packager there will need to be SJS> steps to become one.

Which shouldn't be too hard if Martin is prepared to be the maintainer of these things long term. There should be enough sponsors around reading this that someone is willing to help out. Me included if Martin is willing to hit me up on IRC.

- J<

Ok... now I have a complete list:

For building "python-flask-whooshee" in the copr project.. I need:

python3-blinker: No other dependencies

python3-flask: python3-itsdangerous python3-sqlalchemy python3-werkzeug - Depends on python3-sphinx

python3-flask-sqlalchemy No other dependencies

So all in all, it's 7 packages...

I have the specs for building only the python3..

What should I do to commit these for review???

I'm already in the fedora packager group...

Thanks...

/Martin

----- Original meddelelse ----- Fra: "Orion Poplawski" orion@cora.nwra.com Til: "epel-devel" epel-devel@lists.fedoraproject.org Sendt: fredag, 31. marts 2017 16:39:37 Emne: [EPEL-devel] Re: Pull request/Changes to CentOS Extras repo??

On 03/30/2017 04:41 AM, Martin Juhl 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

FYI - python3-sqlalchemy is already in EPEL7.

python34-sqlalchemy.x86_64 1.1.3-1.el7 epel

Hello,

I would perhaps try to contact one of a package maintainers for python-flask (see https://admin.fedoraproject.org/pkgdb/package/rpms/python-flask/). Or, you could file a request against https://bugzilla.redhat.com/show_bug.cgi?id=1406957 Fedora EPEL on Bugzilla to add Flask for python3. It's mainly about python3(4)-flask to get into EPEL, all other packages are mostly its deps. That would be a great achievement to get it there.

clime

On Thu, Apr 20, 2017 at 12:52 AM, Martin Juhl mj@casalogic.dk wrote:

Hi guys

I have no idea where to go from here???

Can anyone give me a hint???

Regards

Martin

----- Original meddelelse ----- Fra: "mj" mj@casalogic.dk Til: "epel-devel" epel-devel@lists.fedoraproject.org Sendt: tirsdag, 4. april 2017 10:42:20 Emne: [EPEL-devel] Re: Pull request/Changes to CentOS Extras repo??

Ok... now I have a complete list:

For building "python-flask-whooshee" in the copr project.. I need:

python3-blinker: No other dependencies

python3-flask: python3-itsdangerous python3-sqlalchemy python3-werkzeug - Depends on python3-sphinx

python3-flask-sqlalchemy No other dependencies

So all in all, it's 7 packages...

I have the specs for building only the python3..

What should I do to commit these for review???

I'm already in the fedora packager group...

Thanks...

/Martin

----- Original meddelelse ----- Fra: "Orion Poplawski" orion@cora.nwra.com Til: "epel-devel" epel-devel@lists.fedoraproject.org Sendt: fredag, 31. marts 2017 16:39:37 Emne: [EPEL-devel] Re: Pull request/Changes to CentOS Extras repo??

On 03/30/2017 04:41 AM, Martin Juhl 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

FYI - python3-sqlalchemy is already in EPEL7.

python34-sqlalchemy.x86_64 1.1.3-1.el7 epel

-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org

Hi

Ok.. so python3-sqlalchemy is already in EPEL.. then that is solved...

I'll look into the sphinx stuff...

Same as any other review. Just note in the comments that it is EPEL only.

I'm looking for the actual process.. I have the python packages in this repo:

https://copr.fedorainfracloud.org/coprs/mrmeee/elcopr-depends/packages/

But where and how should I upload the packages into a Fedora or EPEL repo??

Thanks

/Martin

----- Original meddelelse ----- Fra: "Orion Poplawski" orion@cora.nwra.com Til: "epel-devel" epel-devel@lists.fedoraproject.org Sendt: onsdag, 3. maj 2017 23:22:42 Emne: [EPEL-devel] Re: Pull request/Changes to CentOS Extras repo??

On 04/04/2017 02:42 AM, Martin Juhl wrote:

Ok... now I have a complete list:

For building "python-flask-whooshee" in the copr project.. I need:

python3-blinker: No other dependencies

python3-flask: python3-itsdangerous python3-sqlalchemy

again, already in EPEL7

python3-werkzeug - Depends on python3-sphinx

python3-sphinx is a hairy mess last I checked. I've either disabled docs or built with python-sphinx.

python3-flask-sqlalchemy No other dependencies

So all in all, it's 7 packages...

I have the specs for building only the python3..

What should I do to commit these for review???

Same as any other review. Just note in the comments that it is EPEL only.

I'm already in the fedora packager group...

Thanks...

/Martin

----- Original meddelelse ----- Fra: "Orion Poplawski" orion@cora.nwra.com Til: "epel-devel" epel-devel@lists.fedoraproject.org Sendt: fredag, 31. marts 2017 16:39:37 Emne: [EPEL-devel] Re: Pull request/Changes to CentOS Extras repo??

On 03/30/2017 04:41 AM, Martin Juhl 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

FYI - python3-sqlalchemy is already in EPEL7.

python34-sqlalchemy.x86_64 1.1.3-1.el7 epel

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

On 18 May 2017 at 08:05, Martin Juhl mj@casalogic.dk wrote:

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...

I thought someone sent this earlier, but I was mistaken. To become a Fedora/EPEL packager you should start here:

https://fedoraproject.org/wiki/Join_the_package_collection_maintainers

This outlines the steps and rules you will need to go through to become a package maintainer. The packages will need to follow items here:

https://fedoraproject.org/wiki/Package_maintenance_guide

Regards

Martin

----- Original meddelelse ----- Fra: "Kevin Fenzi" kevin@scrye.com Til: "epel-devel" epel-devel@lists.fedoraproject.org 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@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org

it is python34-sqlalchemy

On Thu, May 11, 2017 at 12:21 PM, R P Herrold herrold@owlriver.com wrote:

On Wed, 3 May 2017, Orion Poplawski wrote:

...

...

python3-flask: python3-itsdangerous python3-sqlalchemy

again, already in EPEL7

ehh? -- I see no python3-sqlalchemy in EPEL-7

[herrold@centos-7 ~]$ date ; sudo yum -q clean all Thu May 11 12:19:59 EDT 2017 [herrold@centos-7 ~]$ date ; sudo yum -q install python3-sqlalchemy Thu May 11 12:20:04 EDT 2017 Error: Nothing to do [herrold@centos-7 ~]$ sudo rpm -V epel-release [herrold@centos-7 ~]$

-- Russ herrold _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org