Bug#369882: cyrus-doc-2.2 upgrade issues

[Sven Mueller]

Ross Boylan wrote on 13/06/2006 19:49:
> On Tue, 2006-06-13 at 12:32 +0200, Sven Mueller wrote:
> 
>>Well, I can at least give a quick answer on this:
>>Neither 2.1 nor 2.2 differ that much from upstream that the upgrade path
>>is affected. Actually, IIRC, the upgrade from 2.1 to 2.2 is usually just
>>removing 2.1 and installing 2.2, since both use Berkeley DB 4.2 and the
>>same config files and config format. A backup before upgrading and some
>>tests after upgrading is still recommended though.
>>At least it worked that way for me when I upgraded my own mailserver.
> 
> That's a little surprising in view of the upgrade instructions at
> http://cyrusimap.web.cmu.edu/imapd/install-upgrade.html
> 
> Although they appear to be for 2.3, they seem to imply big changes in
> the default database format (from db to skiplist) for some files at the
> 2.1/2.2 boundary.

Well, I guess you are talking about this paragraph, right?
CR> The default database formats for the mailbox list and the seen state
CR> databases has been changed to the skiplist backend. There are two ways
CR> of dealing with this if you have been using the defaults.
CR>
CR>    1. Specify --with-mboxlist-db=berkeley and --with-seen-db=flat to
CR>       configure. This will instruct Cyrus to continue to use the
previous
CR>       defaults.
CR> [...]

Well, if that is true, than there really is nothing to do regarding the
databases. The Debian packages since at least 2.1 use
--with-mboxlist-db=skiplist --with-seen-db=skiplist, so there really is
no change here from Debian package 2.1.* to 2.2.13-3.

> I'm glad to hear that no special conversion action is required, though I
> wonder if that's too good to be true.

Glancing over the upgrade readme from upstream, it reminded me of one
thing you will need to do during the upgrade though: You need to run
masssievec if you use sieve for anything, because cyrus21-imapd used
plaintext sieve scripts while cyrus-imapd-2.2 uses precompiled bytecode
files (automatically compiled when uploaded with sieveshell or an
equivalent, the plaintext file is still stored on disk and is presented
when downloading the script later on).

Regards,
Sven

PS: No need to CC me, I'm subscribed to the pkg-cyrus* list which gets
copies of mails to the BTS anyway.