Upgrading to 3.2 from 3.1

[Troy Carpenter]

I'll follow up on my own email.

I added the repositories listed in the install guide for 3.2 and did a "yum
update".  When all packages were finished, there were a number of .rpmnew
files I had to reconcile (most I didn't need to take the changes and kept my
originals), and there was some error message while updating Roundcube:

Updating   : roundcubemail-1.0-38.1.el6.kolab_3.2.noarch
Updating database schema (2013011000)... [OK]
Updating database schema (2013042700)... [OK]
Updating database schema (2013052500)... [FAILED]

When done, Roundcube wouldn't work.  A quick look in the logs showed most
Roundcube files were missing and I had to reinstall all the roundcube
packages before the problem resolved.

The only remaining problem I had was Android devices not getting email via
Activesync.  I had modified kolab_sync_data.php in kolab-syncroton, and that
was overwritten by the new package.  I quickly added the Android devices
back in and the Android devices I have started working again (see
https://issues.kolab.org/show_bug.cgi?id=2819).

As of now, everything looks like it is working.  Hope that helps others who
haven't updated to 3.2 yet.

Now I'm looking forward to 3.3!

-----Original Message-----
From: users-bounces at lists.kolab.org [mailto:users-bounces at lists.kolab.org]
On Behalf Of Carpenter, Troy
Sent: Monday, August 11, 2014 2:59 PM
To: users at lists.kolab.org
Subject: Upgrading to 3.2 from 3.1

Now that 3.3 Beta is out, I'm once again looking to upgrade from 3.1 to 3.2.
I know the subject has come up in the past, but I don't recall a definitive
answer.  However, if add the repos as outlined in the install doc here:
http://docs.kolab.org/installation-guide/centos.html , then do an yum
update, should that upgrade the system properly, or will I have to do some
data massaging before my system is functional again?


_______________________________________________
users mailing list
users at lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users