FinalBlocker -1

Proprietary client software can't really block Fedora releases. The criteria we have for VPNs say "Using the default network configuration tools for the console and for release-blocking desktops, it must be possible to establish a working connection to common OpenVPN, openconnect-supported and vpnc-supported VPN servers with typical configurations."

@adamwill Yes, I can also confirm that it works with the openconnect plugin for NetworkManager. In this respect I can share your assessment regarding the 3rd party VPN client. However, I don't know if this bug affects other important software as well.

Maybe this proposal could become a "freeze exception" if there is a working fix in 2239304.

Proprietary client software can't really block Fedora releases

Nitpick: When Chrome and others couldn't be installed in the past, we had a FESCo-approved blocker. So technically there's a way.

But yes, in this particular case, we specify which VPNs must work and Cisco Anyconnect is not one of them.

FinalBlocker -1

Maybe this proposal could become a "freeze exception" if there is a working fix in 2239304.

Yes. If the fix materializes soon, feel free to propose it, thanks.

I agree with the above:

FinalBlocker -1

FinalBlocker -1

Since a solution is apparent in 2239304 (reverting the triggering code change in glibc), I have proposed the bug as a "Freeze Exception".

FinalFE +1

If my summary in https://bugzilla.redhat.com/show_bug.cgi?id=2239304#c34 is correct, I'm:

FinalBlocker -1
FinalFE +1

AGREED RejectedFinalBlocker

The following votes have been closed:

• Rejected FinalBlocker (+0, 0, -4)
  • -1 by adamwill, kparal, lruzicka, sumantrom

FinalFE +1

AGREED AcceptedFinalFE

The following votes have been closed:

• Accepted FinalFreezeException (+3, 0, -0)
  • +1 by jnk0, adamwill, asciiwolf

Release F39 is no longer tracked by BlockerBugs, closing this ticket.