mikkov | # 11 | 2009-09-03, 22:36 | Report

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

aboaboit | # 12 | 2009-09-04, 06:16 | Report

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.

mikkov | # 13 | 2009-09-04, 22:53 | Report

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.

aboaboit | # 14 | 2009-09-05, 15:46 | Report

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.

---

Last edited by aboaboit; 2009-09-05 at 15:59.

mikkov | # 15 | 2009-09-05, 19:07 | Report

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.

deter3 | # 16 | 2009-09-06, 17:39 | Report

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 .

aboaboit | # 17 | 2009-09-06, 19:42 | Report

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

---

Last edited by aboaboit; 2009-09-08 at 10:56. Reason: added link to FAQ

jeremiah | # 18 | 2009-09-06, 20:41 | Report

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

Jeremiah

jeremiah | # 19 | 2009-09-06, 21:07 | Report

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

Jeremiah

aboaboit | # 20 | 2009-09-06, 22:10 | Report

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.

---

Last edited by aboaboit; 2009-09-07 at 05:53.