Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2081321 Information from BlockerBugs App: <img alt="2081321" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2081321" />
The votes have been last counted at 2022-05-03 17:07 UTC and the last processed comment was #comment-795683
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
As the reproducer specifically claims to sudo dnf -y install NetworkManager-strongswan NetworkManager-strongswan-gnome, I believe that this does not apply to the chosen criterion "Default functionality" as it is not installed by default.
sudo dnf -y install NetworkManager-strongswan NetworkManager-strongswan-gnome
FinalBlocker -1
There is a very similar bug with NetworkManager-ssh (1, 2), caused by the transition to GTK4.
NetworkManager-ssh
The reason to reject the bug as blocker was that ssh-VPN is apparently not very common, and not that the required packages are not part of the default install.
So how commonly used is strongswan would be the question if we are applying the same logic.
NetworkManager-strongswan and NetworkManager-strongswan-gnome isn't shipped with the iso, I don't think this qualifies as blocker. FinalBlocker -1
FinalBlocker -1 FinalFE +1
AGREED RejectedFinalBlocker AcceptedFinalFE
The following votes have been closed:
Actually, since it's not shipped on the media, I don't see much point in the FE?
REVOTE FinalFreezeException
FinalFE -1
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.