[Pkg-Cyrus-imapd-Debian-devel] Re: Cyrus 2.2 packages in Debian Sarge

[Sven Mueller]

Sebastian Klamar wrote on 18/03/2005 21:10:
>>Problem is I don't have a host handy to do upgrade tests at the moment
>>(that might change next week however). But as far as I can tell from
>>installing cyrus-2.2 on a host which had been preconfigured for
>>cyrus-2.1 (it was a cyrus-2.1 installation but hadn't had any user
>>configured) , an upgrade should work out-of-the-box because virtual
>>domain support is disabled by default in 2.2 and without virtual
>>domain support, cyrus-2.2 seems to work the same way as 2.1 did. This
>>is just from the cyrus-POV however. 
> 
> Which scenarios do you need?  I have some VMware boxes where I can test
> nearly everything.  Maybe we can devide the work.  Only problem is that
> I cannot start before next friday (March 25th).


Well, what I basically need is a test of an upgrade from cyrus21-* to 
cyrus22-*. But VMware get's me to think about that a bit: I might be 
able to do some of the tests locally on my notebook by simply creating 
yet another VMware Debian installation. Using VMware snapshots, I will 
even be able to test upgrade scripts which upgrade from cyrus21 
installations to cyrus22 installations (only those installations that 
don't use robot101mode and virtual domains in cyrus21 though). As far as 
I can tell so far, that upgrade should be relatively easy to do with a 
set of transitional packages. Even without transitional packages, I 
would still like to provide an easy to use script for that sort of 
upgrade. Those users which use the undocumented virtual domains stuff in 
cyrus21 are out of luck though because they - well - used undocumented 
stuff;-)

> P.S.: Why didn't you CC the people offered their help in the bug
>       messages like you did in your mail from yesterday, 02:22:49 +0100?

Well, I think if they are willing to help, they should have subscribed 
to this groups mailinglist by now.

Another thing just crossed my mind when speaking of help needed: I 
transplanted all the patches that made sense to me from the cyrus21 to 
the cyrus22 package. This includes a patch which adds timeouts to 
lib/lock_*.c and I'm not 100% sure they do the right thing. Is anyone on 
this list capable of checking that? I know that the patch doesn't break 
Cyrus, but I'm not sure it is effective.

cu,
sven