Ubuntu
network-manager-openconnect package

  1. Bug #1969734
  2. Comment #51

Comment 51 for bug 1969734

Revision history for this message
Steve Langasek (vorlon) wrote :

I am once again marking this bug incomplete.

It was marked 'confirmed' again after a set of changes to the bug description. But still, NOWHERE IN THE BUG HAS THE QUESTION BEEN ANSWERED:

Could a user, who has configured openconnect directly rather than using NetworkManager-openconnect, have a configuration which relies on the current (incorrect) behavior, and that configuration will then be broken as a result of this SRU?

That question needs a clear yes or no answer. If the answer is yes, then there either needs to be mitigation of this as part of a patch, or a rationale for why it's somehow acceptable to break the user's VPN configuration on upgrade (such as: that config wouldn't actually work and would be buggy in other ways).

It has wasted a lot of SRU Team time trying to get an answer to this question. If I find that this bug has been set back to 'confirmed' again without this question being clearly answered, I am going to reject the SRU.