Topic: [SOGo] Upgrade to 2.0.0?

[mats]

Cheers,

on 2012-09-27 a new version of SOGo (2.0.0) was released. Would it be safe to upgrade from the version 1.3.18a currently running on our SME server?

According to http://wiki.contribs.org/Sogo upgrading could in theory be done by

Code: [Select]

yum update --disablerepo=* --enablerepo=sogo

Since the new SOGo release, yum will try to upgrade SOGo to 2.0.0 when issuing this command. I have not found any information from the smeserver-sogo contrib maintainers or otherwise regarding this upgrade issue.

If it is not safe to upgrade yet (eg. because of smeserver-sogo contrib not yet reflecting the changes in the new SOGo version), maybe an update of the corresponding wiki entry would be necessary.

mats

[Stefano]

AFAIK, you can safely upgrade to SOGo 2 but be aware that you can't use the (new) native outlook compatibility feature, as it needs samba4

IMHO you could clone your server on a virtual machine (all data but the files in the ibays) and try..

my 2c

[mats]

Thanks Stefano. I did not know about the clone procedure before - time allowing, I'll give it a try and report back...
Fortunately, Outlook is not needed on the site in question.

mats

[Stefano]

ok.. let us know, feel free to report here and/or in the wiki

thank you

[nicolatiana]

Hi mats
 
Three SOGo already upgraded: a test one and then my production one in my office and a customer's one. No evident problem so far; the servers have a lot of mail but few tasks-calendar.
Anyway you can follow Stefano's advice to test on a cloned server.
 
Bye
 
Nicola

[mats]

Hi

following up on my original question, I have now successfully upgraded SOGo to 2.0.1 on SME installations both in a test environment and subsequently in a clients network. Thanks for the heads up in advance

Cheers, Mats

[nicolatiana]

   Good!
 
Nicola

[mats]

Just for the record 

As noted above, some weeks ago I did upgrade to SOGo 2.0.1 by following the advice in the wiki http://wiki.contribs.org/Sogo#Upgrade
In the meantime, SOGo has reached version 2.0.2a (which fixes some annoying bugs initially present in the 2.x release).

Unfortunately, after this inital upgrade to 2.x, any subsequent execution of

Code: [Select]

yum update --disablerepo=* --enablerepo=sogo
would always return a "No Packages marked for Update" message (on this particular server).

By looking at the official SOGo repository http://inverse.ca/downloads/SOGo/RHEL5/i386/RPMS/ I found that Inverse keeps several versions of SOGo in the same repository folder. In order to get the latest version of SOGo and its dependencies installed on SME, one has I had to clear the yum cache for the sogo repo first:

Code: [Select]

yum clean all --disablerepo=* --enablerepo=sogo
yum makecache --disablerepo=* --enablerepo=sogo
yum update --disablerepo=* --enablerepo=sogo
# signal-event sogo-modify
/etc/rc7.d/S85sogod restart

Maybe this information could be added to the wiki entry for SOGo upgrades, if the issue is experienced by others as well? (sorry, I'm not on the wiki team myself...)

[nicolatiana]

Mmmmm . . ..  are you sure ?

With yum list sogo* I get:

sogo.i386 2.0.2-1.el5 installed
sogo-tool.i386 2.0.2-1.el5 installed

And I reached this "version" level with regular:

yum update --disablerepo=* --enablerepo=sogo

And the install/upgrade path was:

Aug 17 12:12:37 Installed: sogo-tool-1.3.17-1.el5.i386
Aug 17 12:12:42 Installed: sogo-1.3.17-1.el5.i386
Aug 17 12:12:49 Installed: smeserver-sogo-0.6-1.el5.nh.noarch
Sep 29 08:06:07 Updated: sogo-tool-2.0.0-1.el5.i386
Sep 29 08:06:12 Updated: sogo-2.0.0-1.el5.i386
Nov 07 09:18:46 Updated: sogo-2.0.2-1.el5.i386
Nov 07 09:18:46 Updated: sogo-tool-2.0.2-1.el5.i386

Now I get the option to update to 2.0.2a-1.el5:

Nov 16 01:49:58 Updated: sogo-tool-2.0.2a-1.el5.i386
Nov 16 01:50:06 Updated: sogo-2.0.2a-1.el5.i386

Maybe you experienced a temporary problem of SOGo repository ?
Did You try with more than one server ?

Bye

Nicola

[mats]

You are right Nicola...
It seems to have been a problem either with the Inverse repository or with this particular server. The

Code: [Select]

yum update --disablerepo=* --enablerepo=sogo did indeed upgrade to 2.0.2.a on another SME installation without the need to refresh the yum cache. I have edited my above post accordingly...