PlaneShift

Development => Development Deliberation => Topic started by: dna on February 23, 2005, 05:26:03 am

Title: Linux installer bug
Post by: dna on February 23, 2005, 05:26:03 am

I just installed planeshift with the linux installer and ran into a problem. After the installer ran the updater, psclient-bin lost its executable bit. Easy fix, \'chmod +x psclient-bin\', just thought I\'d report it.

Another thing I noticed:
$ldd updater-bin
 ---snip---
        libssl.so.0 => not found
        libcrypto.so.0 => not found
---snip---
        libssl.so.4 => /lib/libssl.so.4 (0x0074a000)
        libcrypto.so.4 => /lib/libcrypto.so.4 (0x005a9000)

I\'m thinking the build machine has some outdated symlinks hanging around in /lib

All in all, I like the installer. Makes it a whole lot easier than messing around with cvs repos and shell variables.

EDIT---sorry, wrong forum

Title:
Post by: Karosh_Steinkatz on February 23, 2005, 12:05:52 pm

Quote

Originally posted by dna
I just installed planeshift with the linux installer and ran into a problem. After the installer ran the updater, psclient-bin lost its executable bit. Easy fix, \'chmod +x psclient-bin\', just thought I\'d report it.

The updater usually sets the binaries to executable after it\'s done. Did you abort the updating process or something?

Quote

        libssl.so.0 => not found
        libcrypto.so.0 => not found

These files are shipped with the installer and are also in the binary repo. Even if they are not there, they should be downloaded by the updater. Did you run psclient or psclient-bin?