https://bugzilla.redhat.com/show_bug.cgi?id=970009 --- Comment #8 from Simone Caronni <negativo17@xxxxxxxxx> --- (In reply to David Woodhouse from comment #6) > Ah, no. The NM-openconnect parts should all be there already. Now you have a > version of libopenconnect which admits to having stoken support, you should > see the corresponding options in the configuration GUI. Nope, I don't have them. I see support comes from the 0.9.8 release; though I don't know if NetworkManager-openconnect-0.9.7.0-2.git20120918.fc19 is a snapshot of 0.9.8 or not. Can you update the current git snapshot in Fedora 18+ to 0.9.8? ======================================================= network-manager-openconnect-0.9.8 Overview of changes since network-manager-openconnect-0.9.6.2 ======================================================= This is a new stable release of network-manager-openconnect. Notable changes include: * Updated translations * Builds against the GNOME 3.8 versions of GLib and Gtk+ * Software Tokens are now supported (if libopenconnect has support for them) * Fixed typos in several messages * nm-openconnect-service now returns translated error messages (In reply to David Woodhouse from comment #7) > Perhaps you did that when you noticed the errant -O0 that you get by adding > --enable-debug? We'll want upstream to give us a way to build with -O2 -ggdb > which is our normal CFLAGS, rather than forcibly either overriding it to -O0 > or stripping the debug info. Exactly for this actually. > If you apply the patch I just sent you for using GnuTLS, you'll need to run > autoreconf. And then you don't need to hack the libtool script with sed to > fix the stupid rpath brokenness. I was planning to make the minimum changes, but since the GnuTLS requires autoreconf to be rerun I removed the rpath script and CFLAGS override as well. > Is that something you (should) have > reported to the upstream maintainer, to make sure it's not present in the > next release? Before doing anything I would have liked to see all the changes that are required coming from the review. Is removing entirely the "enable debugging option" (lines 25-39) from configure.ac the best approach? Thanks, --Simone -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=bit2CPvn0E&a=cc_unsubscribe _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review