Hi everyone, I was updating the upgrade instructions and I just wanted a few clarifications:
1) When upgrading to 1.6: before running the database upgrade script at step 5, we recommend backing up the database. Now, I have been assuming that only a data dump of the Evergreen database would be required to be secure before running the sql script. However, Roma mentioned that the original instructions mentioned backing up the postgres user directory. Is that required or only the database dump as I have assumed? 2) In the past, Dan seemed to indicate that the Karmic Koala version of Ubuntu was supported and had targets set up in the makefile.install files and that this would be made part of trunk. (See: http://www.mail-archive.com/[email protected]/msg03673.html). However, In recent testing the Karmic targets seemed to be missing from the Makefile.install in the 1.2 version of OpenSRF. Could you verify if Karmic is officially supported and still working or did the beta version break stuff? It would be great to add the Karmic target references in the upgrade and install instructions. 3) Ejabberd issues: I was wondering if the Ejabberd issue as discussed here: http://list.georgialibraries.org/pipermail/open-ils-dev/2009-July/004888.html has been resolved and for which versions of Ejabberd? Is a downgrade required to get OpenSRF to work or did the patch fix? I was testing on my home machine with Ejabberd 2.0.5.1.1 and am getting the errors discussed in the thread. Do I have to downgrade? If so, what is the best way to downgrade from 2.0.5.11? It might be good to have precise instructions for this somewhere in the install documentation. Thanks, Robert This E-mail contains privileged and confidential information intended only for the individual or entity named in the message. If the reader of this message is not the intended recipient, or the agent responsible to deliver it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is prohibited. If this communication was received in error, please notify the sender by reply E-mail immediately, and delete and destroy the original message.
