Bug#620321: cyrus-imapd-2.4: When upgrading to cyrus 2.2/2.4, it shouldn't try to restart it

[Ondřej Surý]

> When upgrading to cyrus 2.2/2.4, it cannot start with the following messages:
>
> Mar 31 20:14:27 wolfe cyrus/lmtpunix[21633]: incorrect version of Berkeley db: compiled against 5.1.25, linked against 4.7.25

I am not sure how this could happen. All binaries are linked to
libdb-5.1.so. But it try to rework the debian scripts so the restart
is done at the very end.

> It shouldn't try to start it UNTIL the DB is upgraded but I was never aware cyrus would break when I upgraded it.

You should really go and read the documentation (README.Debian.*,
UPGRADE.Debian) provided in the /usr/share/doc/cyrus-common/. There is
also a detailed NEWS.Debian which is quite clear that the package is
not ready for automatic upgrade.

> I noticed my /var was full and when investigating, figured out it was because the upgrade of cyrus-imapd didn't go well... but I was never aware of this situation until then.

I don't understand. Are you saying that cyrus-imapd filled your logs?
Or something else happened?

O.
-- 
Ondřej Surý <ondrej at sury.org>