Bug#369882: cyrus-doc-2.2 upgrade issues

[Ross Boylan]

On Mon, Jun 12, 2006 at 10:39:31PM -0400, Benjamin Seidenberg wrote:
> Hi Ross.
> I just wanted to let you know that we're not ignoring you. We usually
> have a very quick turn around time on technical bugs, but unfortunately
> this is a documentation bug, and you know how those things go. Rest
> assured, we do know your issues need to be solved.
> 
> Sven and I have talked about them a few times, but the problem is, he
> doesn't have enough free time and I don't know enough about older
> versions of cyrus to do the work myself.
> 
> We do plan on getting this fixed, and the next upload won't happen
> without it (unless an RC bug comes along I suppose). I apologize for the
> delays, and just wanted to let you know what the status is.
> 
> Thanks for your patience,
> Benjamin
> (Member of Debian Cyrus Packaging Team)

Thanks for letting me know, and for your work on the package.

After all this, I decided I just wasn't sure what the safe upgrade
route was, so I'm holding off.  The old version continues to work; I
mostly got interested because I'm installing the newer version on a
new system, and would rather keep things consistent.

Ross

P.S. There might be an RC issue floating around here, since it's not
clear that an upgrade from 2.1 -> 2.2 leaves you with a working system
(actually, it seems pretty clear that it  doesn't).  There even seems
a chance of data corruption, since the 2.2 will start before the data
are converted (though my guess is it will just refuse to run).

I guess the fact that the packages have different names is kind of a
sign of these incompatibilities (same deal with apache and exim).

One possibility is that there's actually some upgrade code that needs
to be written or changed to deal with this.  Given the current Debian
notes about disliking automated scripts (or the people who use them
:)) and the diversity of installations that may not be possible or
desirable.  But enough info so we can do it on our own would be nice
:) The minimal info would be a description of how the Debian setup
differs (or doesn't) from upstream, so we can tell what fraction of
the upstream advice to take.  That's a little challenging, since we
need to know not only how 2.2 differs from upstream, but also how the
version we are upgrading from differs from upstream.