Bug 2144673 - Please branch and build python-PyMySQL in epel9
Summary: Please branch and build python-PyMySQL in epel9
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-PyMySQL
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Julien Enselme
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2032550
TreeView+ depends on / blocked
 
Reported: 2022-11-22 00:43 UTC by Jonathan Wright
Modified: 2023-02-11 05:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-02-11 05:33:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jonathan Wright 2022-11-22 00:43:31 UTC
Please branch and build python-PyMySQL in epel9.

If you do not wish to maintain python-PyMySQL in epel9,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/python-PyMySQL/addgroup
and grant it commit access, or collaborator access on epel* branches.

I would also be happy to be a co-maintainer (FAS: jonathanspw).

I can be the primary contact for EPEL (FAS: jonathanspw).

Comment 1 Julien Enselme 2022-11-23 09:32:20 UTC
When I tried to create the branch, I got this message: "Could not execute request_branch: This package is already an EL package, therefore it cannot be in EPEL. If this is a mistake or you have an exception, please contact the Release Engineering team." So I think the package is already available.

Comment 2 Carl George 🤠 2023-02-11 05:33:18 UTC
I confirmed that python3-PyMySQL is available in RHEL 9 AppStream, therefore is ineligible for EPEL 9 by policy.  Looking at the bug that led to this bug's creation, it seems this error message was misinterpreted.

No matching package to install: 'python3dist(pymysql) >= 1.0.2'

The package is available but is only at version 0.10.1.


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