Bug 158691

Summary:	NetworkManager-gnome required by vpn providing packages
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Forgotten User wMtT3MV6AL <forgotten_wMtT3MV6AL>
Component:	Network	Assignee:	Robert Love <rml>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	felix, forgotten_NWmiVNctto
Version:	Beta 7
Target Milestone:	RC 1
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User wMtT3MV6AL 2006-03-16 16:32:18 UTC

NetworkManager-gnome is required for the following packages:

NetworkManager-novellvpn
NetworkManager-openvpn
NetworkManager-vpnc

NetworkManager-kde uses its nm-vpn-properties, but this is only needed if one of the mentioned packages is installed.

Comment 1 JP Rosevear 2006-03-19 15:34:18 UTC

Well, it links to gnome-keyring and the like, so the package division is appropriate.  Timo, do you have any proposal for handling this?

Comment 2 Timo Hoenig 2006-03-19 19:23:16 UTC

The missing bit is a "Requires: NetworkManager-gnome" for the NM-VPN packages.  The configuration dialog for all of the three packages (nm-vpn-properties) comes with NetworkManager-gnome.

Comment 3 JP Rosevear 2006-03-20 01:00:52 UTC

This will pull a lot of gnome deps for kde desktops though.

Comment 4 Robert Love 2006-03-20 05:10:15 UTC

One solution is for NetworkManager-kde to provide its own nm-vpn-properties and to require that file in each vpn subpackage.  But then NetworkManager-gnome and NetworkManager-kde cannot both be installed, so that is a nonstarter.

Another idea is to make a new NetworkManager-vpn-properties package that provides just nm-vpn-properties, but that will pull in nearly as many dependencies and require a new package late in Code10 -- not to mention a new package for a single file.

I don't think there is an easy solution.  But I also don't grok exactly what the original bug reporter is saying is the bug.

Comment 5 Timo Hoenig 2006-03-20 07:52:36 UTC

Hm, actually I don't think it is very problematic.

NetworkManager-kde does _not_ depend on anything but NetworkManager.  Hence, installing NetworkManager-kde does not pull GNOME.

Now if one wants to use NM+VPN he'll install some NM-VPN package.  Fine.  If he's using the GNOME desktop everything is set, as NM-GNOME is already installed, nm-vpn-properties is available.  If he's on KDE, nm-vpn-properties will not be available as the NM-VPN packages don't have "Requires: NetworkManager-gnome".

And in this case, yes, GNOME will be pulled.  That's fine, as I am using the GNOME NM VPN infrastructure (g-k-d and VPN the configuration dialog) for KNetworkManager at the moment.  Not a long term solution, but as KNM can not guess the VPN properties of a unknown VPN plugin the only solution for now.

Comment 6 Robert Love 2006-03-20 13:55:09 UTC

So ... are you saying, leave everything as-is, or should I add "Requires: NetworkManager-gnome" to the three VPN subpackages?

Comment 7 Timo Hoenig 2006-03-20 13:56:43 UTC

Adding requires would be the fix in my opinion.

Comment 8 Robert Love 2006-03-20 14:01:26 UTC

As you wish, so it shall be.

Comment 9 Timo Hoenig 2006-03-20 15:16:02 UTC

Thank you!

Comment 10 Robert Love 2006-03-20 20:52:47 UTC

Added "Requires: NetworkManager-gnome" to NetworkManager-{vpnc,openvpn,novellvpn}.

Closing.

Comment 11 Andreas Jaeger 2006-10-16 08:43:18 UTC

*** Bug 212499 has been marked as a duplicate of this bug. ***