Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1828188
Commented but haven't voted yet: kparal, coremodule
The votes have been last counted at 2020-09-08 21:18 UTC and the last processed comment was #comment-677162
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review
I am not very clever from this bug - it has been created during the release cycle of Fedora 32, now it has been reopened but its target says Rawhide and again some wrong behaviour is reported for F32 by @vtrefny. We should be blocking F33 but I could not find an F33 target anywhere.
it has been created during the release cycle of Fedora 32,
But with a Rawhide install at that time, which matches F33 now.
its target says Rawhide
It most probably affects both F33 and Rawhide. It doesn't really matter what's in the Version field for the purpose of a blocker discussion. But nobody reproduced it for a while, so the million dollar question is: "Does it still happen?"
BetaBlocker -1
Cannot reproduce the bug with the latest compose.
AGREED RejectedBetaBlocker
Discussed during the 2020-09-08 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker" was made as there's no indication this bug is still present in current F33 (or Rawhide), the reporter tried and cannot reproduce again, and neither can anyone else. It should probably be closed, but we definitely reject it as a blocker for now.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-09-08/f33-blocker-review.2020-09-08-16.00.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.