VulcanRidr | # 1 | 2009-09-04, 03:47 | Report

I got the indicator for upgrades tonight. During the upgrade, the OpenVPN (2.1~rc19-1maemo2) upgrade failed:

The details say that it is conflicting with OS2008 Feature Upgrade (1:5.2008.43-7)

Anyone else see this problem or have a solution?

Thanks.

---

Last edited by VulcanRidr; 2009-09-06 at 14:27.

shocking | # 2 | 2009-09-06, 07:25 | Report

I chose the overide that it suggested and it works OK. It's just that liblzo is part of the base system.

aboaboit | # 3 | 2009-09-07, 09:08 | Report

Ahem, looks like I made a mistake with the dependencies. Try again now, it should install fine without warnings.

VulcanRidr | # 4 | 2009-09-07, 16:17 | Report

Cool. That worked. Thanks.

jgombos | # 5 | 2009-09-07, 19:19 | Report

Be aware that this openvpn upgrade breaks if you have it configured to kick off scripts upon connection. Perhaps rightly so for security reasons.

The solution is to add "script-security 2" to your client configuration files.

aboaboit | # 6 | 2009-09-07, 19:47 | Report

I got bitten by autostarting too: boot took ages, since openvpn was waiting for my key's password.

For that reason, I made it default NOT to autostart any VPN: I want the user to make an explicit, and hopefully informed, decision.

jgombos | # 7 | 2009-09-08, 05:16 | Report

That's a different problem.. I don't autostart, so I didn't experience any hangs. I use the openvpn desktop tool to choose a vpn and start it.

One would think if you have a password that autobooting would always be a problem, not just on an upgrade. AFAIK, the only way around that is to put your password in the configuration file, or have an app that runs inside an "up" script that prompts for the password and passes it on.

aboaboit | # 8 | 2009-09-08, 08:07 | Report

Yes, you're right: that's why I changed the default.