|Date||Thu, 29 Mar 2007 09:31:38 -0700|
|Subject||[greenstone-users] Re: GLI not functioning with Ubuntu (Michael Dewsnip). #5 in greenstone-users Digest, Vol 48, Issue 35|
I had a similar problem to that reported by Bret Wiebe, and will presently report carefully what I saw and what I did to resolve it. For the moment, let me suggest very briefly what I believe to have been the source of many problem symptoms and what solution worked for me.
I believe that the symptoms I saw, and that might include what Wiebe is seeing, originated in incomplete satisfaction of package dependencies in installing a suitable Java implementation. Which particular unsatisfied dependency a user encounters will depend on which packages happened to be installed when he attempts to execute "./gli.sh". In Wiebe's case, it seems to have been Perl. I believe that Java packages depend on Perl.
I believe that Greenstone GLI is specifically set to not work with GNU Java, perhaps because GNU Java is reputedly replete with bugs. It is recommended that one instead install Sun Java and make that the default choice whenever other software calls for Java. (Uninstalling the GNU Java version delivered as part of Ubuntu Linux risks causing other errors.) Notwithstanding what some Web tutorials suggest, it would be imprudent to install Sun Java using RPM, or by converting Sun's ".rpm" package to a Debian package (".deb") in order to use the Debian installer. Reason: these installers do not seem to resolve all dependencies. A possible consequence is that, after such an installation (I tried each), you are likely to encounter other errors. In my case, I was led astray by such errors--led to attempt to fix the specific errors seen, only to encounter another error. (Sequential debugging--very tedious!)
The Synaptic Package Manager (delivered as part of the Ubuntu distribution) is designed to detect package dependencies and to resolve them recursively. I.e., if you use Synaptic to download and install package A, which happens to depend on package B which in turn depends on package C, Synaptic will handle all together any of A, B, and C that is not already installed on your system.
If you look at the default package list in Synaptic, you will not find Sun Java. However, Sun Java is available via the Synaptic Package Manager if one sets Synaptic up with "Settings --> Repositories --> Non-free (Multiverse)" turned on. Then it installs easily (including forcing the essential end user licence agreement), together with other packages.
This is likely to be a problem with the Perl XML::Parser module. Try:
Do you get a lot of XML output, or errors?
Bret Wiebe wrote:
> occurred. I think that the jre is working okay because the "Greenstone Editor for Metadata Sets" seems to work fine - I can open, edit and
> save files and then exit the app with no errors.
> greatly appreciated.