Upgrading cyrus

Jeroen van Meeuwen (Kolab Systems) vanmeeuwen at kolabsys.com
Tue Sep 14 21:16:09 UTC 2010


Patrick Goetz wrote:
> On 09/10/2010 07:04 PM, Jeroen van Meeuwen (Kolab Systems) wrote:
> > RPM packages ship a export / import utility for database formats that may
> > have been changed either in the configuration file or by upgrades, that
> > is called on a service start&  stop;
> > 
> >    http://git.kolabsys.com/rpm/kolab-cyrus-imapd/tree/cyrus-
> > 
> > imapd.cvt_cyrusdb_all
> 
> First,  I've been looking at this RPM package:
>   cyrus-imapd-2.3.16-5.src.rpm
> which I found on this server:
>   http://www.invoca.ch/pub/packages/cyrus-imapd/
> 
> Is this the same RPM you're talking about?  The version of
> cyrus-imapd.cvt_cyrusdb_all in that file is 1.3.4
> 

Any RPM that is shipped with Fedora / Red Hat Enterprise Linux / CentOS, which 
were originally based on the invoca.ch RPM, but have gone their separate ways 
since then[1].

You can find plenty of versions here;

http://koji.fedoraproject.org/koji/packageinfo?packageID=1560

or those that have actually been released for Fedora, and thus current and not 
really as unstable / testing;

https://admin.fedoraproject.org/updates/search/cyrus-imapd

> I think I understand how this script works (not sure how it's called,
> since it relies on variables not defined in the file):
> 1. find the names and db type of db files in imapd.conf
> 2. Use cvt_cyrusdb to convert each db file to a skiplist
> 3. Use cvt_cyrusdb to convert back to the original db format
> 

Indeed it exports the databases on service shutdown, and then imports them 
back on service startup; noted that a condrestart happens on the RPM update, 
this about covers every thinkable scenario (or at least those I've had in the 
past 7 years).

> Aside from file location issues
> (e.g. data_dir=/usr/share/cyrus-imapd/rpm), I don't seem to have the db
> file information in /etc/imapd.conf, as seems to be required for this
> script.  Is this just because my version of cyrus (2.1.16) is too old?
> 

If there is no information in /etc/imapd.conf explicitly, the defaults are 
being used -just like the service itself would. The defaults for RPM (for the 
purpose of the script) is to use skiplist for all databases.

[1] http://pkgs.fedoraproject.org/gitweb/?p=cyrus-imapd.git;a=history;f=cyrus-
imapd.spec;h=e84665a8f41a45b6ecf0ad3a907fed2e25721d1f;hb=a001a7a9625151a09f2a77a3396658497697b8ff

Kind regards,

-- 
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com

pgp: 9342 BF08



More information about the Pkg-Cyrus-imapd-Debian-devel mailing list