Active Topics

 



Notices


Reply
Thread Tools
Posts: 473 | Thanked: 141 times | Joined on Jan 2009 @ Virginia, USA
#1
I got the indicator for upgrades tonight. During the upgrade, the OpenVPN (2.1~rc19-1maemo2) upgrade failed:

Code:
Unable to update openvpn.
Conflicting application packages.
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.
 
Posts: 8 | Thanked: 2 times | Joined on Jun 2009
#2
I chose the overide that it suggested and it works OK. It's just that liblzo is part of the base system.
 
aboaboit's Avatar
Posts: 129 | Thanked: 60 times | Joined on Jul 2009 @ Castello d'Argile (BO)
#3
Originally Posted by VulcanRidr View Post
I got the indicator for upgrades tonight. During the upgrade, the OpenVPN (2.1~rc19-1maemo2) upgrade failed:

Code:
Unable to update openvpn.
Conflicting application packages.
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.
Ahem, looks like I made a mistake with the dependencies. Try again now, it should install fine without warnings.
 

The Following User Says Thank You to aboaboit For This Useful Post:
Posts: 473 | Thanked: 141 times | Joined on Jan 2009 @ Virginia, USA
#4
Originally Posted by aboaboit View Post
Ahem, looks like I made a mistake with the dependencies. Try again now, it should install fine without warnings.
Cool. That worked. Thanks.
 
Posts: 67 | Thanked: 13 times | Joined on Feb 2008 @ U.S.A.
#5
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's Avatar
Posts: 129 | Thanked: 60 times | Joined on Jul 2009 @ Castello d'Argile (BO)
#6
Originally Posted by jgombos View Post
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.
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.
 
Posts: 67 | Thanked: 13 times | Joined on Feb 2008 @ U.S.A.
#7
Originally Posted by aboaboit View Post
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.
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's Avatar
Posts: 129 | Thanked: 60 times | Joined on Jul 2009 @ Castello d'Argile (BO)
#8
Originally Posted by jgombos View Post
One would think if you have a password that autobooting would always be a problem, not just on an upgrade.
Yes, you're right: that's why I changed the default.
 
Reply


 
Forum Jump


All times are GMT. The time now is 20:45.