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

[Sven Mueller]

Henrique de Moraes Holschuh wrote on 29/04/2005 01:04:
> On Fri, 29 Apr 2005, Sven Mueller wrote:
> 
>>release on alioth (without news this time, the changes vs 0.3 are just
>>too small to be worth a news entry).
> 
> I will upload from the alioth release, then.

Perfect.

>>Do you think an announcement would make sense somewhere once it is accepted?
> 
> Yeah, something like "Cyrus IMAPd 2.2 packages uploaded to debian
> experimental, we do not guarantee the upgrade path yet, etc."

Sure, but where should I post it? debian-user? debian-devel?

>>Yes, it's /usr/lib/cyrus/cyrus-db-types.(active|txt) and it's checked in
>>/etc/init.d/cyrus21 (and I took that mechanism over to cyrus22). I will
>>probably do another upgrade test installation early next week. Will
>>create an appropriate upgrade script if I can figure out how to do it.
>>Only problem is: Do I want to run that script in /etc/init.d/cyrus22 or
>>in postinst?
> 
> You want to have that script in /usr/lib/cyrus/upgrade, and to have the
> cyrus22 initscript hint the used that reading
> /usr/share/doc/cyrus22-common/README.upgrade (or whatever) is the way to go
> if he wants to know why the initscript won't let cyrus start.
> 
> Then, in that script, you document all that needs to be done, including
> running the upgrade script.

Oh well, The description in README.upgrade is already fairly complete. I
would think that if we don't want a fully automatic upgrade, we could
just as well leave it at that. I will think about it some more.

> Cyrus is the kind of package we don't bother doing upgrades automatically,
> the information is too sensitive to risk that.

Yeah, I would certainly not create an automatic upgrade without also
automatically creating a backup of all modified files (and a rollback
script). We'll see.

cu,
sven