http://bugzilla.opensuse.org/show_bug.cgi?id=934129 Bug ID: 934129 Summary: NetworkManager-strongswan configures incorrect path to charon-nm Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: S.M.Flood@uis.cam.ac.uk QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 Build Identifier: Installing NetworkManager-strongswan package will configure the incorrect path for the charon-nm program thus attempting to connect to a strongSwan VPN will fail (given an otherwise correctly configured VPN connection). Reproducible: Always Steps to Reproduce: 1. Install NetworkManager-strongswan package 2. Check program setting under [VPN Connection] section of /etc/NetworkManager/VPN/nm-strongswan-service.name Actual Results: program is set to /usr/lib/ipsec/charon-nm-nm Expected Results: program should be set to /usr/lib/ipsec/charon-nm instead of .../charon-nm-nm Looking at the .spec files on OBS I believe this is a side-effect of the fix for bug #824079 and affects both openSUSE 13.1 & 13.2 where /usr/lib/ipsec/charon-nm is incorrectly being rewritten as /usr/lib/ipsec/charon-nm-nm: # bnc#824079 %if 0%{?suse_version} >= 1230 sed -i "s/charon/charon-nm/" %{buildroot}%{_sysconfdir}/NetworkManager/VPN/nm-strongswan-service.name %endif Whilst a simple fix would be to remove the line from the .spec file it might itself cause a side effect for earlier versions of openSUSE (12.x or earlier) so a better fix might be to anchor the charon string in the sed command: # bnc#824079 %if 0%{?suse_version} >= 1230 sed -i "s/charon$/charon-nm/" %{buildroot}%{_sysconfdir}/NetworkManager/VPN/nm-strongswan-service.name %endif -- You are receiving this mail because: You are on the CC list for the bug.