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

[Sven Mueller]

Henrique de Moraes Holschuh wrote on 17/03/2005 04:25:
> On Tue, 15 Mar 2005, Sven Mueller wrote:
> 
>>One patch I didn't apply since I'm unsure what it does and wether it 
>>still makes sense is the robot101/lmtpeolat patch. Your comment in the 
> 
> That patch should *NOT* be applied to 2.2.  For 2.2, real virtual domains
> are the way to go, and that hideous hack can finally die...

Fine, I removed the patch file from the 2.2 repository (hasn't been 
applied anyway).

> I will add all powers to your user on the project, so as soon as you deem it
> ready, be my guest and upload to experimental and publish a source package
> on alioth (anyone that cannot get a .deb out of a .dsc+tar.gz+diff should
> not get close to experimental packages IMHO). 

Well, I changed the revision number to 2.2.12-0.1 so we can have a few 
experimental releases (even with apt-get updates) before uploading a 
clean 2.2.12-1 to unstable. However as far as I can tell, _I_ can't 
upload to experimental since I'm no DD (yet). Feel free to upload the 
current package though. Ideally take the source from:

http://mail.incase.de/svn/cyrus22/tags/2.2.12-x/

But there are also source and binary packages of that revision for i386 
and amd64 at http://mail.incase.de/cyrus22 resp. /cyrus22/amd64

> Please don't uploads to sid until we have verified that we have changed
> everything we want that might cause upgrade path headaches).

Sure. I wouldn't have uploaded to sid for now anyway. 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. I 
think we might get upgrade problems (no unsolvable ones though) with the 
libdb-Upgrade from libdb3 to libdb4.2.

cu,
sven