Bug#611546: /etc/init.d/cyrus2.2: You are missing a dpkg-statoverride on /var/run/cyrus. Add it.

Henrique de Moraes Holschuh hmh at debian.org
Tue Feb 1 16:21:39 UTC 2011


On Tue, 01 Feb 2011, Lutz Christoph wrote:
> In that time range I upgraded the server, and it retained
> cyrus21-common. (Dunno why it didn't upgrade to 2.2.) And I believe this
> shows a good hint at what happened:

Ah, should be that.  An ordering problem re. cyrus21-common.

> cyrus21-common and cyrus-common-2.2 coexisted for a while until I
> removed cyrus21-common (and the other 2.1 packages). That probably
> removed the overrides.

Yes.  Nasty little bug, that.

> Nothing there upgraded the cyrus packages from 2.1 to 2.2, which is
> probably as intended. When I later upgraded, I must have managed to
> leave the 2.1 packages on the system. Though I wonder how, since the
> cyrus-common-22 packages says:
> 
> Replaces: cyrus21-common, cyrus22-common

It also Conflicts: cyrus21-common.  It *really* should have caused
cyrus21-common to disappear, and it didn't.

> Something that should have prevented cyrus21-common and cyrus-common-2.2
> from coexisting. Any idea hiow that might have happened?

This will require some testing upgrading paths using "piuparts" and chroots
to fix, I fear.

It might be easier to just document it in the BTS (can't happen in
Lenny->Squeeze transitions, since Cyrus 2.1 is not in Lenny), and for the
future, have the initscript heal missing statoverrides.

But we do have to check if it cannot happen also when going from 2.2 to 2.3
or 2.4.  My guess is that it does.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh





More information about the Pkg-Cyrus-imapd-Debian-devel mailing list