#1886 [python-cairocffi] python-cairocffi: FTBFS in Fedora 43 (test fails due to a gdk-pixbuf2 problem) | rhbz#2389370
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2389370 **
Information from BlockerBugs App:
2389370

Current vote summary

Commented but haven't voted yet: churchyard

The votes have been last counted at 2025-09-01 09:31 UTC and the last processed comment was #comment-984020

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


BetaFE +1

Hmm, sure, why not. But I thought we only care about FTI, and FTBFS can wait for a regular update? (Unless this crashes during runtime, or something, haven't tried it).

BetaFE +1

Ah. I was assuming it was a "it's FTI because it didn't build for Python 3.14" situation, but this one did build for Python 3.14.

The issue here appears to be that we want it rebuilt for "Python 3.14.0rc2 bytecode". I'm not sure how critical that is. @churchyard can you clarify? Thanks.

BetaFE +1

Not critical. As well as not dangerous to ship. So I thought, let's get it over with.

I'm not seeing any reason for this to be an FE.

BetaFE -1

Not critical. As well as not dangerous to ship. So I thought, let's get it over with.

This works as long as not too many package maintainers use the same approach :-) Each FE review takes a part of our limited time, so I'd prefer to keep it to the most important only, which really need to break through the freeze.

BetaFE -1

Sorry for taking up your time. I withdraw this request.

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

Release F43 is no longer tracked by BlockerBugs, closing this ticket.

Metadata