CipUX 3.2.x update manual for Debian-Edu/Skolelinux 2.0 Original by Christian Külker 2005-09-07 License GPL Revision 0.1 2005-09-07 by Christian Külker (init) Revision 0.2 2005-09-09 by Christian Külker (add Setup Feature) Revision 0.3 2005-09-16 by Christian Külker (exec setup again) Revision 0.4 2005-11-25 by Christian Külker (new version structure) Revision 0.5 2006-04-19 by Christian Külker (moved to debian wiki) Revision 0.6 2006-04-19 by Christian Külker (changed license) Contents -------- 1 General hints for updates 1.1 Preparation before the update 2 Update from 3.2.7 to 3.2.8 2.1 Updating 2.2 Afterwork 3 Update from 3.2.8 to 3.2.9 3.1 Updating 3.2 Afterwork 4 Update from 3.2.9 to 3.2.10 4.1 Updating 4.2 Afterwork 4.3 Update from 3.2.8 5 Update from 3.2.10 to 3.2.11 5.1 Updating 5.2 Afterwork 5.3 Update from 3.2.8 1 General hints for updates ---------------------------- * before an update, MAKE A BACKUP! Example: /skole/backup/etc_cipux_backup_2005-09-07 * after an update: Generally: check the difference between /etc/cipux and /skole/backup/etc_cipux_backup_2005-09-07 Re-invent YOUR changes to the new configuration. So YOU have to KNOW what your changes are. Normally this would be in system.conf (Customer) and cipux.conf (may be LDAP connection with -ZZ or without -ZZ) If you do not know what your changes are, read the installation manual and change /etc/cipux accordingly. In the future, you should mark your changes: # ckuelker 2005-09-07 # Cipux_Debug=0 Cipux_Debug=1 This means ckuelker changed this on 2005-09-07, the value before the change was CipUX_Debug=0 and CipUX_Debug=1 after the change. Easy, isn't it? 1.1 Preparation before the update --------------------------------- * Save your changes from the /etc/cipux folder just to be safe (1) # cp -a /etc/cipux /skole/backup/etc_cipux_backup_2005-09-07 (Change 2005-09-07 to the actual date) 2 Update from 3.2.7 to 3.2.8 ------------------------------ 2.1 Updating ------------ * Update the local repository information (2) # apt-get update * Install the new version (3) # aptitude install cipux-common cipux-cibot cipux-cat-webmin 2.2 Afterwork ------------- * if upgrading to 3.2.8 add some LDAP values in CipUX configuration If # cipux_get_value -x Cat -e cipuxVariable|grep Setup is empty, do # cipux_set_value -a -x Cat -e cipuxVariable -v Cat_Feature_Setup=1 # cipux_set_value -a -x Cat -e cipuxVariable -v Cat_Acl_Setup=assistent 3 Update from 3.2.8 to 3.2.9 ------------------------------ The upgrade procedure is to set the LDAP password and then change every "assistent" to "assistant" in the LDAP server by executing the migration script. 3.1 Updating ------------- * Be sure you have the cipux source in your /etc/apt/sources.list: deb http://debian.cipworx.org/ sid main contrib * Update the local repository information (2) # apt-get update * Install the new version (3) # aptitude install cipux-common cipux-cibot cipux-cat-webmin 3.2 Afterwork ------------- (1) edit as root /etc/cipux/ldappassword.conf with an editor and save the LDAP password WITHOUT a newline! or do as root # echo -n "the LDAP password" > /etc/cipux/ldappassword.conf when nobody is looking at your screen and nobody else is logged in. (2) # chmod 400 /etc/cipux/ldappassword.conf (3) (not nessesary, but safe) # chown root:root /etc/cipux/ldappassword.conf (4) Test if you have access to the user database # cipux_task_list_users (5) If you have access get the upgrade script $ wget debian.cipworx.org/migrate_3.2.8_to_3.2.9.pl (6) # chmod 750 migrate_3.2.8_to_3.2.9.pl (7) do the upgrade (do not kill the script) ./migrate_3.2.8_to_3.2.9.pl 4 Update from 3.2.9 to 3.2.10 ------------------------------ 4.1 Updating ------------- * do the update as usual. 4.2 Afterwork ------------- * there should be nothing special to do. 4.3 Update from 3.2.8 --------------------- (1) Only if you are upgrading from 3.2.8: * do tasks described in update_from_3.2.8_to_3.2.9 5 Update from 3.2.10 to 3.2.11 -------------------------------- 5.1 Updating ------------- * do the update as usual. 5.2 Afterwork ------------- * there should be nothing special to do. 5.3 Update from 3.2.8 --------------------- (1) Only if you are upgrading from 3.2.8: * do tasks described in update_from_3.2.8_to_3.2.9