Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2273942 Information from BlockerBugs App: <img alt="2273942" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2273942" />
Commented but haven't voted yet: frantisekz
The votes have been last counted at 2024-04-08 20:08 UTC and the last processed comment was #comment-904694
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
I think this one is more like a FE than a blocker.
FinalFE +1
AGREED AcceptedFinalFE AGREED RejectedFinalBlocker
Discussed during the 2024-04-08 blocker review meeting [1]:
It's arguably a conditional criterion violation, but only with a fairly unusual condition (manually-created user account with UID >1000 and no login shell). We do grant it an FE, though; if we do want to change the default list of shells that cause a user to be hidden it seems reasonable to do that for release.
[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-04-08/f40-blocker-review.2024-04-08-16.00.html
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F40 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.