Bug#556388: Problem with cyrus-common-2.2.postinst script
Henrique de Moraes Holschuh
hmh at debian.org
Sun Nov 22 02:05:22 UTC 2009
On Sat, 21 Nov 2009, Henrique de Moraes Holschuh wrote:
> On Sat, 21 Nov 2009, Sven Müller wrote:
> > Henrique, you probably know this better than anyone else in the
> > packaging team, so:
> >
> > Could we skip this script during package upgrades?
>
> I think so. In fact, I am not sure we still need this script at all, it is
> stuff from 2002, Cyrus has came a long way since...
A quick read of doc/install.html tells me we need it on install.
It is the local admin's problem to run it when he creates new partitions (or
run mkimap and make sure the permissions are good for Debian cyrus), so we
can simply skip runing it on upgrades if we check and the dpkg-statoverride
information matches the filesystem.
Actually, I think we might not be doing the best possible thing with the
permissions and owners, either: the cyrus spool is completely private, it
should not be accessible by group "mail" at all, except for the local lmtp
UNIX socket in /var/run/cyrus/socket/, and that is under dpkg-statoverride
control, anyway.
Since we've been using cyrus:mail for about a decade, changing that requires
some care, but this is likely the best time to do it.
--
"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