Bug 2062420 - Branch and build python-poetry-core in EPEL 9
Summary: Branch and build python-poetry-core in EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-poetry-core
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2062419
Blocks: 2048762
TreeView+ depends on / blocked
 
Reported: 2022-03-09 18:19 UTC by Michel Lind
Modified: 2022-07-19 09:36 UTC (History)
3 users (show)

Fixed In Version: python-poetry-core-1.0.7-2.el9
Clone Of:
Environment:
Last Closed: 2022-03-13 18:39:44 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Michel Lind 2022-03-09 18:19:50 UTC 
Needed by python-libtmux; no other missing BRs.

Tested by building locally with https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-87aaf84942
Comment 1 Michel Lind 2022-03-09 18:21:43 UTC 
$ fedpkg request-branch --repo python-poetry-core epel9
https://pagure.io/releng/fedora-scm-requests/issue/42851
Comment 2 Fedora Update System 2022-03-09 21:34:22 UTC 
FEDORA-EPEL-2022-98b1807e3e has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-98b1807e3e
Comment 3 Fedora Update System 2022-03-11 14:47:00 UTC 
FEDORA-EPEL-2022-98b1807e3e 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-98b1807e3e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2022-03-13 18:39:44 UTC 
FEDORA-EPEL-2022-98b1807e3e has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 5 Miro Hrončok 2022-07-19 09:36:23 UTC 
Michel, since you requested this branch without talking to the package maintainers, I am making you the EPEL point of contact.
Note You need to log in before you can comment on or make changes to this bug.