Install fails on Debian Wheezy because of libssl incompatiblity

[jcoffland]

Trac	Data
Ticket	893
Reported by	@bb30994
Status	closed
Component	Deb Package
Priority	3 (major)
Milestone	v7.2.4

Fixing Ticket #791 caused a new problem (or rather the change to a Linux library did):
http://foldingforum.org/viewtopic.php?p=216779#p216779

This depends on whether you have libssl.so.1.0.0 or libssl0.9.8.

[jcoffland]

Comment by @bb30994
The fix for this problem should probably be coordinated with the fix for #572.

A work-around is provided here:
http://foldingforum.org/viewtopic.php?f=67&t=21736#p217860

[jcoffland]

Comment by @bb30994
We're appaently not the only people with this problem.
http://askubuntu.com/questions/77256/i-want-to-install-libssl-0-9-8

[jcoffland]

Comment by @jcoffland
The issue is that the Debian package building tools automatically grab the library version number based on the system it was built on.

It's easy to edit the package but not easy to make it not do this in the first place. The main reason is that Debian was not designed to work with packages that target multiple systems. The intent is that the packages are rebuilt for each package repository. We cannot feasibly do this and we cannot get F@H integrated into Debian because we are not Open-Source.

Here are the possible solutions:

1. Statically link libssl. This causes lintian warnings and potentially other problems.

2. Edit the package after it is created as part of the build process. This is doable but takes some work to automate.

3. Figure out how to make the Debian package builder do the right thing in the first place. Ideal but I'm not yet sure how to do this.

[jcoffland]

Comment by @jcoffland
Fixed and v7.2.9 is now in open-beta.