updated OpenVPN package: how to distribute?
 

Hi.

I have prepared a newer OpenVPN package, version 2.1rc19. I would like to know how I can get it included in the maemo downloads page:
http://maemo.org/downloads/product/OS2008/openvpn/

I had tried contacting the author of the current port, in vain, so I started from the Debian package, kept whatever was reasonable and put together a works-for-me version.

Any tips?

A.

Re: updated OpenVPN package: how to distribute?
 

Whole process should be explained here http://wiki.maemo.org/Uploading_to_Extras

Re: updated OpenVPN package: how to distribute?
 

Can you give us some information on your version and is it available for download? Thanks.

Re: updated OpenVPN package: how to distribute?
 

Sure, here is a rundown of the changes:

• requires libssl0.9.8, not available for Diablo: I rebuilt the Fremantle version with no changes whatsoever and it works fine
• removed the blacklist dependencies: too big for the device
• autostart is disabled by default: if a key is password-protected, the device will appear to hang while booting (it is just waiting for the password, in fact, but you can't see it)
• backup: I added a config entry to backup the whole /etc/openvpn directory (for some reason, the *.key file is skipped... no clue yet)
• resolveconf: I reworked the debian script with the reasonable assumption that you'll be running 1 vpn at a time on the NIT (there's no resolveconf, gotta cut some corners)

Downloads here:
openvpn_2.1rc19
libssl0.9.8

I will now go through the upload steps.

A.

Re: updated OpenVPN package: how to distribute?
 

I see that openvpn is updated now. But it cannot be installed because updating libssl is not possible due to Nokia's update system. Also liblzo1 is missing.

Re: updated OpenVPN package: how to distribute?
 

Hmm, I tried reinstalling openvpn from the gui and I had no problems. I actually have 2 versions of openssl installed, side by side, on my piano keyboard.... no that was Sir Paul, sorry ;-)

Earlier today, the openvpn install file still referenced the older version, while now it points to mine. I have yet to understand how to edit the download page, btw.

Anyhow, what are the exact steps that result in an error for you? Any older version lying around (including dependencies) or clean install?

Re: updated OpenVPN package: how to distribute?
 

Try to install openvpn with application manager.

liblzo1 cannot be installed because it is not in maemo.org Extras repository (liblzo2-2 is)

libssl0.9.8 is locked to 0.9.8e-9maemo3 with osso-software-version-rx34 (or rx44 or rx48). Application manager cannot uninstall osso-software-version-rx34, because it will break automatic update feature.

Re: updated OpenVPN package: how to distribute?
 

I first ran dpkg --force-depends --remove openvpn, then apt-get install openvpn and had no problems. Funny thing is, I also ran the build-dependency checks before uploading and the autobuilder accepted it.

I am at a loss regarding liblzo, I'll have to re-check. I have the "unlocked" variant of osso-software-version, I strongly suspect that is not irrelevant. Thanks for the feedback.

Re: updated OpenVPN package: how to distribute?
 

liblzo1 appears to be in chinook extras but not in diablo extras

Re: updated OpenVPN package: how to distribute?
 

That might explain why it installs on my device but the autobuilder should fetch only from diablo's extras.

See here:
https://garage.maemo.org/builder/dia...oot.log.OK.txt

Re: updated OpenVPN package: how to distribute?
 

Well liblzo1 is also in sdk repository, but it is not meant to be used in device, that's where builder is gettting it

Re: updated OpenVPN package: how to distribute?
 

Care to provide a link to the policy of not having lzo on the device?

I have the diablo/tools repository: if I disable that, I can't install liblzo. I'll have a look at specifying this as a dependency.

Re: updated OpenVPN package: how to distribute?
 

SDK repository is not meant to be used in device. Liblzo can be installed as soon as it's in Extras repository. Generally Extras repository has to work with fresh OS install without adding any other repository than Extras.

Re: updated OpenVPN package: how to distribute?
 

I think now I understand where I went wrong:

• ssl: I accepted the original debian requirement of 0.9.8g-9, even though openvpn mandates a minimum 0.9.5 and osso-software-version-rx44 for the N810 specifies 0.9.8e-9maemo3 as dependency
• lzo: here I assumed that the SDK would have all required packages and changed the dependency of lzo2 to lzo instead of installing lzo2 from extras as would have been proper

Hopefully, the dependencies are correct now and allow clean installation on a pristine N810. Thank you very much for the patience.

I have already submitted the package to the autobuilder. Later, I'll check whether my (now) spurious libssl0.9.8g package is being considered in the dependencies or hopefully not.

Re: updated OpenVPN package: how to distribute?
 

thanks, np :)

I haven't checked the autobuilder logs, but it may be that you have to ask debmaster (jeremiah) to remove too "new" version of libssl from extras-devel.

Re: updated OpenVPN package: how to distribute?
 

Can I have openvpn v2.0.9-4etch1maemo1 back ?

I installed openvpn 2.1~rc19-1maemo3 , all my ultravpn and alonweb account can not work anymore .

Re: updated OpenVPN package: how to distribute?
 

It is still available here:
http://repository.maemo.org/extras/p...ree/o/openvpn/

I am not aware of any compatibility issues. Can you provide some more information? Sadly, "can not work" is not quite helpful for debugging.

Try one of the following:

• applet: run the "test" mode, save the log and post it here
• commandline: run "openvpn nameofconfig.conf" and, again, copy the output

EDIT: did you check the OpenVPN FAQ ? Easy money that you have not specified a port number in your configs

Re: updated OpenVPN package: how to distribute?
 

I am going to remove the spurious libssl, see if that helps things.

Jeremiah

Re: updated OpenVPN package: how to distribute?
 

I have removed openssl, its sources and its built debs in both arches.

Jeremiah

Re: updated OpenVPN package: how to distribute?
 

Great. I went ahead, added an epoch and resubmitted. Package builds ok and the required libssl version now matches the one available in Diablo.

However, the package promoter only shows the source as being moveable while the binaries are not "tickable".

What gives?

EDIT: maybe the promoter needed to sleep it over ;-) Now it is ok.

Re: updated OpenVPN package: how to distribute?
 

Open question: how do you update the downloads page to reflect new packager, homepage and suchlike?

EDIT: nevermind, I found out it happens automatically after a while.