[Pkg-kde-extras] Bug#669702: marked as done (plasma-widget-networkmanagement: Please enable openconnect VPN plugin)
Your message dated Mon, 07 Jan 2013 00:17:43 + with message-id and subject line Bug#669702: fixed in networkmanagement 0.9.0.6-1 has caused the Debian Bug report #669702, regarding plasma-widget-networkmanagement: Please enable openconnect VPN plugin to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 669702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plasma-widget-networkmanagement Version: 0.9.0.1-1 Severity: wishlist Dear Maintainer, please enable support for openconnect VPNs in the Debian build of KDE's networkmanagement module. Upstream supports openconnect for a while already, but the Debian package is built without the openconnect vpnplugin. Probably (but I did not test this) it suffices to add libopenconnect-dev and libssl-dev to Build-Depends. Kind regards, Ralf -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plasma-widget-networkmanagement depends on: ii kde-runtime 4:4.7.4-2 ii libc6 2.13-27 ii libgcc1 1:4.7.0-3 ii libkcmutils44:4.7.4-4 ii libkdecore5 4:4.7.4-4 ii libkdeui5 4:4.7.4-4 ii libkio5 4:4.7.4-4 ii libknotifyconfig4 4:4.7.4-4 ii libplasma3 4:4.7.4-4 ii libqt4-dbus 4:4.7.4-2 ii libqt4-network 4:4.7.4-2 ii libqt4-svg 4:4.7.4-2 ii libqt4-xml 4:4.7.4-2 ii libqtcore4 4:4.7.4-2 ii libqtgui4 4:4.7.4-2 ii libsolid4 4:4.7.4-4 ii libsolidcontrol4abi24:4.7.4-2 ii libstdc++6 4.7.0-3 ii mobile-broadband-provider-info 20120402-1 ii network-manager 0.9.4.0-3 Versions of packages plasma-widget-networkmanagement recommends: ii kwalletmanager 4:4.7.4-2 ii network-manager-openvpn 0.9.4.0-1 ii network-manager-pptp 0.9.4.0-2 ii network-manager-vpnc 0.9.4.0-1 Versions of packages plasma-widget-networkmanagement suggests: pn kdebase-workspace-bin -- no debconf information --- End Message --- --- Begin Message --- Source: networkmanagement Source-Version: 0.9.0.6-1 We believe that the bug you reported is fixed in the latest version of networkmanagement, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated networkmanagement package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Jan 2013 00:45:21 +0100 Source: networkmanagement Binary: plasma-widget-networkmanagement network-manager-kde plasma-widget-networkmanagement-dbg Architecture: source amd64 Version: 0.9.0.6-1 Distribution: experimental Urgency: low Maintainer: Debian KDE Extras Team Changed-By: Michael Biebl Description: network-manager-kde - transitional package for plasma-widget-networkmanagement plasma-widget-networkmanagement - Network Management widget for KDE Plasma workspaces plasma-widget-networkmanagement-dbg - debugging symbols for KDE Network Management Closes: 669702 Changes: networkmanagement (0.9.0.6-1) experimental; urgency=low . * New upstream release. * Enable and install openconnect VPN plugin. Build-Depend on libopenconnect-dev (>= 4.04) to get the version from experimental which is built against GnuTLS. (Closes: #669702) Checksums-Sha1: b2bc22f5cbc6692868957cf60a7de426b07b988e 2480 networkmanagement_0.9.0.6-1.dsc 25762e4d0e4cd1f4f7e3e17739998b31a23ca316 1328455 networkmanagement_0.9.0.6.orig.tar.bz2 a9338eed0c22745cf5828785da313ca67cd49f91 8670 networkmanagement_0.9.0.6-1.debian.tar.gz 8b94048fc880a0198d395550f5c9b5a44b3aa60b 8054 network-manager-kde_0.9.0.6
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
Hi, > I'm not entirely sure when plasma-widget-networkmanagement registers its > NM VPN agent. This is almost certainly a problem with that, rather than > the openconnect-specific parts. Can you restart kded perhaps? I logged out and in, so everything was restarted. Maybe just putting the old debian folder into the new openconnect sources does not work since there was a soname bump - I don't know enough about Debian's handling of shared libraries. Kind regards, Ralf ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
On Tue, 2012-06-12 at 15:18 +0200, Ralf Jung wrote: > [1339506419.612035] [nm-vpn-connection.c:934] get_secrets_cb(): > Failed > to request VPN secrets #3: (6) No agents were available for this request. I'm not entirely sure when plasma-widget-networkmanagement registers its NM VPN agent. This is almost certainly a problem with that, rather than the openconnect-specific parts. Can you restart kded perhaps? I've made a 3.99 release of OpenConnect, which is essentially a beta for 4.00. Matthew, you might want the subsequent patch from the git tree if you're using OpenSSL for DTLS still. The auth-dialog patches for GNOME are already upstream, although you need *not* to include the IPv6 bits from NetworkManager-openconnect unless you've also got an up-to-date NetworkManager. And the final auth-dialog patch for KDE is https://git.reviewboard.kde.org/r/105185/ The packages in Fedora rawhide should be working, using GnuTLS for authentication and falling back to OpenSSL (only in /usr/sbin/openconnect) for DTLS. -- dwmw2 smime.p7s Description: S/MIME cryptographic signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
Hi, I had quite some trouble getting the current openconnect installed without messing my system up (that is, compiling a Debian package for it)... and apparently I did something wrong, or it doesn't work: After also patching and installing plasma-widget-networkmanagement, connecting to the VPN fails with the error [1339506419.612035] [nm-vpn-connection.c:934] get_secrets_cb(): Failed to request VPN secrets #3: (6) No agents were available for this request. Kind regards, Ralf On Thursday 07 June 2012 12:21:05 David Woodhouse wrote: > On Thu, 2012-06-07 at 12:16 +0200, Ralf Jung wrote: > > So the next step would be to change the KDE openconnect NM plugin to use > > the GnuTLS backend of openconnect instead of the OpenSSL one? Currently > > the backend also uses some stuff directly from OpenSSL, I do not know > > why that is needed. > > I fixed that already: > http://git.infradead.org/users/dwmw2/networkmanagement.git/commitdiff/dde75 > baa ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
Hi, On Friday 01 June 2012 03:04:29 David Woodhouse wrote: > On Mon, 2012-05-28 at 13:14 +0200, Ralf Jung wrote: > > > That said, I'm working on porting to GnuTLS anyway. > > > > That's good news. Let me know if I can help testing :) > > http://lists.infradead.org/pipermail/openconnect-devel/2012-May/000572.html So the next step would be to change the KDE openconnect NM plugin to use the GnuTLS backend of openconnect instead of the OpenSSL one? Currently the backend also uses some stuff directly from OpenSSL, I do not know why that is needed. Kind regards, Ralf ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
On Thu, 2012-06-07 at 12:16 +0200, Ralf Jung wrote: > So the next step would be to change the KDE openconnect NM plugin to use the > GnuTLS backend of openconnect instead of the OpenSSL one? Currently the > backend also uses some stuff directly from OpenSSL, I do not know why that is > needed. I fixed that already: http://git.infradead.org/users/dwmw2/networkmanagement.git/commitdiff/dde75baa -- dwmw2 smime.p7s Description: S/MIME cryptographic signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
On Mon, 2012-05-28 at 13:14 +0200, Ralf Jung wrote: > > That said, I'm working on porting to GnuTLS anyway. > That's good news. Let me know if I can help testing :) http://lists.infradead.org/pipermail/openconnect-devel/2012-May/000572.html -- dwmw2 smime.p7s Description: S/MIME cryptographic signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
On Mon, 2012-05-28 at 13:14 +0200, Ralf Jung wrote: > > >* 6. Redistributions of any form whatsoever must retain the following > >*acknowledgment: > >*"This product includes software developed by the OpenSSL Project > >*for use in the OpenSSL Toolkit (http://www.openssl.org/)" > > > > I don't see the relevance of §6. You're linking to a copy of OpenSSL in > > shared library form which already exists on the system; you aren't > > redistributing it in any form. So that should be a non-issue, surely? > > From what I understood - but that's not very much - the problem is simply > that > this is a restriction, while the GPL forbids all kinds of restrictions. It's not a restriction unless you are redistributing OpenSSL, which nobody here is doing. > > That said, I'm working on porting to GnuTLS anyway. > That's good news. Let me know if I can help testing :) It'll be a while; there's a lot to be done and I don't have a lot of free time for it at the moment. If anyone else is interested in working on it, I'd be happy to hand off my work-in-progress and my vague notes on what else needs doing (past the basics of actually making it compile). -- dwmw2 smime.p7s Description: S/MIME cryptographic signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
Hi, > > According to the copyright headers and the git log, you are the main and > > actually almost the only author of that plugin. Is that correct, and if > > yes, would you be willing to add a license extension as stated in [1] to > > the files, so they can be linked with OpenSSL? > > Like libopenconnect itself, Ilia's code is already licensed under the > LGPL, not the GPL. There is no need for an exception for OpenSSL, in the > openconnect-specific plugin. Oh, I did not know that. Sorry for the noise, Ilia. But then I actually do not see the issue here - does the GPL even infect through libraries which are only found and dlsym'ed at runtime? I mean, most of kdelibs is also LGPL. So the entire of kded and would have to be re- licensed for any kded plugin to be able to use OpenSSL? Wow... > Whether that's sufficient or not is not entirely clear to me though. It > is still being loaded into the GPL'd kded as a plugin, after all. > > > [1] http://people.gnome.org/~markmc/openssl-and-the-gpl.html > > That highlights §2 and §6 of the OpenSSL licence: > >* 3. All advertising materials mentioning features or use of this >*software must display the following acknowledgment: >*"This product includes software developed by the OpenSSL Project >*for use in the OpenSSL Toolkit. (http://www.openssl.org/)" > >* 6. Redistributions of any form whatsoever must retain the following >*acknowledgment: >*"This product includes software developed by the OpenSSL Project >*for use in the OpenSSL Toolkit (http://www.openssl.org/)" > > I don't see the relevance of §6. You're linking to a copy of OpenSSL in > shared library form which already exists on the system; you aren't > redistributing it in any form. So that should be a non-issue, surely? >From what I understood - but that's not very much - the problem is simply that this is a restriction, while the GPL forbids all kinds of restrictions. > That said, I'm working on porting to GnuTLS anyway. That's good news. Let me know if I can help testing :) Kind regards, Ralf ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
On 28.05.2012 12:21, Ralf Jung wrote: > Hi Ilia, > > the openconnect vpn module of the plasma widget for networkmanagement links > against OpenSSL, which has some problematic licensing consequences [1]. This > prevents the module from being enabled in Debian [2]. The openconnect vpn module is not problematic, as its sources are under LGPL2. > The only part of network manager directly linking with OpenSSL is that plugin > - I am by far not a licensing expert, but I hope this means that the rest of > the code, which just loads the plugin at runtime, does not need any > relicensing - after all, that code can't know which plugins will be loaded > later. That's exactly what it means, unfortunately. It is the combined work which is problematic. > According to the copyright headers and the git log, you are the main and > actually almost the only author of that plugin. Is that correct, and if yes, > would you be willing to add a license extension as stated in [1] to the > files, > so they can be linked with OpenSSL? The complete networkmanagement sources which use GPL2 would need that exemption. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
On Mon, 2012-05-28 at 12:21 +0200, Ralf Jung wrote: > According to the copyright headers and the git log, you are the main and > actually almost the only author of that plugin. Is that correct, and if yes, > would you be willing to add a license extension as stated in [1] to the > files, > so they can be linked with OpenSSL? Like libopenconnect itself, Ilia's code is already licensed under the LGPL, not the GPL. There is no need for an exception for OpenSSL, in the openconnect-specific plugin. Whether that's sufficient or not is not entirely clear to me though. It is still being loaded into the GPL'd kded as a plugin, after all. > [1] http://people.gnome.org/~markmc/openssl-and-the-gpl.html That highlights §2 and §6 of the OpenSSL licence: * 3. All advertising materials mentioning features or use of this *software must display the following acknowledgment: *"This product includes software developed by the OpenSSL Project *for use in the OpenSSL Toolkit. (http://www.openssl.org/)" * 6. Redistributions of any form whatsoever must retain the following *acknowledgment: *"This product includes software developed by the OpenSSL Project *for use in the OpenSSL Toolkit (http://www.openssl.org/)" I don't see the relevance of §6. You're linking to a copy of OpenSSL in shared library form which already exists on the system; you aren't redistributing it in any form. So that should be a non-issue, surely? So that leaves §2, and I have difficulty understanding precisely what restriction that places on kded. We don't *have* any advertising materials that mention features or use of OpenSSL, but I suppose the concern is that any downstream user must have the right to *create* such, without the wording that OpenSSL requires? But surely they *can* anyway? Doing so doesn't restrict their ability to use libopenconnect or anything higher up in the stack; only their ability to distribute OpenSSL itself, which as already observed we aren't doing. That said, I'm working on porting to GnuTLS anyway. -- dwmw2 smime.p7s Description: S/MIME cryptographic signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement
Hi Ilia, the openconnect vpn module of the plasma widget for networkmanagement links against OpenSSL, which has some problematic licensing consequences [1]. This prevents the module from being enabled in Debian [2]. The only part of network manager directly linking with OpenSSL is that plugin - I am by far not a licensing expert, but I hope this means that the rest of the code, which just loads the plugin at runtime, does not need any relicensing - after all, that code can't know which plugins will be loaded later. According to the copyright headers and the git log, you are the main and actually almost the only author of that plugin. Is that correct, and if yes, would you be willing to add a license extension as stated in [1] to the files, so they can be linked with OpenSSL? Kind regards, Ralf [1] http://people.gnome.org/~markmc/openssl-and-the-gpl.html [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669702 ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: Patch to enable openconnect VPN plugin
Hi, > Unfortunately it's not that easy. > Linking against openssl requires a special exemption which I don't see > granted for networkmanagement. > So atm we can't enable this plugin. > If only openconnect would have used gnutls... > > [1] http://people.gnome.org/~markmc/openssl-and-the-gpl.html Ouch, that's bad (I hate this lawyer stuff^^). Only the openconnect vpn plugin directly links to OpenSSL - does it suffice for these few files to get a license exemption? The plugin is only loaded at runtime, not actually linked against the rest. Kind regards, Ralf ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: Patch to enable openconnect VPN plugin
Hi David, On 25.05.2012 23:07, David Woodhouse wrote: > On Fri, 2012-05-25 at 22:45 +0200, Michael Biebl wrote: >> If only openconnect would have used gnutls... > > If only gnutls would have given a sane way to use a certificate from a > TPM, and supported DTLS. Hey, maybe I wouldn't have had to write HTTP > client support for myself at all; I could have used one of the multitude > of existing libraries! Oh, yeah, I'm very well aware that gnutls has its own share of issues and peculiarities. > Patches to openconnect to make it optionally use gnutls instead of > openssl would be most welcome... and it could be done incrementally; > using gnutls just for the TCP connection first and still using OpenSSL > for DTLS (which happens in openconnect(8) not in libopenconnect). That > would be enough to solve this issue, and adding PKCS#11 support and DTLS > support could come later. Personally I don't have the time to work on that but would appreciate any efforts in that direction. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: Patch to enable openconnect VPN plugin
On Fri, 2012-05-25 at 22:45 +0200, Michael Biebl wrote: > If only openconnect would have used gnutls... If only gnutls would have given a sane way to use a certificate from a TPM, and supported DTLS. Hey, maybe I wouldn't have had to write HTTP client support for myself at all; I could have used one of the multitude of existing libraries! Looking to the future though: gnutls does have DTLS support now, and it shouldn't be that hard to make it support the slightly nonstandard version of DTLS that Cisco use in AnyConnect. And I'd settle for generic PKCS#11 module support (even though there's still no sane PKCS#11 module for TPM access). Patches to openconnect to make it optionally use gnutls instead of openssl would be most welcome... and it could be done incrementally; using gnutls just for the TCP connection first and still using OpenSSL for DTLS (which happens in openconnect(8) not in libopenconnect). That would be enough to solve this issue, and adding PKCS#11 support and DTLS support could come later. -- dwmw2 smime.p7s Description: S/MIME cryptographic signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: Patch to enable openconnect VPN plugin
On 21.04.2012 12:49, Ralf Jung wrote: > tags 669702 patch > thanks > > I attached a patch which adds the necessary Build-Depends and Recommends for > openconnect VPNs and installs the vpnplugin files. I tested it locally and > successfully connected to a VPN using openconnect. Unfortunately it's not that easy. Linking against openssl requires a special exemption which I don't see granted for networkmanagement. So atm we can't enable this plugin. If only openconnect would have used gnutls... Michael [1] http://people.gnome.org/~markmc/openssl-and-the-gpl.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: plasma-widget-networkmanagement: Please enable openconnect VPN plugin
Hi, Michael, you seem to be the active maintainer of this package. I'd appreciate any feedback on whether this patch can be accepted, and if not, then what I could do to help getting openconnect support in the Debian package of the Plasma networkmanagement widget. Kind regards, Ralf ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702:
When you do it, it's best to pull in these fixes and build against OpenConnect 3.20: https://git.reviewboard.kde.org/r/104979/ -- Sent with MeeGo's ActiveSync support. David WoodhouseOpen Source Technology Centre david.woodho...@intel.com Intel Corporation smime.p7s Description: S/MIME cryptographic signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: The patch networkmanagement.diff works
Dear Maintainer, I confirm that the patch works, and I also would like to see it merged. Thanks for your time, and for making Debian such a great OS. ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: Patch to enable openconnect VPN plugin
tags 669702 patch
thanks
I attached a patch which adds the necessary Build-Depends and Recommends for
openconnect VPNs and installs the vpnplugin files. I tested it locally and
successfully connected to a VPN using openconnect.
Kind regards,
Ralf
diff -ur networkmanagement.bak/debian/changelog networkmanagement-0.9.0.1/debian/changelog
--- networkmanagement.bak/debian/changelog 2012-04-09 11:38:33.0 +0200
+++ networkmanagement-0.9.0.1/debian/changelog 2012-04-21 11:32:37.595877386 +0200
@@ -1,3 +1,10 @@
+networkmanagement (0.9.0.1-1.1) unstable; urgency=low
+
+ * Add Build-Depends on libopenconnect-dev and libssl-dev to enable the
+openconnect vpnplugin.
+
+ -- Ralf Jung Sat, 21 Apr 2012 11:31:48 +0200
+
networkmanagement (0.9.0.1-1) unstable; urgency=low
* New upstream release.
diff -ur networkmanagement.bak/debian/control networkmanagement-0.9.0.1/debian/control
--- networkmanagement.bak/debian/control 2012-04-09 11:38:33.0 +0200
+++ networkmanagement-0.9.0.1/debian/control 2012-04-21 12:22:27.632863249 +0200
@@ -6,7 +6,7 @@
Build-Depends: debhelper (>= 8), cmake (>= 2.6.2), pkg-kde-tools (>= 0.5),
libqt4-dev (>= 4:4.6.0), kdelibs5-dev (>= 4:4.6.0), kdebase-workspace-dev (>= 4:4.6.0),
network-manager-dev (>= 0.9.0), libnm-util-dev (>= 0.9.0), libnm-glib-dev (>= 0.9.0),
- mobile-broadband-provider-info
+ mobile-broadband-provider-info, libopenconnect-dev, libssl-dev
Standards-Version: 3.9.3
Vcs-Git: git://git.debian.org/git/pkg-kde/kde-extras/networkmanagement.git
Vcs-Browser: http://git.debian.org/?p=pkg-kde/kde-extras/networkmanagement.git
@@ -16,7 +16,8 @@
Depends: ${shlibs:Depends}, ${misc:Depends}, network-manager (>= 0.9.0),
mobile-broadband-provider-info
Suggests: kdebase-workspace-bin
-Recommends: kwalletmanager, network-manager-vpnc, network-manager-openvpn, network-manager-pptp
+Recommends: kwalletmanager, network-manager-vpnc, network-manager-openvpn, network-manager-pptp,
+ network-manager-openconnect
Replaces: knm-runtime
Breaks: knm-runtime
Description: Network Management widget for KDE Plasma workspaces
diff -ur networkmanagement.bak/debian/plasma-widget-networkmanagement.install networkmanagement-0.9.0.1/debian/plasma-widget-networkmanagement.install
--- networkmanagement.bak/debian/plasma-widget-networkmanagement.install 2012-04-09 11:38:33.0 +0200
+++ networkmanagement-0.9.0.1/debian/plasma-widget-networkmanagement.install 2012-04-21 12:27:33.698549684 +0200
@@ -3,6 +3,7 @@
usr/lib/kde4/kded_networkmanagement.so
usr/lib/kde4/libexec/networkmanagement_configshell
usr/lib/kde4/networkmanagement_novellvpnui.so
+usr/lib/kde4/networkmanagement_openconnectui.so
usr/lib/kde4/networkmanagement_openvpnui.so
usr/lib/kde4/networkmanagement_pptpui.so
usr/lib/kde4/networkmanagement_strongswanui.so
@@ -26,6 +27,7 @@
usr/share/kde4/services/kcm_networkmanagement_tray.desktop
usr/share/kde4/services/kded/networkmanagement.desktop
usr/share/kde4/services/networkmanagement_novellvpnui.desktop
+usr/share/kde4/services/networkmanagement_openconnectui.desktop
usr/share/kde4/services/networkmanagement_openvpnui.desktop
usr/share/kde4/services/networkmanagement_pptpui.desktop
usr/share/kde4/services/networkmanagement_strongswanui.desktop
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#669702: plasma-widget-networkmanagement: Please enable openconnect VPN plugin
Package: plasma-widget-networkmanagement Version: 0.9.0.1-1 Severity: wishlist Dear Maintainer, please enable support for openconnect VPNs in the Debian build of KDE's networkmanagement module. Upstream supports openconnect for a while already, but the Debian package is built without the openconnect vpnplugin. Probably (but I did not test this) it suffices to add libopenconnect-dev and libssl-dev to Build-Depends. Kind regards, Ralf -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plasma-widget-networkmanagement depends on: ii kde-runtime 4:4.7.4-2 ii libc6 2.13-27 ii libgcc1 1:4.7.0-3 ii libkcmutils44:4.7.4-4 ii libkdecore5 4:4.7.4-4 ii libkdeui5 4:4.7.4-4 ii libkio5 4:4.7.4-4 ii libknotifyconfig4 4:4.7.4-4 ii libplasma3 4:4.7.4-4 ii libqt4-dbus 4:4.7.4-2 ii libqt4-network 4:4.7.4-2 ii libqt4-svg 4:4.7.4-2 ii libqt4-xml 4:4.7.4-2 ii libqtcore4 4:4.7.4-2 ii libqtgui4 4:4.7.4-2 ii libsolid4 4:4.7.4-4 ii libsolidcontrol4abi24:4.7.4-2 ii libstdc++6 4.7.0-3 ii mobile-broadband-provider-info 20120402-1 ii network-manager 0.9.4.0-3 Versions of packages plasma-widget-networkmanagement recommends: ii kwalletmanager 4:4.7.4-2 ii network-manager-openvpn 0.9.4.0-1 ii network-manager-pptp 0.9.4.0-2 ii network-manager-vpnc 0.9.4.0-1 Versions of packages plasma-widget-networkmanagement suggests: pn kdebase-workspace-bin -- no debconf information ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
