I can request all the branches and build it for older Fedora releases. Do you plan to maintain it in EPEL?

> Do you plan to maintain it in EPEL?

If necessary I guess I will unless the maintainers for `python-importlib-resources` steps in. Of course this propagates to the other `jaraco` packages needed.

Why do you need the importlib-resources to be in EPEL 9? AFAIU the features from importlib-resources are merged to CPython standard library and Centos stream 9 contains Python 3.9, 3.11, and 3.12 so projects should be compatible with the standard library unless targeting features from 3.13.

Nonetheless, if you want something to be available in EPEL, you should also request all dependant packages to be there. Some maintainers will happily build and maintain their packages in EPEL, some (like me) give you the rights to build and maintain their packages in EPEL so they don't have to commit to this.

The usual workflow is to track down all the packages that need to be added to EPEL first. Open bugzillas for them and then one more bugzilla for the main package (python-importlib-resources in this case) and make all the bugzillas block the main one. The list might be growing and this makes it easy to track the progress.

From the upstream metadata:

Runtime deps:

dependencies = [
	"zipp >= 3.1.0; python_version < '3.10'",
]

Test deps:

test = [
	# upstream
	"pytest >= 6, != 8.1.*",
	"pytest-checkdocs >= 2.4",
	"pytest-cov",
	"pytest-mypy",
	"pytest-enabler >= 2.2",
	"pytest-ruff >= 0.2.1; sys_platform != 'cygwin'",

	# local
	"zipp >= 3.17",
	"jaraco.test >= 5.4",
]

Doc deps:

doc = [
	# upstream
	"sphinx >= 3.5",
	"jaraco.packaging >= 9.3",
	"rst.linker >= 1.9",
	"furo",
	"sphinx-lint",

	# tidelift
	"jaraco.tidelift >= 1.4",

	# local
]

I guess it will be possible to ignore some of those like pytest-cov and pytest-mypy. On the other hand, python-zipp requires jaraco-functools and jaraco-test to build, jaraco-test requires these to build:

python3dist(jaraco-collections)
python3dist(jaraco-context)
python3dist(jaraco-functools)

and that's just the beginning. The tree might be big at the end and there might also be conflicts with centos stream 9 content.

> Why do you need the importlib-resources to be in EPEL 9? AFAIU the features from importlib-resources are merged to CPython standard library and Centos stream 9 contains Python 3.9, 3.11, and 3.12 so projects should be compatible with the standard library unless targeting features from 3.13.

There are features and bug fixes that are introduced in `importlib-resources` but never backported because compatibility package exists. In my case, `MultiplexedPath` is broken prior to Python 3.12, so I need to this package for EPEL9. See https://bugzilla.redhat.com/show_bug.cgi?id=2303229 for more details. The original issue is this PR on `tmt` [1]

I need to make a review request, but I am still waiting on the original packagers to see if they will pick it up

[1]: https://github.com/teemtee/tmt/pull/2946

I've added you as a maintainer for python-jaraco-test for all epel* branches.

Thanks. Still working on getting `jaraco.test` to work [1]. I am stuck at the `test.support` issue which surprisingly affects epel as well [2].

[1]: https://github.com/LecrisUT/importlib-resources-rpmspec
[2]: https://github.com/jaraco/jaraco.test/issues/6#issuecomment-2283519396

FEDORA-EPEL-2024-34fb660455 (python-backports-tarfile-1.2.0-1.el9, python-jaraco-context-6.0.1-3.el9, and 1 more) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-34fb660455

FEDORA-EPEL-2024-34fb660455 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-2024-34fb660455

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

FEDORA-EPEL-2024-34fb660455 (python-backports-tarfile-1.2.0-1.el9, python-jaraco-context-6.0.1-3.el9, and 1 more) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.