Bug 2224032 - [RFE:EPEL9] EPEL9 branch for python-markdown
Summary: [RFE:EPEL9] EPEL9 branch for python-markdown
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-markdown
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-19 15:58 UTC by Martin Hoyer
Modified: 2023-08-03 13:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-03 13:24:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martin Hoyer 2023-07-19 15:58:13 UTC
Description of problem:
python3-markdown is a dependency of tmt, which is being build for EPEL9, currently it relies on an older package in CRB repo, which is not ideal.

Since python-markdown is noarch and does not have any dependency itself, would you consider start building EPEL9 packages?

el9 having Python 3.8, the specfile would need to include python3-importlib-metadata (also from epel) as a dependency.

Comment 1 Thomas Moschny 2023-07-31 07:43:44 UTC
It seems setuptools >= 61.2 is a requirement, see:
https://github.com/Python-Markdown/markdown/blob/f99f176d248d0e472b0960d06a7aaf649bb1da25/pyproject.toml#L3

This is currently not available in el9 afaict, there is only version 53.

Comment 2 Martin Hoyer 2023-07-31 11:06:13 UTC
(In reply to Thomas Moschny from comment #1)
> It seems setuptools >= 61.2 is a requirement, see:
> https://github.com/Python-Markdown/markdown/blob/
> f99f176d248d0e472b0960d06a7aaf649bb1da25/pyproject.toml#L3
> 
> This is currently not available in el9 afaict, there is only version 53.

Thanks for looking into it Thomas.
That is a recent change introduced in 3.4.2.
3.4.1 is still using setup.py and setuptools>=36.6.

I've learned however that it might not be allowed to have a package in both CRB and EPEL repos simultaneously.

Comment 3 Martin Hoyer 2023-07-31 11:22:11 UTC
(In reply to Martin Hoyer from comment #2)
> I've learned however that it might not be allowed to have a package in both
> CRB and EPEL repos simultaneously.

I've opened bz#2227766 to see if it can be updated in CRB.

Comment 4 Thomas Moschny 2023-08-03 06:58:51 UTC
As that bz has been declined, are there options left?

Maybe bundling is an option if tmt really depends on a specific version.

Comment 5 Martin Hoyer 2023-08-03 11:08:25 UTC
(In reply to Thomas Moschny from comment #4)
> As that bz has been declined, are there options left?
> 
> Maybe bundling is an option if tmt really depends on a specific version.

I honestly don't know if there is any other option, as I don't fully understand the CRB/EPEL goals and workflows. Feel free to close this though :)

tmt does not rely on specific version afaik, but should it implement a tighter version control for it's dependencies, it's either locking the python-markdown to older versions everywhere, or have a EPEL9-only patch.

Comment 6 Thomas Moschny 2023-08-03 13:24:41 UTC
Ok, so closing here. Feel free to re-open if needed.


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