Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2073708 ** Information from BlockerBugs App:
Commented but haven't voted yet: frantisekz
The votes have been last counted at 2022-04-11 17:15 UTC and the last processed comment was #comment-791746
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
FinalFE +1
This doesn't feel blockery to me, it seems to require either a custom (though I expect incredibly common) RHEL disk layout, or a no longer supported for upgrades Fedora install. I'm not sure if LVM with separate home volume was used anywhere else.
FinalBlocker -1 FinalFE +1
This is not just about RHEL, a similar layout was created with Fedora by a different user. If I read this correctly, this affects both guided a custom partitioning. So it violates these: https://fedoraproject.org/wiki/Fedora_36_Beta_Release_Criteria#Guided_partitioning https://fedoraproject.org/wiki/Fedora_36_Beta_Release_Criteria#Custom_partitioning and probably even this: https://fedoraproject.org/wiki/Basic_Release_Criteria#Disk_layouts and of course also this: https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Disk_layouts
I find it interesting that it happens on KDE but not on GNOME. Perhaps some automounter daemon interfering?
FinalBlocker +1
Okay, I both misread the ticket, and the criteria. Clearly violates the Disk layouts criteria.
AGREED AcceptedFinalBlocker Decided on meeting https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-04-11/f36-blocker-review.2022-04-11-16.00.log.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.