Bug 2345927 - Please branch and build python-jeepney in epel10
Summary: Please branch and build python-jeepney in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-jeepney
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Göran Uddeborg
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2351418 2345503 2351308
Blocks: 2355197 2319785 2345928
TreeView+ depends on / blocked
 
Reported: 2025-02-15 17:09 UTC by Romain Geissler
Modified: 2025-03-26 22:43 UTC (History)
4 users (show)

Fixed In Version: python-jeepney-0.9.0-3.el10_1
Clone Of:
Environment:
Last Closed: 2025-03-13 02:49:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure 72365 0 None None None 2025-02-17 09:37:30 UTC

Description Romain Geissler 2025-02-15 17:09:25 UTC
Hi,

Please branch and build python-jeepney in epel10.

Comment 1 Göran Uddeborg 2025-02-17 10:16:33 UTC
Branched and ready when the upstreams packages become available.

Comment 2 Romain Geissler 2025-03-08 11:19:24 UTC
If we merge https://src.fedoraproject.org/rpms/python-jeepney/pull-request/5 and upgrade the EPEL 10 branch to the rawhide branch content, then we no longer need the python-async-timeout dependency.

Comment 3 Göran Uddeborg 2025-03-11 09:46:46 UTC
Thanks. I've added the relevant patches (skipping the dbus tests I recently added in rawhide, at least for now).

Comment 4 Ben Beasley 2025-03-11 11:30:38 UTC
Reposting from https://bugzilla.redhat.com/show_bug.cgi?id=2351308#c4:

Requiring flit-core >=3.11 was a recent change in jeepney upstream, released in 0.9.

https://gitlab.com/takluyver/jeepney/-/commit/7a29c4757a742fcd8db36d6e0cff04f7f10e65d3

You could base an EPEL10 branch of python-jeepney on the current F42, https://src.fedoraproject.org/fork/music/rpms/python-jeepney/c/7f11ae8d3ca46c1e1754d081071d7de2cf544a26, although you would then need python-async-timeout (in addition to python-pytest-trio, bug 2345503). This works; I tried it locally.

You could also base an EPEL10 branch of python-jeepney on the current Rawhide, if you add a patch reverting the upstream commit linked above. You would then also need dbus-test-runner, or you would need to revert https://src.fedoraproject.org/fork/music/rpms/python-jeepney/c/013e00517f242739b1d359b307d82524a1d2b500 for EPEL10. Again, I tested both approaches locally.

Comment 5 Göran Uddeborg 2025-03-11 21:04:19 UTC
As mentioned in comment 3, I did exclude the DBus tests and dependency when picking patches from the rawhide to the epel10 branch. I have asked for a EPEL10 build of dbus-test-runner, but I don't want to block this issue waiting for that.

The patch introducing the 3.11 dependency does indeed seem simple enough. I think I dare do as you suggest and undo it for now.

Looking a bit closer, I note that the trio tests will anyway not be run without a DBus. So for now I'll omit that dependency, only include trio itself to meet the import during testing. That makes jeepney build on RHEL10, if with slightly unsatisfactory testing.

Comment 6 Fedora Update System 2025-03-11 21:16:15 UTC
FEDORA-EPEL-2025-de0d8e3448 (python-jeepney-0.9.0-3.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-de0d8e3448

Comment 7 Fedora Update System 2025-03-12 02:24:03 UTC
FEDORA-EPEL-2025-de0d8e3448 has been pushed to the Fedora EPEL 10.1 testing repository.

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

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

Comment 8 Fedora Update System 2025-03-13 02:49:46 UTC
FEDORA-EPEL-2025-de0d8e3448 (python-jeepney-0.9.0-3.el10_1) has been pushed to the Fedora EPEL 10.1 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.