Ubuntu
openconnect package

OpenConnect upstream connection is still not correct

Asked by Mike Miller

Original reporter of https://answers.launchpad.net/launchpad/+question/205338 seems satisfied but I think this is still a problem as I posted in a comment on that question, so asking again.

OpenConnect is its own entity separate from NetworkManager, I don't think linking https://launchpad.net/ubuntu/+source/openconnect to https://launchpad.net/network-manager-openconnect is correct. Also notice that https://launchpad.net/openconnect still links to the openconnect package in previous releases of Debian and Ubuntu, and vice versa, they still link to it.

If there is to be any upstream connection for https://launchpad.net/ubuntu/+source/openconnect, it should be one for OpenConnect itself. Ideally this would be located at https://launchpad.net/openconnect because it is the same name as the package in Debian and Ubuntu. Is it out of the question to relocate or move the project that is there now?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu openconnect Edit question
Assignee:
No assignee Edit question
Solved by:
Max Bowsher
Solved:
Last query:
Last reply:
Revision history for this message
Max Bowsher (maxb) said : 		#1

I've removed all the erroneous links.

Whilst it is true that https://launchpad.net/openconnect is incredibly inactive, I'm not comfortable with forcing a change of project id.

You are, of course, welcome to register a project record for the OpenConnect VPN software under a name such as https://launchpad.net/openconnect-vpn or similar, or to contact the registrant of the 'openconnect' project to ask whether they would be willing to cede the id as their project doesn't seem to actually be using Launchpad in any substansive way.

Should the registrant prove uncontactable, Canonical staff might possibly prove willing to intercede and free up the id anyway - if you find yourself wanting to ask for that, do so as a Launchpad question on the "Launchpad itself" project.

Revision history for this message
Best Max Bowsher (maxb) said : 		#2

I've removed all the erroneous links.

Whilst it is true that https://launchpad.net/openconnect is incredibly inactive, I'm not comfortable with forcing a change of project id.

You are, of course, welcome to register a project record for the OpenConnect VPN software under a name such as https://launchpad.net/openconnect-vpn or similar, or to contact the registrant of the 'openconnect' project to ask whether they would be willing to cede the id as their project doesn't seem to actually be using Launchpad in any substansive way.

Should the registrant prove uncontactable, Canonical staff might possibly prove willing to intercede and free up the id anyway - if you find yourself wanting to ask for that, do so as a Launchpad question on the "Launchpad itself" project.

Revision history for this message
Mike Miller (mtmiller) said : 		#3

Thanks Max Bowsher, that solved my question.