wilde: doc/raw-howtos kolab_2.0_to_2.1_upgrade_instructions.txt, 1.1, 1.2

cvs at kolab.org cvs at kolab.org
Wed Nov 15 16:13:52 CET 2006


Author: wilde

Update of /kolabrepository/doc/raw-howtos
In directory doto:/tmp/cvs-serv24102

Modified Files:
	kolab_2.0_to_2.1_upgrade_instructions.txt 
Log Message:
Dome additions and clarifications.
These were generated from an actual upgraded experience. :-)


Index: kolab_2.0_to_2.1_upgrade_instructions.txt
===================================================================
RCS file: /kolabrepository/doc/raw-howtos/kolab_2.0_to_2.1_upgrade_instructions.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- kolab_2.0_to_2.1_upgrade_instructions.txt	13 Nov 2006 15:29:06 -0000	1.1
+++ kolab_2.0_to_2.1_upgrade_instructions.txt	15 Nov 2006 15:13:49 -0000	1.2
@@ -48,7 +48,6 @@
 Configuration
 -------------
 
-
 1. Check custom configuration
 
 If you have custom configurations in your templates, the installation
@@ -56,6 +55,15 @@
 extension .rpmsave.  Copy any modifications from your templates to the
 new one if they are still needed.
 
+After that the files with the extension .rpmsave must be removed or
+renamed.  There might be more files with the .rpmsave ending in
+/kolab/etc, you can find them for example using the find command:
+
+find /kolab/etc -name '*.rpmsave'
+
+Any files found must be checked and moved out of the way, in most
+cases they can just be deleted.
+
 
 2. Cyrus IMAPd
 
@@ -63,8 +71,8 @@
 hashimapspool option.  This means that in 2.1 the default directory
 layout of the imapd spool (/kolab/var/imapd/spool/) is different from
 the one in 2.0.  When you upgrade from 2.0 it's best to keep using the
-old structure, so remove or comment out the corresponding line in
-/kolab/etc/kolab/templates/imapd.conf.template *before* running
+old structure, so remove or comment out the line "hashimapspool: yes"
+in /kolab/etc/kolab/templates/imapd.conf.template *before* running
 kolabconf.
 
 For new installations the new default setting is recommended because
@@ -79,7 +87,7 @@
 You need to make two small changes to the configuration file
 /kolab/etc/openldap/slapd.conf:
 
-  - comment out the line 
+  - comment out the line
 
      require        none
 
@@ -106,6 +114,7 @@
    rm /kolab/var/openldap/openldap-data/*
    /kolab/sbin/slapadd -l ~/kolab-2.1.ldif
 
+This will issue some warnings which can be safely ignored.
 
 
 4. kolabconf
@@ -116,9 +125,9 @@
     /kolab/sbin/kolabconf
 
 
-Kolabconf will most likely complain about be some files ending in
-.rpmsave or .rpmnew under /kolab/etc.  Check those files and move them
-out of the way.  It's likely that you can simply remove them.
+Kolabconf will might complain about be some files ending .rpmnew under
+/kolab/etc.  Check those files and move them out of the way.  It's
+likely that you can simply remove them.
 
 
 Start the Server
@@ -127,3 +136,22 @@
 Now you should be able to start the server again:
 
     /kolab/bin/openpkg rc all start
+
+
+Final Steps
+-----------
+
+1. The internal format of the ldap records for the list of privileged
+   networks has changed, to updated these recods go to the kolab web
+   interface an log in as administrative user.  Open the "Services"
+   page and search for the "Privileged Networks" section.  Klick the
+   update button for the networks list.
+
+2. Kolab 2.1 doesn't need some of the OpenPKG packages which were
+   installed for 2.0, these can be removed:
+
+   /kolab/bin/openpkg rpm -e dcron vim pth
+
+   Especially the dcron package should be removed in any case,
+   otherwise deprecated cronjobs will be run and generate mails with
+   error messages to the kolab administrator.





More information about the commits mailing list