Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2010061 ** Information from BlockerBugs App:
Commented but haven't voted yet: adamwill, zbyszek
The votes have been last counted at 2021-10-06 14:28 UTC and the last processed comment was #comment-756673
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)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
This would be a blocker if python3-jwt+crypto were in any release-blocking default package set, but the bug report doesn't actually say that it is, and the openQA upgrade tests are passing. @zbyszek , what "release-blocking package set" includes python3-jwt+crypto by default?
Yeah, it's not required by anything in the release-blocking default package set. But it can be a freeze exception though?
FinalBlocker -1
The reason given for the blocker seems bogus.
FinalFE -1
The problem only happens with python-cryptography from updates-testing (now even unpushed).
The update that causes the break has been obsoleted 20 hrs ago https://bodhi.fedoraproject.org/updates/FEDORA-2021-122248d76a So I follow churchyard FinalFE -1 FinalBlocker -1
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F35 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.