Bug 2397294 - fapolicyd: Please unstuck the Fedora 43 Bodhi updates
Summary: fapolicyd: Please unstuck the Fedora 43 Bodhi updates
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fapolicyd
Version: 43
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Grubb
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYC3.14rc3
TreeView+ depends on / blocked
 
Reported: 2025-09-22 10:58 UTC by Karolina Surma
Modified: 2025-09-29 15:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-09-29 15:14:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Karolina Surma 2025-09-22 10:58:07 UTC
Dear package maintainer,

Due to reasons described in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/XO5QGOXBWHFG7AOGDQBG23AQDS2MDTWI/ a rebuild of fapolicyd was needed in Fedora 43 and 44.

During the mass rebuild the package built successfully, but now appears to be stuck on gating in Bodhi.

https://bodhi.fedoraproject.org/updates/?packages=fapolicyd

Please, determine the reason for this yourself and unstuck the Bodhi updates, ideally before the Fedora 43 Final freeze (2025-10-07).

Thank you. Let me know if you need help.

Comment 1 Steve Grubb 2025-09-22 21:56:42 UTC
This package is not stuck on gating, it is in testing. Since this is not critical path, it can just age out if no one gives it karma.

Comment 2 Steve Grubb 2025-09-22 21:59:42 UTC
I gave it karma. It can now be pushed to stable.

Comment 3 Karolina Surma 2025-09-29 14:19:41 UTC
Hello. This is a bulk comment.

This package still needs to be rebuilt and/or shipped with Python 3.14.0rc3+ bytecode in Fedora 43.

The Final Freeze of Fedora 43 is scheduled to start next week. Please prioritize this bugzilla accordingly.

Thanks.

Comment 4 Petr Lautrbach 2025-09-29 15:14:39 UTC
This package is not related to Python 3.14.0rc+ bytecode change in Fedora


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