Bug 2100049 - Please build esmtp for epel9
Summary: Please build esmtp for epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: esmtp
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2042486 2101784
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-22 09:20 UTC by david lindstedt
Modified: 2022-07-30 02:32 UTC (History)
4 users (show)

Fixed In Version: esmtp-1.2-19.el9
Clone Of:
Environment:
Last Closed: 2022-07-30 02:32:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description david lindstedt 2022-06-22 09:20:29 UTC
Comment 1 Jaroslav Škarvada 2022-06-23 11:14:04 UTC 
https://pagure.io/releng/fedora-scm-requests/issue/45206
Comment 2 Jaroslav Škarvada 2022-06-28 11:04:35 UTC 
It requires libesmtp.
Comment 3 Jaroslav Škarvada 2022-06-28 11:08:17 UTC 
(In reply to Jaroslav Škarvada from comment #2)
> It requires libesmtp.

Created bug 2101784, but the component is orphaned. We need to find a maintainer first.
Comment 4 Jaroslav Škarvada 2022-06-30 10:10:38 UTC 
It seems there is already bug 2042486. I think I could take it.
Comment 5 Fedora Update System 2022-07-21 10:02:55 UTC 
FEDORA-EPEL-2022-dbf5200b44 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-dbf5200b44
Comment 6 Fedora Update System 2022-07-22 06:07:32 UTC 
FEDORA-EPEL-2022-dbf5200b44 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-dbf5200b44

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2022-07-30 02:32:54 UTC 
FEDORA-EPEL-2022-dbf5200b44 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.