Control: severity -1 important On Tue, Mar 08, 2016 at 08:04:42 +0100, Michael Stapelberg wrote: > 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.
Thanks for responding for me ;) Yikes, out of order quoting: > On Tue, Mar 8, 2016 at 3:09 AM, Ryan Chewning <r...@chewning.us> wrote: > > On Mon, Mar 7, 2016 at 12:22 PM, Michael Stapelberg <stapelb...@debian.org > >>> > >>> 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? My understanding is that it is backwards-compatible (e.g. I am still able to connect via nm-openconnect on my system). However, they do seem to have dropped support for old-style plugins in the nm-connection-editor, possibly nm-applet. I use gnome-shell which still allows me to create, edit, and connect to OpenConnect VPNs perfectly. I'm downgrading to important. Request for a new version would normally be wishlist. This package is still mostly working for users with existing VPNs or who use gnome-shell or manage VPNs with keyfiles manually, but not for nm-applet users. > >>> There is an updated version of the network-manager-openconnect but it is > >>> failing to be pulled down by uscan. Manual intervention is needed. JFTR, manual intervention is always required. I don't know why the tracker and udd are reporting upstream failures, uscan works locally for me, but that's a separate issue (if I understand what you meant). -- mike
