Bug 2041142 - Please branch and build certbot in epel9
Summary: Please branch and build certbot in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: certbot
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nick Bebout
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2036380 (view as bug list)
Depends On: 2077441 2032588 2036234 2041159 2076197 2077442 2077443 2077444
Blocks: 2041148 2041143 2041144 2041145 2041146 2041147 2041149 2041150 2041151 2041152 2041153 2041154 2041155 2041156 2041157 2041158
TreeView+ depends on / blocked
 
Reported: 2022-01-16 06:26 UTC by Matthew Davis
Modified: 2023-08-27 20:25 UTC (History)
12 users (show)

Fixed In Version: certbot-1.27.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-03 02:58:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Matthew Davis 2022-01-16 06:26:18 UTC
Please branch and build certbot in epel9

Comment 1 Felix Schwarz 2022-01-16 13:49:35 UTC
*** Bug 2036380 has been marked as a duplicate of this bug. ***

Comment 2 Gerwin Krist 2022-04-07 15:01:33 UTC
Hi! Is there any way we can get this one rolling? :-) I can offer some limited help (testing is one of them)

Comment 3 Felix Schwarz 2022-04-07 19:29:18 UTC
I think what's mostly needed is someone who drives this. I don't have time for EPEL 9 (see bug 2041159 comment 1).


Steps towards certbot in EPEL 9

- build the packages in a COPR repo to verify all required dependencies are available
- file bugs and link them to the appropriate certbot component (I think the dependency tree in bugzilla is missing quite several items)
- bonus: clarify with upstream if they are planning to change something with regards to the current plugin structure (e.g. deprecating some plugins). I think that each new EPEL release should be a point in time where each maintainer really thinks hard about his/her workload and if maintaining the package in EPEL X is doable. As a first step we could also limit support in EPEL 9 to python-acme, certbot, certbot-nginx and certbot-apache.

Comment 4 Matthew Davis 2022-04-07 19:46:55 UTC
There is an outstanding blocked dependency[1] preventing the from moving forward.  I submitted a pull request that was accepted to but the package has not been branched and built yet.

Once the dependency is build, python-acme will can be branched and built so this request can move forward.

Comment 5 Matthew Davis 2022-04-07 19:48:08 UTC
(In reply to Matthew Davis from comment #4)
> There is an outstanding blocked dependency[1] preventing the from moving
> forward.  I submitted a pull request that was accepted to but the package
> has not been branched and built yet.
> 
> Once the dependency is build, python-acme will can be branched and built so
> this request can move forward.

1 https://bugzilla.redhat.com/show_bug.cgi?id=2044030

Comment 6 Fedora Update System 2022-05-25 21:47:39 UTC
FEDORA-EPEL-2022-53d990001a has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-53d990001a

Comment 7 Fedora Update System 2022-05-26 01:46:01 UTC
FEDORA-EPEL-2022-53d990001a has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-53d990001a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-05-27 01:50:40 UTC
FEDORA-EPEL-2022-53d990001a has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-53d990001a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-06-03 02:58:55 UTC
FEDORA-EPEL-2022-53d990001a has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Clint Goudie 2023-08-27 20:25:15 UTC
I can confirm that 2.6.0 fixed this for me.


Note You need to log in before you can comment on or make changes to this bug.