Obsolete Releases > SME 8.x Contribs

[SOGo] Upgrade to 2.0.0?

<< < (2/2)

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:
 8)  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: ---yum update --disablerepo=* --enablerepo=sogo
--- End code ---

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: ---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

--- End code ---

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:

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

--- End quote ---
And I reached this "version" level with regular:

--- Quote ---yum update --disablerepo=* --enablerepo=sogo
--- End quote ---
And the install/upgrade path was:

--- Quote ---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
--- End quote ---

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

--- Quote ---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
--- End quote ---

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: ---yum update --disablerepo=* --enablerepo=sogo
--- End code ---
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...

Navigation

[0] Message Index

[*] Previous page