[Pkg-Cyrus-imapd-Debian-devel] Upload to debian/experimental?

[Sven Mueller]

debian-devel@der-mic.de wrote on 29/04/2005 07:51:
>>Are there any reasons against this?
>
> Yes, please let's update the docs before. See below.

Oh well.

>>Should we provide a better upgrade path for those coming from cyrus21?
>>Except for the necessary database upgrade (from BDB3 to BDB4), cyrus22
>>is a drop-in replacement for cyrus21. If the websieve maintainer doesn't
> 
> Well, no ;-).
> Not if you are using Sieve-Filters.

Ooops, right. I just committed a change which includes the necessary
masssievec (well, you could to what massievec does manually) in
cyrus22-common and included a small piece of information about that in
UPGRADE.Debian. However, any additional (or better) documentation of the
upgrade process is really welcomed.

> Starting with cyrus 2.2.? you have to use sieve-scripts compiled into
> bytecode.
> I upgraded my cyrus from 21 to 22 a month ago. Off course I read
> UPGRADE.Debian.gz but there is no word of bytecode. Simply a note to run
> /usr/lib/cyrus/upgrade which did not worked for me. None of my scripts
> were updated. I think the script did not dive into the subdirs [a-z]*.

Well, I think the existing upgrade scripts simply don't compile sieve
scripts. Don't have much time to check that though, any assistance
highly appreciated there.

>>to the libcyrus-imap-perl22 package. Actually, I've already done so and
>>websieve still works perfectly fine. I also checked the API of both perl
>>bindings, and the cyrus22 version seems 100% backward compatible.
> 
> BTW: SmartSieve works also perfectly.

Good. Would have found it very confusing if it didn't though.

cu,
sven