Thanks for clarifying the issue you’re seeing. I don’t think this is related to the D-Bus changes.
Also, to be clear: I’m not the maintainer of this package, I sponsored mtmiller@’s uploads, who maintains the package. On Tue, Mar 8, 2016 at 3:09 AM, Ryan Chewning <r...@chewning.us> wrote: > Michael, I copied you on this bug as you're the package maintainer for > network-manager-openconnect and the imports of the upstream are failing. > Currently, upstream for network-open-connect is at 1.91 and in Debian > unstable/testing are both on the 1.0.2 release which isn't working with the > network-manager builds in unstable and are on 1.91. I'm attempting to > create an openconnect vpn profile but I get the following error messages in > my .xsession-error log when launching nm-connection editor > > """ > ** Message: vpn: (iodine,/usr/lib/NetworkManager/VPN/ > nm-iodine-service.name) cannot load legacy-only plugin > ** Message: vpn: (ssh,/usr/lib/NetworkManager/VPN/nm-ssh-service.name) > cannot load legacy-only plugin > ** Message: vpn: (openconnect,/usr/lib/NetworkManager/VPN/ > nm-openconnect-service.name) cannot load legacy-only plugin > ** Message: vpn: (strongswan,/etc/NetworkManager/VPN/ > nm-strongswan-service.name) cannot load legacy-only plugin > """" > > I also only have the option to configure the following three types of vpns > OpenVPN, PPTP or KVPNC even though I have iodine, ssh, openconnect and > strongswan installed. > > If you think this bug is better suited for the network-manager package > please let me know and I'll head over that way. > > Thanks, > > Ryan > > On Mon, Mar 7, 2016 at 12:22 PM, Michael Stapelberg <stapelb...@debian.org > > wrote: > >> >> >> On Mon, Mar 7, 2016 at 9:07 AM, Ryan Chewning <r...@chewning.us> wrote: >> >>> Package: network-manager-openconnect >>> Version: 1.0.2-1+b1 >>> Severity: grave >>> Tags: upstream >>> Justification: renders package unusable >>> >>> The latest builds of networkmanager in testing/unstable no longer >>> support dbus. https://blogs.gnome.org/dcbw/2016/02/19/die-dbus-glib-die/ >>> >> >> I’m only a bystander for the purpose of this bug, but “networkmanager […] >> no longer supports dbus” conflicts with the article you refer to, which >> mentions: >> >> """ >> I cannot understate how much work this was and how much careful planning >> we (well, mostly Dan Winship) did to ensure we didn’t break backwards >> compatibility of either the utility libraries or the D-Bus interface. >> """ >> >> The way I read this, the new networkmanager version is >> backwards-compatible with regards to its D-Bus interface. >> >> Can you clarify? If it turns out that it’s actually backwards-compatible, >> is severity: grave still justified? >> >> >>> There is an updated version of the network-manager-openconnect but it is >>> failing to be pulled down by uscan. Manual intervention is needed. >>> >>> Thanks, >>> >>> Ryan >>> >>> -- System Information: >>> Debian Release: stretch/sid >>> APT prefers testing-updates >>> APT policy: (500, 'testing-updates'), (500, 'testing') >>> Architecture: amd64 (x86_64) >>> Foreign Architectures: i386 >>> >>> Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) >>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) >>> Shell: /bin/sh linked to /bin/dash >>> Init: systemd (via /run/systemd/system) >>> >>> Versions of packages network-manager-openconnect depends on: >>> ii adduser 3.113+nmu3 >>> ii libc6 2.21-9 >>> ii libdbus-1-3 1.10.6-1 >>> ii libdbus-glib-1-2 0.106-1 >>> ii libglib2.0-0 2.46.2-3 >>> ii libnm-glib-vpn1 1.1.90-6 >>> ii libnm-glib4 1.1.90-6 >>> ii libnm-util2 1.1.90-6 >>> ii network-manager 1.1.90-6 >>> ii openconnect 7.06-2+b2 >>> >>> network-manager-openconnect recommends no packages. >>> >>> network-manager-openconnect suggests no packages. >>> >>> -- no debconf information >>> >>> >> >> >> -- >> Best regards, >> Michael >> > > -- Best regards, Michael
