On 21/01/2022 22:23, Felix Schwarz wrote:

Hi,

the packaging guidelines have a few excemptions for the package review process [1]. I'm working on updating certbot to Python 3 in EPEL 7 (rhbz 1797129, [2]). I need some additional Python 3 packages in EPEL 7 to achieve that and my question is which of these packages should get a proper review.


A) python3-augeas
https://bugzilla.redhat.com/show_bug.cgi?id=2043744

This is mostly the Fedora spec with just on additional bugfix (already upstream).


B) python3-josepy
intended spec file: https://github.com/FelixSchwarz/certbot-epel7-python3/blob/rawhide/python3-josepy/python-josepy.spec

I did not want to upgrade the existing EPEL 7 package as the required version is Python 3 only. We can not use some newer macros like %pytest but otherwise the spec is the same as in Fedora.


C) python3-boto3
python-boto3 (Python 2) version is in RHEL and won't get a Python3 package.
intended spec file: https://github.com/FelixSchwarz/certbot-epel7-python3/blob/rawhide/python3-boto3/python3-boto3.spec

The spec file is very close to the RHEL spec file just with some customizations removed.

Should I try to get reviews for each of the three packages or can I skip some of these according to the Fedora review policy?

Felix



[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/#_package_review_process
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1797129

A bit o/t, but will you be updating the python2-certbot-dns-* packages as well?
_______________________________________________
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to