On Sun, Oct 30, 2011 at 09:12:22AM -0400, Ludovic Marcotte wrote:
> That's probably a sign of having old SOPE packages around after
> proceeding with the SOGo update. Make sure you update all SOPE
> packages to the latest version and restart the SOGo service after.
Yes, looks like you had some packages in the v1.3.9 yum-repo with
version numbers that rpm/yum would interpret as newer than the new ones
for sogo v1.3.9-2. Those who had upgraded to v1.3.9-1 will probably
still be running on wrong sope49-cards and sope49-gdl1-contentstore
after upgrading to v1.3.9-2.
[janfrode@webmail2 ~]$ rpm -q sope49-cards sope49-gdl1-contentstore
sope49-cards-1.3.9-2.centos6.x86_64
sope49-gdl1-contentstore-1.3.9-2.centos6.x86_64
[janfrode@webmail2 ~]$ sudo yum update
================================================================================
Package Arch Version
Repository
Size
================================================================================
Updating:
sope49-cards x86_64 2.0_20111018-1.el6.0 sogo 161 k
sope49-gdl1-contentstore x86_64 2.0_20111018-1.el6.0 sogo 54 k
Transaction Summary
================================================================================
Upgrade 2 Package(s)
$ rpmdev-vercmp
Epoch1 :
Version1 :1.3.9
Release1 :2.centos6
Epoch2 :
Version2 :2.0_20111018
Release2 :1.el6
:2.0_20111018-1.el6 is newer
The reason this was hitting us is that I sync'ed in your packages
to our local repository, since our servers aren't allowed to talk
openly on the internet, and I hadn't noticed that these needed to
be deleted from the repo..
-jf
--
[email protected]
https://inverse.ca/sogo/lists
