Bug 1913141 - Please build python-typeshed for EPEL 8
Summary: Please build python-typeshed for EPEL 8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-typeshed
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: EPELPackagersSIG
TreeView+ depends on / blocked
 
Reported: 2021-01-06 05:27 UTC by Davide Cavalca
Modified: 2021-05-21 02:50 UTC (History)
4 users (show)

Fixed In Version: python-typeshed-0.1-0.20191011git2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-21 02:50:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Davide Cavalca 2021-01-06 05:27:29 UTC
python-typeshed is already available in EPEL 7 but not in EPEL 8. I just tried a mock build and it worked straight away without any changes, could you please add it? Thanks!

Comment 1 Davide Cavalca 2021-05-05 20:14:55 UTC
Any update on this? Also happy to do it myself if you prefer, just request the branch and add me as a co-maintainer in case (FAS: dcavalca). Thanks!

Comment 2 Gwyn Ciesla 2021-05-05 20:27:26 UTC
I'll get this out.

Comment 3 Fedora Update System 2021-05-05 20:31:40 UTC
FEDORA-EPEL-2021-b58b10e474 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b58b10e474

Comment 4 Fedora Update System 2021-05-06 01:06:07 UTC
FEDORA-EPEL-2021-b58b10e474 has been pushed to the Fedora EPEL 8 testing repository.

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

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

Comment 5 Fedora Update System 2021-05-21 02:50:52 UTC
FEDORA-EPEL-2021-b58b10e474 has been pushed to the Fedora EPEL 8 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.