Bug 1948518 - Pyzor 1.0 for EPEL 7
Summary: Pyzor 1.0 for EPEL 7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: pyzor
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-12 10:54 UTC by Aldo Necci
Modified: 2022-01-01 00:42 UTC (History)
5 users (show)

Fixed In Version: pyzor-1.0.0-28.20200530gitf46159b.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-01 00:42:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Aldo Necci 2021-04-12 10:54:17 UTC 
May someone upgrade pyzor to version 1.0 for EPEL 7?
Comment 1 Aldo Necci 2021-12-20 13:07:26 UTC 
This request has been opened more than 6 mounths ago. May we get some feedback about what the difficulties are to updating pyzor?
Comment 2 Robert Scheck 2021-12-23 14:57:55 UTC 
Honestly, I'm not sure if it's worth having pyzor in EPEL at all these days when looking to bug #2026772 comment #1 and the lack of upstream development (or maintenance) activity at https://github.com/SpamExperts/pyzor.
Comment 3 Fedora Update System 2021-12-23 17:43:13 UTC 
FEDORA-EPEL-2021-ee8a110aeb has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-ee8a110aeb
Comment 4 Fedora Update System 2021-12-24 02:06:08 UTC 
FEDORA-EPEL-2021-ee8a110aeb has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-ee8a110aeb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2022-01-01 00:42:12 UTC 
FEDORA-EPEL-2021-ee8a110aeb has been pushed to the Fedora EPEL 7 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.