On Tue, Dec 13, 2016 at 11:56:28AM +0100, Aurelien Bompard wrote: > Hey people, > > I'm in a situation that I don't think is covered by the guidelines. Here's > the thing: RHEL/CentOS ships some python packages in their Python 2 > version, but not for Python 3 since RHEL/CentOS does not ship Python 3. > > Let's take the example of python-zope-interface. I need the python3 > version, so I thought I'd adapt the existing python-zope-interface package > we have to only build the Python 3 version in EPEL. Then Kevin told me > that this was a bad idea because koji (I think it was koji?) works on > source packages, and won't like having two python-zope-interface packages, > one from RHEL/CentOS and one from EPEL. > So I built a python3-zope-interface package that only builds the Python3 > version. It got accepted, it builds fine, but now I realize that I don't > want this package to be built for Rawhide, since Rawhide already has the > Python 3 version of Zope Interface (built from the main package, as > usual). > I removed the spec file from the master branch in git and put a README > explaining all that, but I wonder if our release engineering process will > like that. Do I need a special exception, as we have for orphan packages, > so it does not error out? No that should be no problem, you can basically just retire the master branch and keep only the epel one. We have this for other packages, such as: https://admin.fedoraproject.org/pkgdb/package/rpms/python-sqlalchemy0.8/ or https://admin.fedoraproject.org/pkgdb/package/rpms/python-sqlalchemy0.7/ back when we needed them in infra on rhel6. Pierre _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
